13 ms·
Help EFF test Privacy Badger, our new browser extension for privacy
- dan_bk 13y agoFirefox users should install: To block tracking background requests: -> RequestPolicy: https://addons.mozilla.org/en-US/firefox/addon/requestpolicy/ https://addons.mozilla.org/en-US/firefox/addon/requestpolicy... To block ads/trackers: -> Adblock Edge: https://addons.mozilla.org/en-US/firefox/addon/adblock-edge/ https://addons.mozilla.org/en-US/firefox/addon/adblock-edge/ To eliminate tracking via cookies/persistent Flash cookies/Localstorage: -> Self-Destructing Cookies: https://addons.mozilla.org/en-US/firefox/addon/self-destructing-cookies https://addons.mozilla.org/en-US/firefox/addon/self-destruct...
- heinrich5991 13y agoI have RequestPolicy installed, but at some point its intrusiveness led me to disabling it again. I can't really recommend it. The other two however, go for them, they're not intrusive to the user experience at all in my experience. Is there a reason why you suggest Adblock Edge instead of Adblock Plus?
- shiven 13y agoAdblock Plus has gone partly rouge, at least for the hardcore anti-ad crowd, ever since it started taking money from and "allowing" certain advertisers to get through without blocking. Adblock Edge is not known to have such issues, as of yet.
- dan_bk 13y ago> [...] its intrusiveness [...] Personally, I'd rather call the usual +/- 20 background requests per page (of which each company may track you) "intrusive". But I suppose that's a matter of preferences. EDIT re: Adblock Edge instead of Adblock Plus: Adblock Plus has sold out, taking money for unblocking certain ads.
- hackuser 13y agoAs a counterpoint: I use Request Policy and love it. For those who don't know, Request Policy (RP) simply blocks requests outside the website's domain. I configured mine to deny all requests unless I whitelist them (by hostname). It eliminates most security issues; Ghostery rarely has to block any trackers, for example. I would never recommend it for a typical end-user; it requires too much understanding (e.g, to understand enough about CDNs to identify which hosts need to be whitelisted). For most people reading this, it would be no problem. It comes with large, pre-configured whitelists that cover many common websites. Many sites work fine without anything whitelisted, though most need at least one host for their CSS. More complex sites, such as those running applications, can take some effort to get running. Once you figure out a site, RP remembers the whitelist and the site works indefinitely. The interface needs work but it's functional. There is a beta of a new version, which is supposed to fix some interface issues, but I haven't tried it.
- huhtenberg 13y agoI'd start with Smart Referrer https://addons.mozilla.org/en-US/firefox/addon/smart-referer/ https://addons.mozilla.org/en-US/firefox/addon/smart-referer...
- SudoNick 13y agoFYI: The latest versions of Adblock Plus and Adblock Edge yield to Firefox during startup. Which, it seems, prevents them from having loaded all of their rules by the time Firefox begins to process requests. IOW, they don't block everything they should when Firefox first starts up.
- IvyMike 13y agoHow does this compare to Ghostery and/or Disconnect?
- Kerrick 13y agoFrom https://www.eff.org/privacybadger https://www.eff.org/privacybadger > How is Privacy Badger different to Disconnect, Adblock Plus, Ghostery, and other blocking extensions? > Privacy Badger was born out of our desire to be able to recommend a single extension that would automatically analyze and block any tracker or ad that violated the principle of user consent; which could function well without any settings, knowledge or configuration by the user; which is produced by an organization that is unambiguously working for its users rather than for advertisers; and which uses algorithmic methods to decide what is and isn't tracking. > Although we like Disconnect, Adblock Plus, Ghostery and similar products (in fact Privacy Badger is based on the ABP code!), none of them are exactly what we were looking for. In our testing, all of them required some custom configuration to block non-consensual trackers. Several of these extensions have business models that we weren't entirely comfortable with. And EFF hopes that by developing rigorous algorithmic and policy methods for detecting and preventing non-consensual tracking, we'll produce a codebase that could in fact be adopted by those other extensions, or by mainstream browsers, to give users maximal control over who does and doesn't get to know what they do online.
- furyg3 13y agoYet another plugin to add to my privacy arsenal (opt-outs from Google, AdBlock, Ghostery, Disconnect, and now Badger). This really reminds me of the early years of antivirus on Windows, when you needed at least two antivirus suites to catch everything. Just as vendors eventually acknowledged (mostly) their responsibility for security on their OSes, browsers need to step up and start implementing these features by default, and innovating. It's crazy that, at the moment, I have to grant a third party total and unlimited access to my browser and history in order to protect my own privacy. This should be on, by default, since most people are generally either adamantly against being tracked or ignorant of it and their options. The handful of people that have a hard-on for targeted marketing should be ticking checkboxes in preference panels and installing plugins, not people who would rather Neilson not know everything about them...
- scrollaway 13y agoThis seems like it would completely replace Disconnect/Ghostery. Am I correct?
- untothebreach 13y agoI think he is aiming for redundancy. I.E., what happens if Ghostery starts letting companies pay to be 'let through'? The GP might know about it, since I'm sure that kind of story would find it's way to HN, but it's nice to have some redundancy when it comes to protecting ones privacy.
- scrollaway 13y agoWhich is why it's awesome the EFF is doing this one. They can be trusted.
- higherpurpose 13y agoYou could just use Epic instead, which would be like using Linux or Mac without an antivirus: https://www.epicbrowser.com/ https://www.epicbrowser.com/
- aaronem 13y ago> This week, Mozilla published research showing that privacy is the single most important thing that users want from their web browsers. I can't speak for anyone else, but I'd be happy just to have a version of Firefox that didn't leak memory like a sieve and become unusably laggy after a day or so. Strangely enough, though, Mozilla's "research", which is nothing more or less than a "click this or this or this" sort of poll, doesn't offer any option for "I'd like your product to suck less please".
- mike-cardwell 13y agoYour opinion is out of date.
- aaronem 13y agoIt's funny you should say that, because outside cross-browser functionality testing, Firefox has been my default browser since back when it was still called Phoenix. The reason I complain about Firefox's memory leaks and general flakiness is not because I hate the browser and want it to die, but because I like it and I'm sick of having to kick it over and restart it every day so that I can use it without the UI freezing for ten seconds out of every thirty. Naturally, I've grown quite accustomed, in those rare cases when I muster the temerity to express this opinion, to being shouted down for it. I am surprised to see that happen on Hacker News, though; on 4chan it'd be de rigeur, of course, but I expected better here. I don't know why, though; after all, it's precisely the same attitude which characterizes Mozilla's approach to bug reports.
- mike-cardwell 13y agoYou must be unlucky then, because I've been using Firefox for years, on various versions of OSX, Linux and Windows and have never suffered issues as severe as you describe. And over the past year or so, things have just got better and better. From what I've seen, most people don't have the problems you describe with recent versions of Firefox.
- 13y ago
- Revisor 13y agoI would love it if there was a plugin that combined the blacklist part of Disconnect/Ghostery with the learning algorithm of Privacy Badger and the anti-fingerprinting features of Secret Agent. There are many trackers that are known in advance and there is no need to analyse them. Stop them right away. New ones crop up, or old ones change domains, watch them and block them. And randomize my headers so even if cookies are blocked, they can't fingerprint me statistically. Btw. what is the point of Privacy Badger without the Do Not Track header?
- blueskin_ 13y agoEven without DNT, it still blocks tracking cookies, etc.
- jstalin 13y agoThanks for mentioning Secret Agent. I had looked for a plugin to do that some time ago and couldn't find one. Now I have!
- Revisor 13y agoYou're welcome. A direct link is here: https://www.dephormation.org.uk/?page=81 https://www.dephormation.org.uk/?page=81 Just bear in mind the default installation can break some pages (Soundcloud) or worsen your user experience (many web sites, Google, Wikipedia or Ars Technica among others, redirect you to the mobile version if you have a certain user agent).
- unhush 13y agoThe reasons for not using a blacklist in Privacy Badger were philosophical, not technical. I agree it would be more convenient to ship with a blacklist but hopefully the learning algorithm works well enough to be almost-equivalent. > Btw. what is the point of Privacy Badger without the Do Not Track header? Not sure I understand. Privacy Badger Alpha currently sets the Do Not Track header on all requests.
- throwawayaway 13y agoOK I have reached saturation point with all these plugins. I value the work that the eff are doing. I think a comparison page on wikipedia is a good idea, who agrees? for example: https://en.wikipedia.org/wiki/FTP_clients https://en.wikipedia.org/wiki/FTP_clients https://en.wikipedia.org/wiki/Comparison_of_numerical_analysis_software https://en.wikipedia.org/wiki/Comparison_of_numerical_analys...
- handsomeransoms 13y agoThat's a great idea! I would be willing to help, and could probably find some others to help too!
- throwawayaway 13y agohttps://en.wikipedia.org/wiki/User_talk:Tootsestes/Comparison_of_web_browsers_privacy_extensions https://en.wikipedia.org/wiki/User_talk:Tootsestes/Compariso... let's go!
- mike-cardwell 13y agoSo this addon just blocks some third party cookies? I already have third party cookies disabled in my Firefox settings. Does that make this plugin useless to me? Wasn't there already plans to "block" third party cookies from being delivered as standard anyway, when the top level site domain changes?
- noisy_boy 13y agoI have third party cookies blocked as well in Firefox settings - I see this error when I click on the badger icon in the toolbar: "Your cookie preferences are changed from the defaults. This may reduce the effectiveness of Privacy Badger." Probably if all third-party cookies are blocked, then Badger doesn't have anything to work with.
- unhush 13y agoYes, the alpha version (what we just launched) only works on third-party cookies, so the heuristic blocking algorithm doesn't do anything if you block 3rd party cookies entirely. We plan to add detection of other tracking methods (Flash cookies, local storage, fingerprinting, etc.) as time goes on. More info in the Firefox version's README: https://github.com/EFForg/privacybadgerfirefox/blob/eb1055c44d9a27fa50b63e73ae328309366da59d/README.md https://github.com/EFForg/privacybadgerfirefox/blob/eb1055c4...
- noisy_boy 13y agoThanks for clarifying. This is a much needed initiative and your work is greatly appreciated. Happy to see my donations hard at work :)
- gavinpc 13y agoI have all cookies blocked except for the domains that I whitelist (where I need to login). This is built into all browsers (AFAIK). Why not just use that feature? What am I missing here?
- scrollaway 13y agoI have to say, I love that the EFF is doing this. No more wondering about some of the classic privacy extensions' ulterior motives. Having "one extension to rule them all", built by the EFF, is excellent. On top of that, no more conflicts between them either (and disabling each and every one of them whenever you get a loading issue on some site is frustrating!) I fully intend to contribute to my browser's extension's repository. I hope other developers on HN will join me.
- matt-attack 13y ago> I fully intend to contribute to The EFF. I hope other developers on HN will join me. Fixed that for you :)
- ASneakyFox 13y agoIs this bassicaly just adblock with just the anti tracking list enabled?
- bitbiter 13y agoFrom their main page[1]: > Does Privacy Badger contain a "black list" of blocked sites? > No, unlike other blocking tools like AdBlock Plus, we have not made decisions about which sites to block, but rather about which behavior is objectionable. Domains will only be blocked or screened if the Privacy Badger code inside your browser actually observes the domain collecting unique identifiers after it was sent a Do Not Track message. Privacy Badger does contain a whitelist of some sites that are known to provide essential third party resources; those sites show up as yellow and have their cookies blocked rather than being blocked entirely. This is a compromise with practicality, and in the long term we hope to phase out the whitelist as these third parties begin to explicitly commit to respecting Do Not Track. [1]: https://www.eff.org/privacybadger https://www.eff.org/privacybadger
- jstalin 13y agoI currently run adblock edge with the regular easy list, privacy list, and social blocking list. How is this plugin different?
- gorhill 13y agoAs part of my project, I like to benchmark regularly privacy enhancing extensions ("blockers") for Chromium-based browsers. So I took the opportunity to run one of my key benchmark this morning. [1] The results are meant for a github page, but I decided to present them here, and I reformatted specifically to be HN friendly (hopefully). In short, any of the following blockers help a lot against no blocker at all. Some are less likely to break web pages, while some other are more likely, and every users have their own requirements when it comes to striking balance between privacy and convenience. This is for information purpose only, not to make a statement that one is better than the other. With the proper information, people can make an informed choice according to their own prerogatives. I ordered the list by the amount of distinct domains which are "touched". I figure the more distinct domains are touched, the more metadata is leaked to different parties. The format of the results is n / N, where n is the number of distinct 3rd-party domains, and N is the total number of distinct domains. "3rd-party" is from a DB-less machine point of view, i.e. if a domain name differs from the one of the URL of the page, it is deemed 3rd-party. Despite this caveat, I think this still allows to compare blockers between themselves for the same benchmark ran inside the same narrow time frame. Benefit to the users: It's nice to see privacy becoming more and more a top issue and more and more choice to address this particular problem. So here: No blocker Domains: 420 / 421 Hosts: 641 / 720 Scripts: 518 / 641 Outbound cookies: 263 / 341 Net requests: 2,079 / 2,849 Privacy Badger 2014.5.1 (BETA) Domains: 192 / 193 Hosts: 299 / 381 Scripts: 334 / 455 Outbound cookies: 52 / 115 Net requests: 1,340 / 2,176 Disconnect 5.17 Domains: 93 / 94 Hosts: 171 / 248 Scripts: 262 / 385 Outbound cookies: 19 / 83 Net requests: 1,124 / 1,936 HTTPSB 0.9 Allow-All/Block-Exceptionally Domains: 54 / 55 Hosts: 101 / 153 Scripts: 169 / 265 Outbound cookies: 2 / 43 Net requests: 930 / 1,648 Adblock Plus 1.7.4 Domains: 54 / 55 Hosts: 97 / 149 Scripts: 177 / 272 Outbound cookies: 1 / 33 Net requests: 913 / 1,612 Ghostery 5.2.1 Domains: 52 / 53 Hosts: 99 / 160 Scripts: 173 / 286 Outbound cookies: 8 / 47 Net requests: 966 / 1,722 HTTPSB 0.9 Block-All/Allow-Exceptionally Domains: 21 / 22 Hosts: 49 / 75 Scripts: 0 / 0 Outbound cookies: 0 / 0 Net requests: 680 / 1,199 [1] https://github.com/gorhill/httpswitchboard/wiki/Comparative-benchmarks-against-widely-used-blockers:-Top-15-Most-Popular-News-Websites https://github.com/gorhill/httpswitchboard/wiki/Comparative-...
- smoyer 13y agoI installed the plug-in and went to three sites I know contain tracking code. Privacy Badger tells me "Could not detect any tracking cookies." ... Am I missing something?
- aspidistra 13y agoMaybe it's a bug. FTA: This is an alpha release; we've been using it internally and don't think it's too buggy. But we're looking for intrepid users to try it out and let us know before we encourage millions of people to install it. If you find bugs, you can file them on github against either the Firefox or Chrome repos as appropriate. https://github.com/EFForg/privacybadgerfirefox/issues https://github.com/EFForg/privacybadgerfirefox/issues https://github.com/EFForg/privacybadgerchrome/issues https://github.com/EFForg/privacybadgerchrome/issues
- unhush 13y agoDo you have other extensions installed that are already blocking trackers? (NoScript, for instance.) If so, Privacy Badger shows only the ones that they've missed.
- mbrownnyc 13y agoHappy see an alternate to Ghostery that isn't run by an advertising company.
- hackuser 13y agoYou might also be interested in Disconnect. https://disconnect.me/ https://disconnect.me/
- gorhill 13y agoI wish I had EFF's clout behind my work too[1]. In the last few months, I have been completely dedicated to write an extension which completely informs the user about what a web page does, and gives the user full control over what web sites do in his/her browser. Spent hours after hours at not only making it work, but also making it work efficiently (wrote custom ABP engine from scratch which doesn't suffer the real one's abuse of memory/CPU), and yet barely anyone is noticing it. EFF is also one of the recipient I suggest for people who really want to donate something for my work. In any case, an important warning concerning any extension which modifies HTTP headers on Chromium-based browsers: only one extension is allowed to modify the HTTP headers[2], and since EFF's badger does modify outbound request headers, it will break any previously installed extension which relies on also modifying these headers to work properly. This means mine[1] is incompatible, one of the two extensions won't be able to do what it says it does. This applies for any other extension modifying outbound HTTP headers. [1] https://github.com/gorhill/httpswitchboard#http-switchboard-for-chromium https://github.com/gorhill/httpswitchboard#http-switchboard-... [2] https://developer.chrome.com/extensions/webRequest#implementation https://developer.chrome.com/extensions/webRequest#implement...
- losvedir 13y agoSorry, that sounds frustrating. I just installed your extension and it looks pretty slick so far! I had been using RequestPolicy, CookieMonster, and NoScript on Firefox to do something similar, but wasn't aware of something like RequestPolicy for Chrome. Your extension fits the bill nicely. Couple questions: * Your documentation says "Efficient blacklisting ... javascript won't execute". Is this because you prevent the request altogether or do you somehow allow the Javascript to be fetched but then sandbox it or something? The latter seems brittle and prone to issues (tptacek's warnings about security/javascript in the browser come to mind). * The control panel seems to let me block scripts from the domain I'm actually on (so, not a 3rd party request). Does this include inline script tags in the HTML? Obtrusive javascript via "onclick=..."? Last I checked, I thought Chrome didn't give you hooks to be able to stop, with an extension, the evaluation of scripts. In fact, that's why I've been using Firefox w/ NoScript, since I didn't think Chrome could match it. Is that not the case? * When I search Google (but no other page), it seems to flash and reload since installing the script. What's that? Thanks for your hard work on this! I appreciate it a lot.
- cs702 13y agoI love it! By far the most important thing about Privacy Badger is that it's backed and controlled by the EFF, instead of some individual or business that might be tempted in the future to betray users for profits.[1] -- [1] For example, consider what happened with Adblock Plus. For years, it blocked all ads, but then in 2011 its developer announced it would allow "acceptable ads" by advertisers who had partnered with Adblock Plus. (For the details, see http://en.wikipedia.org/wiki/Adblock_Plus#Controversy_over_ad_filtering_and_ad_whitelisting http://en.wikipedia.org/wiki/Adblock_Plus#Controversy_over_a... ) The EFF is extremely unlikely ever to do something like that.
- hackuser 13y agoThe EFF is doing something similar, though I don't know if their standards are different than Adblock Plus': "Advertisers and other third-party domains can unblock themselves in Privacy Badger by making a strong commitment to respect Do Not Track requests."
- aspidistra 13y agoTo be fair to EFF, it is explicit about what it considers that strong commitment to be: publishing this DNT policy notice on the domain: https://www.eff.org/dnt-policy https://www.eff.org/dnt-policy Quote: What does the dnt-policy.txt promise mean? Posting the dnt-policy.txt file makes a promise to the users who interact with their domain. We [EFF] believe it would be a false and misleading trade practice to post the policy without the intent to comply in good faith. However, EFF is not in a position to enforce this promise or monitor compliance.
- unhush 13y agoThere is code in Privacy Badger that checks whether a site has publicly posted a statement of compliance with DNT before blocking it. If they do and then violate that commitment, we have a record of it and can call them out on it.
- DerpDerpDerp 13y agoCan you still configure the plugin (manually) to not trust such sites? I don't want it to be a negotiation between the EFF and a website as to the state of my privacy - I want the final say in who is going to be trusted.
- ralfn 13y agoI'm going to drown in downvotes likely, because this will go against popular opinion. But i have to speak out about this nonsense: most adserving scripts aren't violating your privacy! People keep confusing the adserving/retargeting sector with the identity-sector (Google, Facebook). Identity (centralized) vs anonymous (or decentralized) is an important debate. But the adserving industry are not picking sides in that debate. they don't want your name, and they are not keeping any data any milisecond longer than required, because it's all low-margin: costs matter a lot. People want all their content for free. People don't want annoying popups all the time. So when you look at some product, you get a cookie. That product-id and the cookie-id (that refers to your browser, not you) go into a typical cassandra or redis cluster for about 30 days. Then they are deleted. End result: (1) your content is free (2) you are not drowning in ads (3) your privacy was not violated. Nobody in _this_ sector wants to store your personal stuff. People should be concerned about what identity-providers (like Google or Facebook) do with your information. And people should be very wary of identity-providers where you are not the customer. But pure adserving companies, the ones targetted with this tool, were never messing with your privacy in the first place. All tools like this do, is put websites out of bussiness. Can the intelligent people in HN please start getting more informed about the difference between these two sectors? Retargeting-sector ==> Be anonymous, see few ads, get free content. Low-margin, technology-driven. Identity-sector ==> Give all your info, see lots of ads, spam your friends. High-margin, social-life-extortion-driven. And maybe, not freak out so much about 'retargeting'. Retargeting is fine: its why so much of the internet is free. It funds many YC companies (like Reddit). Just don't ever deal with identity providers who also sell ads. But that's about 10 scripts of the thousands that are blocked by this tool.
- aspidistra 13y ago> People keep confusing the adserving/retargeting sector with the identity-sector (Google, Facebook). Can you blame them when the latter keep buying the former? Google bought Doubleclick. Twitter bought MoPub. Facebook bought Atlas. And so on...
- ralfn 13y agoI don't blame them, but the sector is much bigger than just the identity-players.
- sequoia 13y agoFrom FAQ: "Privacy Badger is a browser-add on tool that analyzes sites to detect and disallow content that tracks you in an objectionable, non-consensual manner." If this is for average users, something like "Privacy badger stops advertizers from secretly tracking your movements and activities online" be better. "browser-add[sic] on tool that analyzes sites to detect" etc. etc. is too complicated, people won't read it IMO. "When you visit websites, your copy of Privacy Badger keeps note of the "third party" domains that embed images, scripts and advertising in the pages you visit. If a third party server appears to be tracking you without permission, by using uniquely identifying cookies to collect a record of the pages you visit across multiple sites, Privacy Badger will automatically disallow content from that third party tracker." Words you probably shouldn't use for a layperson friendly explanation: embed, script, server, disallow, "third party" (without explaining precisely what you mean in this context). The top question on the should be broken out into a "how does it work (generally speaking)" and "how does it work (more technical)." I'm afraid people will get stuck on that say "this is too technical" and not read the rest.
- sequoia 13y ago"When you see an ad, the ad sees you" this is excellent!! It succinctly explains the problem in a layperson friendly way. "When you see an ad, the ad sees you. When the advertiser 'sees' you it sees what site you are on when you view the ad. This information can be used to build a profile about you: where you shop, what blog or news sites you read, what forums you post on, etc.. Privacy Badger stops your browser from requesting the ads, so the advertiser never 'sees' what sites you're visiting. When you see an ad, the ad sees you... Privacy badger stops you from seeing the ad and stops the ad from seeing you!!" Ideally you'd just copy this: http://donttrack.us/ http://donttrack.us/ but specifically for ads.
- unhush 13y agoHi, I'm the main author of Privacy Badger's Firefox version. You are 100% right; I'll point this out to the text authors. On the other hand, EFF's fanbase is generally very technical compared to the average person and I'm sometimes afraid of coming off as imprecise or belittling to them. Striking the balance is hard.
- charonn0 13y agoIf I've already got NoScript, ABP, and Ghostery will this addon make any difference?
- canvia 13y agoAre there any extensions that will block flash cookies (LSOs) instead of allowing them and deleting after each browser session? http://www.wired.com/2009/08/you-deleted-your-cookies-think-again/ http://www.wired.com/2009/08/you-deleted-your-cookies-think-... One current option: https://addons.mozilla.org/en-US/firefox/addon/betterprivacy/ https://addons.mozilla.org/en-US/firefox/addon/betterprivacy...
- angry-hacker 13y agoWhy extension if you can disable the local shared objects (LSO cookies) entirely from the flash settings? Or just use click to play to activate flash on your browser, at least then they can't be set anywhere in the background.
- SudoNick 13y agoIn order to be effective against the numerous tracking techniques that are in use, the extension MUST block requests. If you aren't breaking many popular websites as a result of blocking their third party requests then it is your own privacy that gets broken. So this concerns me: "In some cases a third-party domain provides some important aspect of a page's functionality, such as embedded maps, images, or fonts. In those cases, Privacy Badger will allow connections to the third party but will screen out its tracking cookies."
- unhush 13y agoTo clarify, those cases where we block cookies but not requests entirely are the sites on this whitelist: https://www.eff.org/files/cookieblocklist.txt https://www.eff.org/files/cookieblocklist.txt This pull request will also apply the whitelisting to subdomains of the domains on the whitelist: https://github.com/EFForg/privacybadgerfirefox/pull/63 https://github.com/EFForg/privacybadgerfirefox/pull/63. Unfortunately blocking all those sites and making users whitelist them manually is a lot of work for most users. So we ship a whitelist.
- unhush 13y agoPerhaps now is a good time to mention that if you want to work on projects like Privacy Badger with EFF, we're hiring for a Staff Technologist: https://www.eff.org/opportunities/jobs/staff-technologist https://www.eff.org/opportunities/jobs/staff-technologist. The role is a mix of software engineering, doing security/privacy research, pressuring large internet companies and standards groups to not be evil, and teaching lawyers/reporters about technology issues. It's overall a fun job. I wrote most of Privacy Badger Firefox with help from Mozilla folks in the last two months, and it's very satisfying to see people using and reporting bugs in the software that I made almost immediately after launch. :)
- mgreg 13y agoIt's great to see additional attention on privacy while browsing from the desktop. It does feel, however, a little like we're fighting yesterday's war. With so much browsing / internet usage taking place on mobiles it would seem to be much more important (or at least _as_ important) to provide privacy to mobile browsers. Given the limited ability to impact the way mobile browsers work (especially on iOS) I wonder if we'll see any real solution here?