Advertisement
Wolfbeast

AdNauseam, developer discussion

Sep 1st, 2017
331
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 27.25 KB | None | 0 0
  1. ========================================================================
  2.  
  3. >> Forum PM
  4.  
  5. ========================================================================
  6.  
  7. Re: AdNauseam (discussion with the developer)
  8. Sent: 30 Aug 2017, 11:48
  9. From: dhowe
  10. Recipient: Moonchild
  11. Moonchild,
  12. Greetings. I am the primary developer of the AdNauseam extension... Wondering if you might have a moment to discuss the issue ?
  13. much appreciated,
  14. Daniel
  15.  
  16. ========================================================================
  17.  
  18. Sent: 30 Aug 2017, 12:37
  19. From: Moonchild
  20. Recipient: dhowe
  21.  
  22. dhowe wrote:
  23. Greetings. I am the primary developer of the AdNauseam extension... Wondering if you might have a moment to discuss the issue ?
  24.  
  25.  
  26. Absolutely. I'm not sure if you've taken a look at the thread on this forum about it yet, but if you haven't please read my posts in it explaining the problem with your extension that makes it directly harmful due to its clickbot nature.
  27.  
  28. ========================================================================
  29.  
  30. Sent: 30 Aug 2017, 14:46
  31. From: dhowe
  32. Recipient: Moonchild
  33. Sure, and of course I have read your posts and the various responses on the forum. So you know, my intent in contacting is not to argue, but only to make sure we fully understand each others positions (both being long-time members of the FOSS community) ... then if we still disagree, thats ok
  34.  
  35. So, whats your preferred place to chat: signal, telegram, email ?
  36.  
  37. ========================================================================
  38.  
  39. Sent: 30 Aug 2017, 21:54
  40. From: Moonchild
  41. Recipient: dhowe
  42. Good.
  43.  
  44. I don't even know what "signal" is, so definitely not preferred. I don't use Telegram. If you prefer instant messaging we can use XMPP/Jabber, my account being {{scrubbed}} for that, or (maybe best to get our points across) via e-mail. You can use {{scrubbed}} for that.
  45.  
  46. Either way, you've read my responses. I also understand the reason why the extension was created but in my observations it completely misses the mark and the collateral is severe.
  47.  
  48. ========================================================================
  49.  
  50. >> e-mail
  51.  
  52. ========================================================================
  53.  
  54. From: Daniel Howe
  55. To: Moonchild
  56. Subject: Re: AdNauseam (discussion with the developer)
  57. Message-Id: <D73B446F-79DB-4E79-8B3F-324FDD693E51@rednoise.org>
  58. Date: Thu, 31 Aug 2017 22:46:30 -0400
  59.  
  60. Moonchild,
  61.  
  62. Thanks for the reply. We have read your explanation (and the forum discussion) for the ‘block’ of AdNauseam and there are a few counter-arguments we’d like to make:
  63.  
  64. 1. First it seems that we're in agreement on the basic idea that user well-being should be the primary objective, and so that is a good starting point... We only disagree as to how that well-being can be best served. We believe that users are already being harmed, in quite significant ways, by the surveillance advertising system. This system relentlessly tracks users from site-to-site without their knowledge or consent, imposes significant costs, both financial (for users on fixed data plans) and in terms of page-load times, and exposes them to malware (a fact that has been very well-documented). These do not even begin to list the general privacy threats stemming from these accumulations of personal data maintained by vast commercial actors (what happens, for example, when such data is lost to hackers?)
  65.  
  66. 2. We also both worry about the health of the large ecosystem (the web) in which we all work. However, we would argue that the current state of the ecosystem is already quite unhealthy and does not at all represent a desirable equilibrium we’d want to maintain or protect. The way we see it, surveillance advertising is one of the most harmful forces on this ecosystem, definitely not our small attempt at protest. In fact there is significant evidence that the recent false news trends and recent various forms of hateful expression have been directly fueled by advertising payments [1].
  67.  
  68. 3. We disagree with your classification of ADN as malware for a number of reasons: malware works against the user's own interests/intentions, AdNauseam does not; malware misrepresents or hides its functions, AdNauseam does not; malware operates without the user's knowledge or consent; AdNauseam does not; once installed malware is difficult or impossible to remove; AdNauseam is not. It is far easier, we’d argue, to characterize tracking and profiling by ad networks as malware, as it works against user interests, misrepresents its function, and operates without the user's knowledge or consent -- and ever since it took over the web's ecosystem and established itself as the status quo, it has become impossible to remove.
  69.  
  70. 4. You claim that our efforts will end up hurting small publishers and web sites whose only option for funding is (tracking) advertising.
  71.  
  72. First, we argue (as you yourself suggest on your home page**) that other more 'responsible' alternatives exist for websites, big or small, who wished to generate revenue via ads. Our project is not against online advertising itself, but only irresponsible and harmful advertising. In fact, if a website is acting responsibly and asserts this with a simple text-only DNT notice [2], ads on their website are neither hidden, nor clicked by AdNauseam by default.
  73.  
  74. ** Actually would be great if you could provide some more info on what you use for your advertising, as we weren't able to find it in your documentation. From a quick inspection, it looks like your site contacts hundreds of 3rd-parties, including Google, Facebook, and other tracking ad networks (see https://github.com/dhowe/AdNauseam/wiki/Pale-Moon-website)
  75.  
  76. Second, it is not our intent to harm small publishers, or publishers at all. As stated in our documentation we target advertisers and ad-networks. Is it possible that some small websites may be injured in the process? Perhaps (though in the short term their revenues may actually increase), but it is clear that the harmful and unethical system currently in place will not change while advertising profits remain as high as they are...
  77.  
  78. As the EFF (who we worked with on AdNauseam) put it: "This brings us to the fundamental challenge: the publishing and advertising ecosystem must reform in order to recover the user trust lost due to widespread bad practices in the industry” [3]. Unfortunately, the big players (Google, Facebook, etc.) hear only one language, that of money. There are alternative, more ethical models for funding that are currently being experimented with, but none of them will become truly viable without some financial (dis)incentive for the big players who have monopolized the market into stagnation.
  79.  
  80. Looking forward to your feedback…
  81.  
  82. cheers,
  83. Daniel
  84.  
  85.  
  86. [1] Dave, Paresh. "Without these ads, there wouldn't be money in fake news." The Los Angeles Times. December 6, 2016.
  87. Nicas, Jack. "Fake-News Sites Inadvertently Funded by Big Brands." The Wall Street Journal. December 8, 2016.
  88. Marshall, Jack. "IAB Chief Calls on Online Ad Industry to Fight Fake News." The Wall Street Journal. January 30, 2017.
  89. Tambini, Damian. "How advertising fuels fake news." LSE Media Policy Project Blog. February 24, 2017.
  90.  
  91. [2] https://www.eff.org/issues/do-not-track
  92.  
  93. [3] ibid
  94.  
  95. ========================================================================
  96.  
  97. Subject: Re: AdNauseam (discussion with the developer)
  98. To: Daniel Howe
  99. From: Moonchild
  100. Message-ID: <59A842AB.70203@palemoon.org>
  101. Date: Thu, 31 Aug 2017 19:08:59 +0200
  102.  
  103.  
  104. Daniel,
  105.  
  106. Thanks for taking the time to write your counter-arguments down for
  107. me, however it seems you are unaware of some of the mechanics at work
  108. here. As I already stated in my forum PM reply, your intention with
  109. the extension is clear, however, it completely misses the mark.
  110.  
  111. On 01/09/2017 04:46, Daniel Howe wrote:
  112. > 1. [...] We believe that users are already being harmed, in quite
  113. > significant ways, by the surveillance advertising system. This
  114. > system relentlessly tracks users from site-to-site without their
  115. > knowledge or consent, imposes significant costs, both financial
  116. > (for users on fixed data plans) and in terms of page-load times,
  117. > and exposes them to malware (a fact that has been very
  118. > well-documented).
  119.  
  120. The problem is that AdNauseam makes this surveillance worse (and that
  121. is where it completely misses the mark as far as that is concerned) by
  122. first collecting the ads (causing requests to advertisers) and then
  123. purposefully generating clicks, instead of preventing the content from
  124. being grabbed. I have absolutely no problem with the other two
  125. components of your extension (ad blocking and malware domain
  126. blocking), but the bot-ad-clicking is a problem, even from this
  127. privacy point of view. You are generating visits to external sites
  128. that would otherwise not know of the user's existence, and in turn to
  129. their linked external sites, in effect putting the user on the map and
  130. making them many-fold easier to track from site to site by
  131. broadcasting the presence to linked target sites.
  132.  
  133. Also, I'd like to remind you that upholding privacy for any visitor to
  134. any public site on the web is a paradox. As a user, you are moving
  135. around in the public space. The tracking is possible mainly because
  136. the advertising in general is in the hands of a few very large
  137. corporations that will be able to track users' "motions" because they
  138. have sensors (in the form of ads) on a very large percentage of sites
  139. on the web. Making this presence more obvious with generated clicks
  140. only makes the tracking more accurate and you are going right against
  141. the premise behind your extension: it doesn't do its job, and in fact,
  142. does the opposite of what it sets out to do.
  143.  
  144. > 2. We also both worry about the health of the large ecosystem (the
  145. > web) in which we all work. However, we would argue that the current
  146. > state of the ecosystem is already quite unhealthy and does not at
  147. > all represent a desirable equilibrium we’d want to maintain or
  148. > protect. The way we see it, surveillance advertising is one of the
  149. > most harmful forces on this ecosystem, definitely not our small
  150. > attempt at protest. In fact there is significant evidence that the
  151. > recent false news trends and recent various forms of hateful
  152. > expression have been directly fueled by advertising payments [1].
  153.  
  154. I absolutely agree that some things are definitely not in the most
  155. desirable state, but the whole false news trends (and the equally
  156. false counter-initiatives that are just censorship in disguise) are
  157. *completely* beside the point here. It doesn't matter what advertising
  158. money is used for. It also doesn't matter that false news would
  159. generate advertising money by creating a buzz and the resulting
  160. traffic to otherwise unknown or not-visited websites.
  161.  
  162. Approaching it in a way that is harmful is not going to shift that
  163. balance in favor of the desired equilibrium either, because you are,
  164. whether you intend to or not, hurting publishers (or at the very least
  165. hurting them disproportionately more than the ad networks because of a
  166. combination of factors, see below) who use advertising on legitimate
  167. sites with legitimate interests and a legitimate need to obtain
  168. revenue to keep afloat. This is especially true for publishers of free
  169. software who, save a few corporations (with their own issues of
  170. freedom as a result) will have to depend on their independence and
  171. independent income to keep doing what they are doing. Many FOSS
  172. projects are small teams or individuals who have no other source of
  173. funding for their projects -- individual donations are by far and wide
  174. a joke that won't help with practical expenses. I've seen the same in
  175. the early years of Pale Moon.
  176. In fact, the only reason Pale Moon is still a thing after mid-2016
  177. when Google pulled a nasty on us is because I had been able to branch
  178. out to alternative sources of income to support the project (our
  179. partnership with DuckDuckGo chief among them) -- only thanks to the
  180. steady, organic growth we've seen because of my work and principles.
  181. Many small-time publishers won't have that option, and it will ring
  182. their death bell -- not unlike many vloggers who had to shut down
  183. because of the youtube revenue "adpocalypse".
  184.  
  185. > 3. We disagree with your classification of ADN as malware for a
  186. > number of reasons: malware works against the user's own
  187. > interests/intentions, AdNauseam does not; malware misrepresents or
  188. > hides its functions, AdNauseam does not; malware operates without
  189. > the user's knowledge or consent; AdNauseam does not; once installed
  190. > malware is difficult or impossible to remove; AdNauseam is not.
  191.  
  192. Malware is a general term for malicious software. It does not have to
  193. be hidden to be malicious; it does not have to act like a worm, trojan
  194. or other difficult to counter or remove piece of software to be
  195. malicious. It does not have to harm the user installing it to be
  196. malicious.
  197.  
  198. Malware does not have to target the user who installs it. Botnet
  199. clients are malware; while they do not harm the user installing the
  200. software, they cause harm to innocent third parties (either targeted
  201. or not) by using the user's resources. AdNauseam does this.
  202.  
  203. Malware is often installed with the user's knowledge and consent, but
  204. is malicious in that it misleads the users into thinking that its
  205. purpose is something different than what it effectively achieves.
  206. (e.g.: a productivity toolbar in a browser that causes ad popups)
  207. AdNauseam does this too. It misrepresents its functions
  208. (anti-surveillance while causing more surveillance. Causing a protest
  209. to ad networks (good intention) while causing harm to publishers,
  210. instead (bad effective result)) and goes against the user's intentions
  211. by achieving something different (and in this case also opposite) than
  212. its claimed purpose.
  213.  
  214. If you want to avoid a discussion about semantics, then we can agree
  215. that AdNauseam is at the very least harmful. Part of this harm is by
  216. design (but ineffective, see below) but a bigger part of this seems to
  217. be unintentional.
  218.  
  219. Whether there is intent or not involved is, however, not a criterion
  220. for what ends up on our blocklist; that is pure a matter of objective
  221. observation and evaluation of observed behavior and result from said
  222. behavior.
  223.  
  224. > 4. You claim that our efforts will end up hurting small publishers
  225. > and web sites whose only option for funding is (tracking)
  226. > advertising.
  227. >
  228. > First, we argue (as you yourself suggest on your home page**) that
  229. > other more 'responsible' alternatives exist for websites, big or
  230. > small, who wished to generate revenue via ads.
  231.  
  232. Can you please point me to the exact location where this is stated?
  233. The only statement similar to that is where we alert people who use ad
  234. blockers that we use responsible ad services (which means that we
  235. avoid known malicious ad networks wherever possible) to keep the users
  236. as safe from malvertising as feasible.
  237.  
  238. > Our project is not against online advertising itself, but only
  239. > irresponsible and harmful advertising. In fact, if a website is
  240. > acting responsibly and asserts this with a simple text-only DNT
  241. > notice [2], ads on their website are neither hidden, nor clicked by
  242. > AdNauseam by default.
  243.  
  244. DNT is, however, a completely failed concept because there is no
  245. organizational structure in place to ensure that sites that state they
  246. do not track, really don't track. Also, as you have seen from your
  247. analysis of www.palemoon.org, placing an ad through a bidding system
  248. (which is the regular way of offering ad space) contacts third party
  249. servers, out of direct control of the publisher, that may or may not
  250. track. Stating that the website "does not track" doesn't mean that
  251. external content does not track, and relying on such a statement is
  252. completely pointless as a result, since it is almost certainly false
  253. in practice.
  254.  
  255. > ** Actually would be great if you could provide some more info on
  256. > what you use for your advertising, as we weren't able to find it in
  257. > your documentation. From a quick inspection, it looks like your
  258. > site contacts hundreds of 3rd-parties, including Google, Facebook,
  259. > and other tracking ad networks (see
  260. > https://github.com/dhowe/AdNauseam/wiki/Pale-Moon-website)
  261.  
  262. We use Meridian(Sovrn) as a "first bid" (RTB) network. This currently
  263. a trial and I'm not generally happy with the way it looks despite
  264. their promises, so may remove them. When there is no fill from them,
  265. it falls back to Google AdSense (single cascade). That is all that is
  266. in use.
  267. Any further content pulled in by either ad provider is out of our
  268. control, and as expected contacting other sites and servers in their
  269. ad network to provide the bidding service and display ad content --
  270. which may be as complex as an html5 iframe. That is the very nature of
  271. an ad network.
  272. We place our trust in these providers that they exclude malvertising
  273. domains. If you want to prevent that behavior, then blocking the
  274. initial ad script call is your only sure-fire way. Actively pulling in
  275. the ad and then on top "clicking" on it will contact many more
  276. external sources, whether you discard the response or not.
  277.  
  278. > Second, it is not our intent to harm small publishers, or
  279. > publishers at all. As stated in our documentation we target
  280. > advertisers and ad-networks. Is it possible that some small
  281. > websites may be injured in the process? Perhaps (though in the
  282. > short term their revenues may actually increase), but it is clear
  283. > that the harmful and unethical system currently in place will not
  284. > change while advertising profits remain as high as they are...
  285.  
  286. It's great that it's not your intent! I had no doubts about that,
  287. however what you really intend to do with the extension, you don't
  288. achieve either, and the unintentional result is being harmful (and as
  289. a result unethical) here. You say you have read my explanation on the
  290. forum, but judging by the statement here you haven't fully
  291. comprehended or grasped what factually happens.
  292.  
  293. The short-term increase caused by false clicks will only last as long
  294. as the ad network does not detect the nature of the traffic (and trust
  295. me, their algorithms for detecting fake clicks are pretty damn
  296. accurate because of so many attempts at click-fraud that occur all the
  297. time). For example, any fake clicks will always cause a noticeable and
  298. otherwise unwarranted increase in ad target site impressions, and
  299. those impressions will have 0% conversion since they are not displayed
  300. to the user.
  301.  
  302. After that, two things will happen:
  303.  
  304. 1. Direct harm: The ad network will put a hard filter on the
  305. publisher's account (not just the detected website) to dock any and
  306. all pay that looks even the most remotely like invalid traffic.
  307. Because of delayed payment by ad networks, this is usually done on
  308. anything that has not been paid out yet, retroactively. This kind of
  309. docking usually is not reflected in what advertisers pay (since they
  310. pay the moment ads are placed) and will be a net **win** for the ad
  311. network until the delay catches up with the catalog price of the ad
  312. positions.
  313. In the worst case, publishers may see their account closed with no
  314. opportunity for appeal, effectively cutting their income off
  315. completely, overnight, by no action of their own -- that's a financial
  316. take-down. It's usually up to the publishers to try (note: try) and
  317. provide evidence that "it wasn't them" when they are accused of
  318. click-fraud.
  319.  
  320. 2. Indirect harm: The paid revenue value of the ad positions on all
  321. sites on the account will drop like a brick. Ad networks will no
  322. longer adopt the ad positions as "prime" placements when the account
  323. is marked as "generates invalid traffic above the threshhold", and
  324. advertisers aren't willing to pay top dollar for positions known to
  325. attract fake traffic. This devaluation is usually permanent, even if
  326. the publisher "shapes up to them" later on.
  327.  
  328. While (2) is a longer-term effect for ad networks (since their catalog
  329. of ad positions will have fewer "favored" sites), it does not cause a
  330. loss for them because Advertisers will use fixed budgets, and in turn
  331. will just end up with their ads shifted to other sites or paying more
  332. per impression because of increased competition with a smaller (but
  333. higher quality of conversions) market. So in effect it has zero
  334. influence on advertisers or ad networks unless your small protest
  335. would cover a large percentage of browser users out there, which is
  336. likely not going to happen.
  337.  
  338. As a result, the net outcome of AdNauseam is that people's browsers
  339. are turned into clickbots that hurt the very sites they like to visit,
  340. and does nothing to combat "ad surveillance", nor hurt ad networks.
  341. AdNauseam only does harm by its bot-clicking. As such, I saw no
  342. alternative but to block it by default in the browser, until its
  343. behavior is no longer harmful.
  344.  
  345. Counter the EFF, all of this knowledge comes from from personal
  346. experience and having moved in the website and advertising business in
  347. many levels for over 10 years. I agree the system is not at all fair
  348. and driven by mo'money in many respects, but damaging the very people
  349. who would, if able to band together in a concerted effort, be able to
  350. start making a change in attitude is definitely not going to help
  351. their or your cause.
  352.  
  353. I'm sure your immediate question would be "but adblockers are harmful
  354. too?", and you are correct. There is however an important difference
  355. between ad blocking (preventing content from being downloaded by the
  356. client and resulting in a shifted balance between bandwidth used and
  357. revenue gained by all involved, which is usually not that big of a
  358. deal, and otherwise not harming revenue of ads displayed) and
  359. generating fake user actions (actively harming website publishers'
  360. revenue over ALL their ad's clicks, not just the ones generated by the
  361. bot). On top, being selective in what sites to generate clicks on
  362. makes the extension even more like an attack on targeted websites and
  363. more like your own limited definition of malware.
  364.  
  365. Sorry that this has gotten very lengthy, but I wanted to make sure to
  366. try and be as clear as possible to get across why I cannot in good
  367. conscience allow your extension to be freely installed and leveraging
  368. the browser to cause harm to others who have had no part in creating
  369. or maintaining this unbalanced ad monopoly.
  370.  
  371. If you think I'm overlooking something essential, please let me know
  372. -- it seems rather clear-cut to me though.
  373.  
  374. Moonchild.
  375.  
  376. ========================================================================
  377.  
  378. Subject: Re: AdNauseam (discussion with the developer)
  379. From: Daniel Howe
  380. To: Moonchild
  381. Date: Fri, 1 Sep 2017 14:13:01 -0400
  382. Message-Id: <75EB3476-CBEF-4D2E-B2E3-E4455FBF5D66@rednoise.org>
  383.  
  384.  
  385. Thanks for the reply. I think that at this point it is perhaps best to agree to disagree, as you seem committed to your position and/or more comfortable than we are with the status quo. That you would consider your use of Google/Doubleclick ad networks, exposing even casual visitors to your site to hundreds of trackers without their knowledge or consent, to be “responsible”, is difficult for us to understand. However, the Web, like all communities, thrives on respect for a range of different opinions and options, as I think you would agree. It is disheartening that you don’t respect the users of Pale Moon enough to come to their own decisions on such matters, but in the end this is your call to make.
  386.  
  387. [image of anti-adblock announcement on www.palemoon.org]
  388.  
  389. ========================================================================
  390.  
  391. Subject: Re: AdNauseam (discussion with the developer)
  392. To: Daniel Howe
  393. From: Moonchild
  394. Message-ID: <59A90C8B.5070409@palemoon.org>
  395. Date: Fri, 1 Sep 2017 09:30:19 +0200
  396.  
  397.  
  398. Hi Daniel,
  399.  
  400. It's disappointing to see that you are using our use of Google ads on
  401. our home page as the only argument to discard our entire discussion!
  402. I thought better of you.
  403.  
  404. --- about the ads; tangent ---
  405. Do you realize that the "alternative" to using this network is using
  406. small-time networks that use all the dirty tricks in the book to have
  407. people download actual viruses, trojans, and other form of your
  408. definition of malware? I've tried several dozen, and none of them were
  409. responsible in their ad content because all they would look at would be
  410. maximum revenue regardless of content of ads. In that respect those are
  411. way worse than Google in that it's a wild west and real danger to
  412. website visitors -- Sovrn and Google are responsible in their ad
  413. content, whether you hate them or not doesn't change that fact.
  414.  
  415. Also, as another thread on the forum is indicating: I'm going to reduce
  416. our use of display ads on our websites when it becomes feasible, so
  417. please don't underestimate the effort I am making in my own way to
  418. combat this status quo and user tracking through ads. Being able to have
  419. donations and sponsorship pay for our sites to become ad-free is a
  420. primary goal. And then everyone wins.
  421.  
  422. This still has nothing to do at all with the fact that blocking these
  423. ads would stop the potential tracking for website visitors. This is
  424. still an option that I indicate clearly -- users can donate and ignore
  425. the message on our page when they do. Close it and it's gone; or they
  426. can not do anything else and keep blocking, or block the message too --
  427. that's fine too.
  428. --- end tangent ---
  429.  
  430. But sure, if this is only how far you're willing to go, then I'll agree
  431. to disagree; mainly because you choose to ignore the facts I laid out in
  432. our discussion about your extension's level of damage. I find it really
  433. sad to see a good idea at heart being locked in an unacceptable
  434. execution with a disinterest when pointed to (I think solvable)
  435. behavioral issues with the extension.
  436. Your extension will remain on our block list as long as it won't change
  437. its damaging behavior at the "harmful" level (hard-blocked by default).
  438.  
  439. With your permission, I'd like to make (parts of) our discussion public
  440. for our users to provide some feedback and keep things transparent to
  441. them, without having to re-write them (dealing with AdNauseam has
  442. otherwise already been too much of a timesink, all in all).
  443.  
  444. Looking forward to your reply,
  445.  
  446. MC
  447.  
  448. [quoted text removed]
  449.  
  450. ========================================================================
  451.  
  452. Subject: Re: AdNauseam (discussion with the developer)
  453. From: Daniel Howe
  454. In-Reply-To: <59A90C8B.5070409@palemoon.org>
  455. Date: Fri, 1 Sep 2017 16:20:02 -0400
  456. Message-Id: <C53E6D08-F5E5-4B27-891F-F8C88A5A236B@rednoise.org>
  457. To: Moonchild
  458.  
  459. MC,
  460. I am fine with you publishing the discussion in its entirety, however I would
  461. request you not to extract any parts or sections from the larger context.
  462. thanks,
  463. Daniel
  464.  
  465. [quoted text removed]
  466.  
  467. ========================================================================
  468.  
  469. Subject: Re: AdNauseam (discussion with the developer)
  470. To: Daniel Howe
  471. From: Moonchild
  472. Message-ID: <59A919E8.3040009@palemoon.org>
  473. Date: Fri, 1 Sep 2017 10:27:20 +0200
  474.  
  475.  
  476. Of course I'll keep things in context.
  477.  
  478. [quoted text removed]
  479.  
  480. ========================================================================
  481.  
  482. Subject: Re: AdNauseam (discussion with the developer)
  483. From: Daniel Howe
  484. In-Reply-To: <59A919E8.3040009@palemoon.org>
  485. Date: Fri, 1 Sep 2017 16:45:20 -0400
  486. Message-Id: <A6B60D57-7E29-4E04-AAD5-0610E6E341A5@rednoise.org>
  487. To: Moonchild
  488.  
  489. Just to be fully clear, I am fine if you publish the entire conversation,
  490. but I do not give permission for the publication of any parts or sections.
  491. best of luck going forward,
  492. Daniel
  493.  
  494. [quoted text removed]
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement