UnGoogled Chromium: Chromium with enhanced privacy, control and transparency
github.com
github.com
Skipping testing in IE is one thing. Skipping testing in Firefox is a sin.
[0] Unnecessarily, because cross-browser compatibility isn't hard, simply include CSS prefixes besides -webkit and use standardized JS APIs.
[1] Internet Explorer, a term for a closed-source browser that creates non-standard APIs that developers jump on, forcing either users to use that browser, or other browsers to implement the non-standard APIs too.
Fudging the user agent however, allows that website to work perfectly fine.
Not testing in IE is one thing. Presenting an nonintrusive message warning you don't test in IE is another. Paying money to advertise your website, then, when I click your link, greeting me with a condescending "IE Users are idiots" type message that doesn't let me proceed, doesn't make me buy your product.
I visited their website and was, like in a lot of cases where they assume ARMv7 means I must be using a mobile device, redirected to the mobile site.
That's not the stupid part, though (just annoying). These guys took it one step further and had their mobile website decide that I was in fact not on mobile, and then they proceeded to throw me into a redirect loop between the desktop and mobile site. Talk about messing up with browser detection.
I wrote an e-mail to report the issue to the people in charge of the site, and you know what they tell me? Oh, "we forwarded your message to our web developers but they said that this doesn't happen". Wow, ok, "this doesn't happen". Guess I must be hallucinating, then? Well, jokes on them 'cause if they hire people who break their website so that I can't check the opening hours, guess where I'll be shopping? Not at their store, that's for sure.
I have Chrome on my Surface. I choose to use Edge instead because Chrome is unusable without my Type Cover plugged in, and I'm not doing that while laying on the couch.
Hey Google, want me to use Chrome on my Surface? Then give me the Android version of Chrome running in a container. Phone UI, please.
Windows tablets were my only option. An Android tablet (or an iPad) might work fine in the car, but it would make a terrible laptop in the hotel room, and a conventional laptop would be unusable in the car.
After my road trip, my Surface found continued use as my couch computer, effectively replacing my phone. Honestly, as long as I have a web browser that works I don't need much else. Edge works; it might be more minimalistic than I like, but the vast majority of what I want to do with a computer on my couch is satisfied by Edge. Oh, and the Facebook app for Windows 10 is awesome. It's everything I've wanted out of the Android app, which has been a constant disappointment for me.
On the other side, developers can spend more time developing features instead of fixing IE compatibility bugs.
Pun intended? But seriously, whenever I see one of these browser-blockers (and it seems Opera gets hit too), I just leave the site and never come back. Chances are, your site is not unique and I'll find what I need somewhere else.
developers can spend more time developing features
IMHO, those are "features" which no one really cares about. Stop messing around with fancy CSS and JS, spend the time developing a simple site that almost naturally works in IE too.
I agree that targeting of Edge browsers is ridiculous since it's keep current, on the other hand for IE and if the site is non-commercial/personal (commercial sites should really try to be compatible on as many browsers as they can) I don't really blame them if they're wanting to use modern web standards. Microsoft has abandoned feature updates to IE, and sadly only made Edge available to W10 users.
Flexbox in CSS is one example. It was made to simplify the creation of page layouts and content flow and includes various features that were sought-after for a long-time that require hacky or more complex solutions otherwise. The majority of its bugs, or just plain missing features are found in IE10-11 (and absent completely in earlier versions). Either creators design the site to entirely compensate for IE and loose that flexibility (pun not intended), find some Javascript polyfill that actually works/fixes such bugs, or just present some message to users for unsupported browsers (not that it needs to necessarily block the page though). It's just one of several useful features that make things far easier but lacks full/partial/any support in IE.
https://github.com/mozilla/togetherjs/commit/ced91da4bb53bea...
Clue: what is the problem with this code?
I filed an issue on the Chromium bug tracker, they assigned someone to look into it, and of course, nothing has been said since.
To this day, and for years, I continue to receive these messages from Google sites informing me to upgrade to Chrome. I've even had them pop-up on Chromium.
Obviously, I don't have Chrome, since my issue is them pestering me to install Chrome. Which I'm not going to do.
On the other hand, if Google wants to prevent their reputation from sinking to the level of "install the Ask Toolbar", one of the Googlers on the Chromium bug tracker will see that it is dealt with.
A large web app is almost guaranteed to run into one of Firefox's many long-open bugs. But the biggest reason in my experience is performance. Gecko's rendering engine is poorly-optimized, to the point where I regularly see a DOM modification take 10ms in Chrome (easily within a single frame) and 1000ms in Firefox (locks the UI and causes the page to flash white).
(We have some enormous architectural changes inbound which should help, but I'd still love to make sure we have a test to prevent regressing)
Here's a product that I'm working on
https://www.ux-app.com/dev/editor?m=trial
In Chrome it's buttery smooth on any decent computer made in the past 5 or 6 years. In Firefox it's usable on a powerful computer, but notably worse than Chrome.
On an under powered laptop Chrome is still very usable, not quite 60fps, but probably 30-40fps on moderately complex designs.
Firefox is a choppy mess on low end hardware.
This is a recurring issue with Firefox. It's just ok for regular web browsing, and it's a hot mess for any web app that needs to do any moderately taxing DOM manipulation.
As much as I love Firefox, it's just leagues behind Chrome in regard to performance.
Having different browsers compete on things like this and then having the better technology become standardized and implemented in multiple browsers seems like a fairly positive outcome.
[0] https://wiki.mozilla.org/WebExtensions
[1] https://addons.mozilla.org/en-US/firefox/addon/chrome-store-...
http://www.theregister.co.uk/2016/03/21/microsoft_edge_exten...
You mean like when I spent 30 minutes figuring out that text area in chrome is counting new line as 1 letter and firefox is counting it as two ?
They should both count it as one now, for what it's worth.
By most measures, an equal or larger number of people use IE than Firefox.
On that note - can you tell us more about the project? ie. if you plan on keeping this updated long terms (i've watched a lot of promising chromium forks fade after an initial big splash), what your plans are, if you'll you accept contributions, how the binary distributions are built so we can verify the checksums, if you can tag the Chromium releases from Google so they can be verified, etc.
I've had the idea of a chromium fork with privacy enhancements in the back of my mind for a while now (turns out a lot of people have) specifically to replace Tor Browser and/or have a lighter browser (without canvas, webgl, webrtc etc.) with better defaults (ie. no hardware access, location, notifications, cookies, history, etc.) for opening links, private browsing etc[1].
This may be a good base to work on - assuming you want to go beyond just "de-googlify"
[1] I think there is a real need for an alternate browser that is lightweight[2] and has stricter privacy and security controls - with proper user segregation (ie. you really don't want to open random links from social media in the same browser session as where you're logging into your primary accounts).
[2] ie. do to Chrome/Firefox what Firefox originally did to Netscape - and Chrome would be the better foundation to work on
Please do not do this. Webgl and Webrtc are fundamental technologies needed to efficiently do basic activities like process an image or send sound data to another user.
I am all for a "lighter" browser, by removing UI, removing dev tools, etc. Get rid of the stuff that's not required to make a web page work well. But WebGL and WebRTC are cornerstone technologies for the web to thrive. WebRTC is critical for allowing open source software to thrive in particular (allows apps that don't need a central server) and WebGL is critical in particular for web software to compete in the AR/VR age. We need 100% browser support on these two APIs, and we need it yesterday.
I realize these technologies are not currently doing anything for you. I sympathize. But we need them in browsers now so that we can use them in 10 years.
Please, please, please jetsam other parts of the ship before you cut those features.
>fundamental technologies
>basic activities
>process an image or send sound data to another user.
We must live in different worlds, those are not "basic" or "fundamental" to me. I'm not sure I've ever used either.
>the AR/VR age
You're overstating how important these technologies are. Maybe in 10 years but only time will tell.
That kind of infrastructure is crucial to the freedom of information and therefore the freedom of global citizens. You will not realize we need it until it's too late.
The revolution will not be televised, it will not be in your news feed, it will happen in the streets and in the minds of citizens, and we need to prepare ourselves with the proper tools for that time, because it is coming sooner than you think.
Also, what you described is certainly a good thing. But I'm pretty sure it doesn't _have to_ be done in a browser.
Hold your horses! The introduction of dev tools was one of the best things to happen to browsers. Removing them would take away opportunity from a lot of people in learning web development, and would also lead to websites having more bugs.
My mom, like yours, would have no use for dev tools -- because she's just not interested. And neither would my brother, but my grandma would have loved learning about this stuff if she had lived long enough, and my kids have discovered this "secret hacker mode" all on their own and are delighted.
But for fun and laughs I saved js-generated source of a pretty big web page, opened it, and then pressed CTRL-U. It took 50 seconds to generate and render the source view. No wonder...
> document.getElementsByTagName('*').length
< 956632
(should be fun to go deeper and save this html, and then go ctrl+u on that)
edit: Tried it and it's been choking on the next "level" for the past 9 minutes. The tab is at over 1.5GB memory, I'm going to kill it.
Some time ago I tried Lynx and I liked the idea, It was waay simpler that I'd like, but in the other hand I feel that interfaces made for web are always crippled compared with desktop interfaces (from G docs vs MS office, up to clara.io compared to blender).
For web browsing I think that something between a browser and Lynx is something that I would use, most of the time I am interested in the content more than the aesthetics or the pixel perfect alignment of visuals... and if I was interested in an application (that requires the newest tech in browsers) most of the time there is a better tool for desktop.
6 years ago many people didn't even knew what web browsers were (What is a Browser? https://www.youtube.com/watch?v=o4MwTvtyrUQ)
If you get right down to it, what you need to make a web page work is HTML. That's it - WebGL and WebRTC are interesting, but the web isn't going to die if one browser doesn't include them. Lynx still works fine without them, after all.
I'm seeing a lot of alarmism from people who I'm guessing have vested interest in those products, completely forgetting that Chrome, Firefox, Explorer and Safari (in no particular order) are what drive the current state of the modern browser.
[1] https://www.reddit.com/r/chrome/comments/1xsxjv/best_browser...
I then proceed onto the settings app, into 'accounts'. There, I tap 'Google' and lo and behold: App-data, Calendar, Contacts, Google Fit Data and People details are all ticked to sync.
I turn them off.
Then I open the default browser. It logs me into Google, by default. I have to explicitly tell it not to.
Google really really wants users to be logged in. That is my experience anyway.
We are building one [1]. Contributions are welcome! In the meanwhile, the ungoogled-chromium project in combination with uMatrix is I think a great way to transition away from Chromium.
They really restructured their whole browser several years ago specifically to switch to the chromium platform. I apologize I didn't mean to butt in I was just curious.
Feel free to make an issue (for questions, suggestions, or bug reports) or a pull request anytime. I might respond to a few more comments here before calling it a day.
That seemed pretty random, and not related to the ultimate goal of the project. Are there other normal features that are disabled, that don't relate to Google at all?
BTW, how easy is it to add FF + noscript type of features to chrome?
--- Only enable JS on whitelist websites - all others are default disable unless user explicitly temporary or permanently enable it.
Settings->Advanced->Privacy->Content: Cookies->Keep until quit + exceptions you choose. Javascript->Deny all + exceptions you choose.
When you browse there is a little icon in the address bar to whitelist a site. It is a bit of a pain at first but it makes things a lot safer. When you go incognito it will forget which sites you whitelisted at session end, so you are not enabling a site forever.
I can also recommend the EFF Privacy Badger and the Cross Domain Request Filter extensions. CDRF needs to be updated to work in whitelist mode instead of blacklist mode, but it is still pretty cool. I also like Poper Blocker, but their telemetry mode is wrong.
I'd really like an in-browser firewall which also blocked extensions by default. Something with an inspectable rule set.
See also: Whitelist Manager, comes with source code.
https://chrome.google.com/webstore/detail/cross-domain-reque...
https://chrome.google.com/webstore/detail/privacy-badger/pke...
https://chrome.google.com/webstore/detail/poper-blocker/bkkb...
https://chrome.google.com/webstore/detail/whitelist-manager/... https://github.com/unindented/whitelist-manager
https://github.com/maximelebreton/quick-javascript-switcher
https://chrome.google.com/webstore/detail/quick-javascript-s...
The last time I used Firefox on mobile, it didn't integrate well with the phone UI. It felt clunky, the fonts were bad, and the viewport was wrong on many websites.
I feel like Mozilla would do the most good in the world by spending more effort on a mobile browser. Mobile Chrome is flat out disgusting and abhorrent, but I haven't found anything else that's remotely as performant. It just sucks that Google refuses to allow extensions to protect their ad revenue.
Are there any good alternative browsers that block shitty, intrusive, and entirely irrelevant mobile ads? Are they open source?
It's not perfect. There are deviations from the usual "Material Design" UI standards. Some sites don't render properly. It's slower. But it's worth it to me.
Do you have more information on this?
I tried using FF on Android for a while. If I saw a page with a link to a YouTube video, the fastest way for me to watch the video was 1) Copy the link to the clipboard. 2) Open Chrome and paste it in 3) Click the link.
Lots of apps are bad actors like this - Facebook, Twitter, etc. In those cases, when you click a link in a post or tweet, you go there in their own built-in browser, trying to keep you in their app. But, they give you the ability to turn it off. It's in the app settings if you look.
Firefox doesn't have this. You have to wait until the page is fully loaded, and then decide if it's worth your trouble to open it in the native app now. Most of the time it isn't, it would have been faster in the native app, but you're there now, so eh. For YouTube, it usually is. But it's just so hair-pullingly frustrating.
Also you can setup your own ad blocker DNS server with [1] PiHole (works on any linux machine)
Another option is [2]NetGuard firewall with a host file
There're options, nobody likes ads
P.S. All these projects are open source.
[0] https://block-this.com/ [1] https://pi-hole.net/ [2] https://github.com/M66B/NetGuard/blob/master/ADBLOCKING.md
Note that one of the recent updates [4] introduces ads for the free version. But not if you buy any of the pro features. Seems a fair trade, plus it's open source (which makes me slightly happier about routing all network traffic through it)
[1] https://play.google.com/store/apps/details?id=eu.faircode.ne... [2] https://github.com/M66B/NetGuard/releases [3] https://github.com/M66B/NetGuard/blob/master/ADBLOCKING.md [4] https://github.com/M66B/NetGuard/releases/tag/2.45
IMHO Chrome has a better track record than Firefox when it comes to security issues, but Firefox has better privacy.
Blocking 3rd party ads and trackers really speeds things up!
https://it.slashdot.org/submission/5553519/pwn2own-2016-wont...
The worst Firefox might do is get your machine pwned.
Chrome is the one running any x86 binary the website presents it with, only trying to run a static verification that it won't do anything evil.
Chrome is far more at risk of pwning you (and NaCl sandbox breakouts have been quite common).
Point is, Chrome falls every year at Pwn2Own just like every other browser, but only Firefox has been excluded because it's too easy.
Looking through the previous year's results, it doesn't seem like firefox has done especially poorly?
And as noted in https://redd.it/45epd7, firefox multiprocess is sandboxed, and it does have security features that other browsers don't have
so... IMO it doesn't seem like the reason given is quite genuine?
How does this play with the HSTS preload list? That'd be quite the baby to throw out with the bathwater.
edit: well, I don't see anything like "transport_security_state_static.json" in this list here, so maybe it's fine: https://github.com/Eloston/ungoogled-chromium/blob/master/re...
edit2: The preload list seems to be excluded from domain substitution explicitly. Yay! https://github.com/Eloston/ungoogled-chromium/blob/4bbfff447...
While many may not like the uses of that event, it taints what otherwise could have been a "purely about privacy" fork of Chromium with non-privacy opinions.
If you have the computing resources, you can easily take out the patch that does the "wishlist" changes you don't want.
My ideal browser has zero persistence and each tab maintains its own cookies. Links opened as new tabs would share the parent's cookie jar, but separate tabs loaded to the same page could both be logged in at the same time.
There are stealth techniques such as browser cache hits, browser configuration fingerprinting, and even system clock drift, that can track you beyond cookies.
You would need a separate browser profile or even a separate OS for each tab (see Qubes OS) to be on the safe side.
> Create an Account Password (You will use this to log in to the browser to activate it)
Uhm, no.
> Each group of tabs, separated by color, is its own browsing session with its own cookie jar
Yes!
> Log in to one web site with many accounts simultaneously
Yes!
> Use with Mac OS X or Windows
No!
Would need a Linux build as well (actually that's the only one I need). Otherwise, looks cool though and will be keeping an eye on it. Thanks for sharing!
Those days it was all technical, google was perceived first as technically proficient and their agenda was to produce a fast and efficient browser. Many people could and did align with that.
Now there are too many question marks about Google's motives and agendas and Chrome does not feel like a technical achievement, it feels burdened by all these agendas.
Firefox is supposed to be the default go to when in doubt but why do you need such a large coporation to develop a fast and lean browser and here too there appears to be conflicting actions and agendas.
Now more than ever we need clean open source projects with no agendas but because of growing complexity its becoming increasingly impossible for small groups to do, and I think we have not evolved open source structures to deal with this yet.
Started trying out alternative browsers a while ago--vimb, dwb, and luakit--and enjoyed their snappiness and customizability.
Recently, however, I discovered uzbl and fell in love. It feels like everthing a shell for the web should be.
I am unsure whether I should be worried about security pr something though. Would love to hear others' input!
> a freeware web browser, and an implementation of Chromium by SRWare of Germany. It primarily aims to eliminate usage tracking and other privacy-compromising functionality that the Google Chrome browser includes. (https://en.wikipedia.org/wiki/SRWare_Iron)
First released 8 years ago: https://www.srware.net/en/software_srware_iron.php
One of my biggest gripes with Chrome is the inability to stop a rogue site from playing audio (on top of the music I'm listening to in another tab). CNN is one of the worst, as soon as I find the freaking video on the page and try to pause/mute it, the video controls slide away. Why can't Chrome allow me to just turn off audio on that tab? I have assumed Google doesn't give us that because it will interfere with their advertising or something.
(maybe there is an extension that will help? I haven't found one)
Well this feature is built into Chrome. Just right click the rogue tab and click "Mute Tab"
I'm not finding anything about that in repo readme page. This looks odd and suspicious. Because it's even blocks requests there -> http://imgur.com/a/UnMu8
Edit: see https://github.com/Eloston/ungoogled-chromium/blob/8dd86477d...
- doubleclick([A-Za-z\-]*)\.net#60u613cl1c4\1.qjz9zk
+ doubleclick([A-Za-z\-]*)\.net#doubleclick\1.g.invalid
https://en.wikipedia.org/wiki/.invalidThe HN community really is polarized ( or so it seems ) about these data-harvesting companies and issues like privacy/transparency.
My thought then, is which group is larger here (privacy-aware vs. GooAppFace )
Either there are a lot of Google employees here on HN, or a lot of Google fanboys. Or both.
That is a very bad idea. I sympathize with the idea of the project, but please think twice before meddling in security things. See https://news.ycombinator.com/item?id=9779990
I filed an issue to explain the risks: https://github.com/Eloston/ungoogled-chromium/issues/50
Connecting to a foreign company in a country that directly threatened you with invasion and relying on that for webbrowsing is not acceptable.
There's a setting to disable SafeBrowsing in Chromium, too. You can just disable that. But force-disabling it is dangerous.
I'm not sure what your point you're trying to make with the invasion comment.
My argument is that browsers aren’t just used in private use, but also in governments, in military companies, etc.
If you rely on anything phoning home to a company that’s in the country of a potential enemy, that’s a very stupid idea. (And thanks to the Den Hague Invasion Act of 2001, even Europe knows the US doesn’t give a fuck about allies)
> Well and how would I go about that? Your suggestion doesn't make any sense because it's not viable.
Well, ask Google. It’d be viable if they had intended for an actual safety infrastructure, and published the required information to self host, and not just another way to phone home.
Error:Dependency is not satisfiable:libavcodec-ffmpeg56(>=7.2.4)|libavcodec-ffmped-extra56(>=7:2.4)
Suggestion -
The repo does not provide install instructions. For a highly not tech privacy enthusiast, I find it difficult to install for linux.
That looks like a version of libavcodec specific to one version of Ubuntu; that package will never work on Debian, another version of Ubuntu, or most non-Debian distributions.
* the other being security updates for ffmpeg
Note that many of the changes in this fork come from the Debian packaging of Chromium.
I'd expect the distro ffmpeg to not need as much updating if you're only using it for local media that you trust. But Chrome's ffmpeg has to decode media from untrusted sources so it's important that security bugs get fixed ASAP.
[1] https://security.googleblog.com/2014/01/ffmpeg-and-thousand-...
Use a better distro with a better packaging mechanism. Instead of inventing something new, use something that already exists.
Imagine a package system where you could ask to download node.js, and you'll get the latest version. And that's it.
Better yet, imagine having to build a package from source and installing it. You could do it by hand, leaving orphan files all over your system. Or you could write a PKGBUILD that handles installing dependencies, building, and packaging, all in one go.
That's what running Arch feels like. Being able to install fresh popular packages, and being able to easily package your own. Try it sometime.
Depends what you classify as criteria for a "good packaging system". Arch didn't even sign their packages until a few years ago, and the build system for their packages is not very good IMO. What makes Arch great is the fact that they have a large library of very up to date packages. Personally (though I'm biased) I like openSUSE's package manager (zypper). It's an enterprise-grade package manager that supports things like patterns and can differentiate between security updates and regular updates. It also supports delta RPMs for patching.
> Better yet, imagine having to build a package from source and installing it. You could do it by hand, leaving orphan files all over your system. Or you could write a PKGBUILD that handles installing dependencies, building, and packaging, all in one go.
rpmbuild has this. And there's also OBS (the open build system) which was originally written by the openSUSE community but supports many other distributions (including Arch as well as Fedora, Debian and the other usual suspects).
https://lwn.net/Articles/676664/ https://wiki.debian.org/DontBreakDebian
The nice compromise that I've found is Ubuntu Mate, which seems to do away with Ubuntu's Bloat and Unity crapness, but still maintaining a Debian distro that operates properly (everything comes upstream from Ubuntu repo's)
Just something to consider. People might have some other opinions on Mint which would be good to hear too.
Windows desktop apps work great without tabs. Could life be better without tabs?
[1] https://github.com/Eloston/ungoogled-chromium/blob/master/FA...
[1] Chromium bug tracker: https://bugs.chromium.org/p/chromium/issues/list [2] Chromium code reviews: https://codereview.chromium.org/ [3] Chromium development mailing lists: https://www.chromium.org/developers/technical-discussion-gro...
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=500922
Any web page can listen to your microphone if you allow it to, and the code for it can be downloaded without your consent, even if you have JavaScript disabled, if it's embedded in the HTML code.
This part is inaccurate. See: https://bugs.chromium.org/p/chromium/issues/detail?id=500922...
> You don't have to take my word for it. Starting and stopping the hotword module is controlled by some open source code in Chromium itself [3], so while you cannot see the code inside the module, you can trust that it is not actually going to run unless you opt in.
Also:
> I hope this explanation is satisfactory. I am closing this as WontFix because it is already an opt-in feature, and Debian has already removed the component in their distribution of Chromium [2].
I've read the comments on that bug thread and I really struggle to see anything sinister that doesn't require several visits to the tinfoil haberdashery. There are problems around governance, communication and lack of respect for the priorities of the OSS community - but to see this as a failed attempt to listen to the conversations of Chromium users without their consent strikes me as verging on conspiracy thinking.
> First and foremost, while we do download the hotword module on startup, we do not activate it unless you opt in to hotwording. If you go into "chrome://settings", you will see a checkbox "Enable "Ok Google" to start a voice search". This should be unchecked by default, and if you do not check it, the hotword module will not be started.
Meanwhile, Google doesn't return results for guns in the shopping section. So I get to search a bunch of sites and call people like i'm on astalavista in 1998.
Sad Truth: both companies inject a brand of exclusionary (read: discriminatory) politics into their products. I don't trust either.
Chromium is open source, but the supported product where the developer cares about the quality of the experience is Chrome. Android is much the same, where the platform almost all apps and services target requires Google Play.
I can't expect Google to properly address my needs in either of these open source offerings, because the actual users are almost exclusively using the proprietary version.
When Google looks at what the browser needs to do, it can either make the solution proprietary or open source, and then just tell the open source users that it's unavailable unless they switch to Chrome. (See things like browser syncing, or Google Cast support.) But when Firefox implements such features, they have to do so in an open way, which is why you can run your own Firefox Sync Server.
I'd encourage you to read this document[3] detailing the differences between Chrome and Chromium instead of speculating.
[1] https://www.chromium.org/developers/design-documents/sync [2] https://codereview.chromium.org/2347503002 [3] https://chromium.googlesource.com/chromium/src/+/master/docs...
Contributing to either feels like a waste of time.
I think Chrome has a lot of interesting parts from a technological perspective. However, I think Firefox as an organization has done more for JavaScript and that community as far as fostering an open environment than any other browser maker. So providing a good browser plus fostering and growing the development community are both great things.
Another advantage is that it is not tied to some large conglomerate that is now engaged in questionable practices. That you need to rip entire parts of the code base out in this manner. This sort of thing has never been a concern with Firefox.
In general I think people ought to look at Google much more skeptically than they used to and all of the technologies that they push for. They all in some way push their agenda forward.
I've been skeptical of Google for a long time, and quit using them as much as possible since they rolled out "Don't be evil." Talk about telegraphing the punch.
A corporation with a ton of resources and a ton of people's information. Anyway I don't want to go into a rant but lately everything they do even the open source stuff is just to further their agenda and seldom to help the community.
Google started as a technology company for nerds. Remember when Google broke all "rules" when their website was a simple image, input, and two buttons?
Then they were into open standards, tech innovation, and where the company was run by engineers, and not media people (see Yahoo).
The result was a focus on UX and not design.
Unfortunately, around when Google+ came out, they decided they're done with that, and became a "company for the masses".
XMPP integration - dead Open Source apps - dead
They're back to bloat (just JS instead of animated GIFs and Flash), "beauty" over "UX", closed source apps (remember when most apps put out by Google were open source? Remember the shock that Picasso wasn't?)
That code of conduct just make it worse they were caught red handed, and I can very much understand people who completely lost their trust in the company.
Mozilla is not a club of like-minded hackers that try to keep the web livable anymore. They're a large company now with corporate salaries and expensive furniture and a prime real estate office that values advertisers over users. Firefox is their money maker.
Chromium is a Free Software version derived from a proprietary browser. The people who made that happen must have had an idealistic motivation, or otherwise it wouldn't exist.
Both browsers are libre license-wise, which is a good thing, but in my opinion Chromium is less likely to be used as a marketing stick against users, since the marketing stick version of Chromium already exist. As such using the Chromium browser is preferable for me, since the intentions behind it are likely to be more in line with a free Internet in spite of its proprietary origin.
Chrome is based on Chromium, not the other way around. It's also pretty much Chrome with changed branding and no built-in Flash (thank god!)
Thinking that google leaves Chromium alone or that it's somehow independent is naive.
1st Chrome release: 2008-09-02
1st Chromium release: Dec 17th, 2012
So even though current Chrome might be based on Chromium, Chromium was initially derived from Chrome.
That means somewhere down the line someone at Google must have suggested making a free version, probably out of enthusiasm for open source, and even though it buys Google little, the project was okay'ed.
I have no illusions about Chromium being independent, but as things are, Chromium development, in my opinion, is less commercially driven than Firefox development in spite of being a Google-driven project, allowing it to better serve its users with regards to freedom and the open web.
The main danger of Google's involvement is if Chromium would somehow outpace Chrome deployments, and them pulling the plug, but that's still very far away. And even then, due to its libre license, everything is far from lost.
> 1st Chromium release: Dec 17th, 2012
> So even though current Chrome might be based on Chromium, Chromium was initially derived from Chrome.
Not sure where you got that second date, but Chromium was definitely released the same day as Chrome: http://arstechnica.com/information-technology/2008/09/google...
But that is, quite frankly, not the case.
In other words, open-source software maintainers are under no obligation to accept outside contributions. The only freedom you are guaranteed in this respect is the freedom to start a fork.
However I'm using a pretty beefy phone whereas when I used my Moto G it wasn't quite the best browser in terms of resources however a lot has changed since then. (Like Chrome no longer having tabs integrated into the task manager. That feature was great for devices with not too much RAM and horribly buggy firmware that would unload apps prematurely. It's also very convenient to use. Maybe could have used a little bit more refinement.)
Also it's the only browser that supports my dusty old PCs. So I tend to use it on those as well.
Thanks Firefox devs.
I find that firefox is a little funky on Android though... the integration with lastpass is weird, have to copy/paste, at least site identification works now, there have been a few other oddities too... I notice a lot of sites improperly detect a lack of video support, or it may just be format that's the problem.
I tend to like/use chrome and prefer it... but I do think there's been some weird behavior in/from google... just finding out about chrome apps being killed off irks me to no end, considering it's the first actually decent write once run everywhere option. I'm guessing the recent hangouts change was because of this, as they'll likely move to electron on the desktop.
I'm glad Firefox is still an option though... I also appreciate what they've done to further the platform... Though I do chuckle a bit of how much easier web components, and even react might have come in if e4x had been implemented in other browsers.
I also like the quick sharing actions, remembering the last 3 apps used for sharing. And the local search in your history it does, avoiding roundtrips to the search engine. Although to be fair this functionality appears to work better on the desktop.
> the integration with lastpass is weird
On Android the defacto standard for password managers is to use custom keyboards. Ironically, the custom keyboard I found most usable for this purpose has been Keepass2Android [1], precisely because if it loses focus it still remembers the last account selected and I've tried both Lastpass and 1Password. Along with KeeWeb on my desktop, it's way better than Lastpass imho and free.
[1] https://play.google.com/store/apps/details?id=keepass2androi...
I agree on much you write about Firefox but unfortunately the only sane browser to use on mobile is one that automatically reflows text on zoom. The only one I know is Opera and I can't understand why no other browser implements this feature. Any other browser forces me to endlessly scroll horizontally and not zooming means that some text can be too small to read.
I tried these addons but none of them worked for me, they appear to do nothing.
* https://addons.mozilla.org/en-US/android/addon/fit-text-to-w...
* https://addons.mozilla.org/en-US/android/addon/android-text-...
I also happen to use Firefox as my daily driver on my main laptop, largely due to the Tree Style Tabs addon, which I have not seen a decent substitute for on Chrome/Safari.
Offtopic, but I'm uncomfortable with the trend of calling a perfectly normal Linux OS, running on perfectly normal read-write solid-state storage, "firmware" just because the device manufacturer chose not to give you root. It encourages you to regard it as a static device that happens to need some software (like a CD-ROM drive), rather than an internet-connected fully general purpose computer "owned" by someone else. Ubuntu doesn't become "firmware" because I padlocked the case and locked the root account, and neither should Android.
Page transitions, time to render, fast JS engine. Firefox just feels clunky in comparison, sadly.
But last week I completely moved from Chromium to Firefox.
I didn't miss Chromium.
Can you point to concrete cases where Chromium has not taken contributions (without giving a good reason, that is)?
The team works really hard both on privacy and on open standards. But let's set that aside for a moment: There are many other companies contributing as well. (Opera, Samsung, Intel pop out when I just browse through the commit logs, but I'm sure I'm missing more).
And you as an individual, are free to contribute as well. We welcome OSS devs who want to help make Chrome better. Send me a ping if you ever get stuck, should you choose to contribute.
Yes, the project does not accept all changes. We can't, and no OSS project can. Some don't make sense ("Render all text blinking!" ;), some don't work for what the general idea for Chromium is ("Let's remove JS!"). But in general, the team tries to be accommodating when somebody wants to land a change.
I can understand when people say "Hey, Mozilla aligns more with what I want, I'll contribute there". It's awesome. You should work on something you believe in, and I'm glad you've found a project that works for you.
But Chromium is certainly happy to accept contributions, contrary to what the OP said.
Opera, I would use but I don't trust the chinese parent company.
The core Firefox / Gecko repos can be a bit conservative and slow to accept patches, but subprojects like Firefox Accounts / Sync, Devtools, Rust / Servo, browser.html, TestPilot, etc. tend have much lower friction while still affecting the direction of Firefox.
As an example, we recently replaced the JavaScript debugger with one written in HTML instead of XUL, using React, etc. All on GitHub and super accessible to outside contributions: https://github.com/devtools-html/debugger.html
On the recent discussion here about the Session Saver code, one Mozilla dev said that it needs rearchitecting, but that the issue is "manpower." I don't understand how a company that rakes in hundreds of millions of dollars per year can't afford to rewrite a problematic component--they had the manpower to write the bad design in the first place. Can they not afford to hire another programmer or two? Even now that they've cancelled FxOS? Where is the money going?
And generally Mozilla is taking Firefox in a direction that loyal users--who have used Firefox for nearly two decades now!--do not want. Mozilla is chasing Chrome users, rather than maintaining Firefox's useful, unique features. They just don't get it: if people wanted to use Chrome, they'd use Chrome. If they turn Firefox into Chrome, there'll be no reason to use Firefox instead of Chrome.
The handwriting is on the wall. Mozilla is no longer focused on making the best, most user-empowering browser. They are chasing ghosts, and when the money runs out...
How does this make it hard to contribute to Firefox? It just means that there's no guarantee that your bug will get fixed immediately?
Which ... is true for basically any open source product out there. And many closed source ones too.
I mean, yeah, it's disheartening to see your bug not get fixed. And as someone who is contributing by filing bugs and triaging, that isn't any fun. But, again, this is pretty standard for many open source projects.
> they had the manpower to write the bad design in the first place
That's not how software works. Software evolves over time, and requirements themselves change, leading to bad architecture. The session save stuff used to be json based probably because folks didn't/couldn't have that many tabs open for it to matter, but it does now.
> On the recent discussion here about the Session Saver code, one Mozilla dev said that it needs rearchitecting, but that the issue is "manpower."
This, again, has nothing to do with contributing? If anything the dev offered to mentor someone who wanted to work on it. There's activity on that bug, too, which shouldn't discourage contribution.
Bugs don't exist in a vacuum. There are priorities. And there are people who know enough to tackle the bug, who may have different priorities; you can't just randomly assign someone to a bug.
If you listened to everyone who said "you should make X your highest priority", nothing would get done.
> rather than maintaining Firefox's useful, unique features.
Example of this? I suppose you're talking about extensions here (that's the only example I can think of). There's a reason behind the direction Firefox is taking with extensions; the old extension model sucked. There was no API there, addons just reached in and tinkered with Firefox code. This means that improving Firefox by rearchitecting things was hard, for example addons were a big pain point for the electrolysis project that made firefox multiprocess. You were complaining about bad design before, this is an incredibly bad design (may have made sense at the time, but doesn't now). Fixing this involves replacing it with an API. The best direction to go in here is probably to have a standardised base for the API, which is Web Extensions. Firefox isn't planning on sticking to Chrome's feature set; it intends to make the API handle many of the needs of existing extensions. So Firefox still intends to maintain this unique feature, just in a different way.
It's been a few years now, perhaps things are better? I'm not interested in returning to that world to find out.
Those that can be will be, but I imagine entire categories, scores and scores of addons will be abandoned. So much of what people expect from Firefox addons is going away with no replacement in favor of basically light javascript web apps.
Which is the point of the switch: dramatically reduce addon functionality in the interest of safety / security.
> And using an unmaintained addon is dangerous.
And this is the kind of thinking I'm talking about. Firefore/Chrome/etc are all about protecting tech ignorants from themselves rather than allowing adept users to do what they want.
The kind of thinking that says "security-sensitive software with no active maintenance and regular updates is a security hole waiting to happen"?
Letting users install and run unmaintained software is dangerous. They'll get exploited. (And they'll blame the browser for that, and rightfully so.)
You can still do what you want; it's entirely possible to install local untrusted addons. You just have to poke some settings that are intentionally hidden from most end users, to make it somewhat more likely that users doing so understand the implications. And similarly, you can make your addon available to others willing to go through the same steps. They'll balk at doing so, and rightfully so.
Who says the addons have to be unmaintained?
https://github.com/Pale-Moon-Addons-Team
And look man, a lot of addons don't need to be "maintained," they just keep working. An addon that adds a button to the UI or something like that--it doesn't need to be constantly churned. Something like NoScript and ad-blocking addons need more attention, but a lot of very useful addons that let users customize their browser will continue working as long as the underlying APIs do.
So please lay off the scary language. Better be careful, when the Pale Moon comes out, addons become "dangerous"! :P
Millions of Firefox users lost their privacy without ever being asked about that with the help of Firefox default settings.
This long term collaboration with privacy-destroying ad tracking companies disqualifies Firefox as a privacy tool.
BTW, yes, this post carries an unusual view of things, but no illegal content - do you believe unusual views should be censored?
This statement doesn't make sense. All cookies can be tracking cookies and for example all session cookies are tracking cookies by definition.
Assuming for the sake of argument that you're referring to third-party tracking cookies, such as those from Google Analytics, or Facebook, this is the default because it's how the web has always worked. And maybe changing this default is reasonable, much like how browsers started blocking popups at some point, but it's debatable if such actions should be taken or would benefit users.
First of all, blocking third-party cookies by default might break web pages. But even more problematic is that this restriction can be bypassed, as to turn a third-party cookie into a first-party cookie publishers only need to inject some extra Javascript. Also meet http://samy.pl/evercookie/ - In other words, if you really want privacy, blocking third-party cookies isn't enough.
Also Firefox is the only browser that does block trackers in Private Mode, without any plugins needed, a setting that you can also enable to be active all the time: https://developer.mozilla.org/en-US/Firefox/Privacy/Tracking....
> Millions of Firefox users lost their privacy without ever being asked about that with the help of Firefox default settings.
This statement is factually not true, as it implies that blocking cookies has been the default and thus users had privacy to lose.
> This long term collaboration with privacy-destroying ad tracking companies disqualifies Firefox as a privacy tool.
Out of curiosity, when was the last time you contributed to the Mozilla organization? And if not, then you must have a better idea of how they should make a living, developing software in the open such that people can use it for free. They need a business model and nothing they did thus far had privacy implications for me. If you have a concrete example, I'd love to hear it.
> BTW, yes, this post carries an unusual view of things, but no illegal content - do you believe unusual views should be censored?
It's not an unusual view, it's just a silly one and silly views are quite common.
About your fact denial: Firefox does save cookies forever by default without asking users for permission about that, what enables tracking them forever. This is the opposite of proactive privacy.
This is factually true. It is not possible to "untrue" this fact. Everybody can check it.
What makes it even worse is that Mozilla is positioning itself as a "privacy aware" organisation, effectively brainwashing non-technical users with false claims about "privacy awareness".
> I will ask you to repeat that insult when we meet in meatspace one day.
That was not a personal insult, I was just criticizing your ideas. However I'll gladly meet with you and if I think you're stupid, I'll say so in your face.
Spidermonkey in particular (Firefox's Javascript engine) is laughably bad when it comes to vulnerabilities. This is also the reason why the Servo browser that some folks think will be a lot more secure (due to Rust) is mostly smoke & mirrors. They're planning to keep using Spidermonkey there too!
This is the first I've heard this claim. Do you have data showing this?
JS engines, from my point of view, regularly have all sorts of memory safety issues. No particular JS engine stands out relative to the others.
> This is also the reason why the Servo browser that some folks think will be a lot more secure (due to Rust) is mostly smoke & mirrors. They're planning to keep using Spidermonkey there too!
Smoke and mirrors? Servo has sandboxing, which is already implemented (and which I maintain). There's a night and day difference between that and an unsandboxed browser.
The goal of Servo's architecture is to, first, achieve a best-in-class sandboxing story and then, afterward, to advance the state of the art by reducing attack surface. We aren't going to reduce the memory safety attack surface to zero. But it's very much feasible to reduce it so far down that attackers don't even look at layout/DOM/etc. code for memory safety issues the way they do today when searching for browser holes. The return on investment when looking for memory safety holes in memory-safe languages just isn't there.
How can something that gets publicly exploited year after year by _teenagers_ (1)(2) be called "very secure" ?
The grim reality is that we never had a browser than can be called even remotely secure. Major factors for that are the implementation languages (C++ and C) and the vast attack surface. It's disheartening to see this trend continue.
(1) http://www.tomsguide.com/us/pwn2own-browsers-2015,news-20680...
You realize that there's only one browser which is starting to adopt alternative implementation languages, and it's not Chrome, right?
You're underestimating teenagers.
However, Firefox's user-centric development model has been declining for years now as Mozilla has grown and become accustomed to raking in hundreds of millions of dollars per year. Mozilla has been actively imitating Chrome for some time now. It is becoming less unique.
Mozilla's future plans for Firefox continue to make it less like Firefox and more like Chromium. The coming changes to the addon APIs, deprecation of XPCOM/XUL, etc, will probably erase any useful distinction between Firefox and Chrome. Electrolysis, while nice in theory (because who isn't tired of the janky Firefox UI), will also probably erase Firefox's advantage in memory usage.
It saddens me to say it, but Firefox needs to die and be reborn--the Phoenix needs to rise again from the ashes. Perhaps this has already happened in a sense with Pale Moon, although Pale Moon isn't even in Debian, so using it requires extra effort.
But it won't really happen (Firefox dying/forking) until Mozilla hits rock bottom. Only when they are forced to confront their bloated bureaucracy and their lack of user-focus will any real change happen. It will require (near)bankruptcy, leadership change and many layoffs. And who knows if Firefox would even survive; it's so enormous and complex, would anyone pick up the pieces? Would a community effort even be able to?
Anyway, we won't have to wait long to find out. The way Mozilla's going, I'd be surprised if they still exist in their current form in 3 years. Sad, but hey, Netscape died to give birth to Firefox, so maybe Mozilla's death will give birth to...Phoenix? (Can we use that name now, after all these years?)
I would actually love to see some more work on creating consistent extension APIs so that a single add-on is easier to write against the big 4. I know that FF is caving in favor of more Chrome like models in some places... In general it's sometimes because they are better models, and some because they are chasing chrome.
In some ways Chrome actually is better in terms of UX... in others (configuration in particular) FF has been better. Mozilla has never been just Firefox though. They are an important part of web development... And I'm glad they're out there... I do think some people are holding onto how things were for the sake of resisting change, and likewise some are changing for the sake of.
It's not just "the voice" of the community... it's millions of voices screaming for different things, and those stearing paying attention to the majority for most of them.
Whether it "failed" is entirely a matter of perspective. From my perspective it has been a wild success, providing a flexible, powerful foundation for Firefox and Thunderbird, as well as some other projects. It enabled Firefox to be the most powerful, customizable browser by empowering extension developers to meet users' needs.
So, no, it has not failed. What has happened is that a new generation of Mozilla developers has arisen who are not enamored with the old code. They don't want to work on it; they want to make something new and shiny, users and extension developers be damned.
Just like all the OS vendors went for flat UI in a mindless herd mentality, so Mozilla is following Google and mindlessly imitating Chrome--first in UI, now in architecture. Then in 5-10 years (if Mozilla is still around), another generation of programmers will come up and want to throw out that baby as well. Meanwhile, browsing web pages will still be browsing web pages, and users will have to waste time on useless churn.
> It's not just "the voice" of the community... it's millions of voices screaming for different things, and those stearing paying attention to the majority for most of them.
Firefox did not dethrone IE by paying attention to a majority of screaming voices. It led the way with a vision of empowering users to take control of their web browser, going against the commercial, corporate grain.
Mozilla is no longer leading, but following, chasing, like a jilted lover who pines, "Please, don't go with Chrome, come back, I can be like Chrome too!" What they don't understand is that, if they act like Chrome, there will be no reason to go with Firefox.
What will attract users is a strong, unique browser that knows what it wants to be, that takes care of and empowers its users--in contrast to a browser project dominated by an enormous corporation which profits from exploiting its users. Only when Mozilla groks this will it turn around and reverse its decline.
Firefox didn't dethrone IE alone, iirc, Firefox didn't even exceed IE usage until after Chrome came out, and even then only because Chrome ate further into IE's share and subsequently passed Firefox as well. Chrome was successful in part because of marketing, but in part because it was such a nicer browser experience. I still don't get why Firefox still has a separate search bar, when the address bar works for searches.
I'm not a Chrome apologist either, I'm frustrated with their decisions to remove browser scripts and make user installed extensions much harder to work with, the confusing nag notice at every startup is irritating to say the very least. I do find the UI much nicer to work with, though I wish it had nearly the advanced controls that FF offers.
That said, most people don't want or need to dig that far into their browser.. they want something to check facebook, watch youtube and send emails.
https://blog.mozilla.org/blog/2014/04/05/faq-on-ceo-resignat...
"On April 3, 2014 Brendan Eich voluntarily stepped down as CEO of Mozilla."
He could have stayed if he wanted to. Yes, it would have hurt their brand if he did, and yes it should have. Because yes, I and many others care very much if the CEO of a product donates to strip a minority of equal rights. Thanks to people like Eich, for seven years me and my husband had to lie and check "single" on all of our federal and state forms. For seven years we had to worry about being denied hospital visitation should one of us fall ill. We had to worry about how we'd handle inheritance should one of us pass. And on and on.
So yes, everyone is entitled to their own voice. Eich had a right to make that donation. And other people had a right to protest and boycott over it. Mozilla did not cave to the protests, so there was no free speech violation here.
Yeah as voluntarily as those politicians resigning to spend more time with their families really resign to spend more time with their families. It's not fooling anybody else, and I have very hard time believing it's fooling you. He resigned because he was asked to resign. That's how top management firing is done.
> He could have stayed if he wanted to.
Physically - yes, I guess, until they call security and carry him out :) Seriously - no, when Powers That Be in your org ask you to resign, you resign.
> Because yes, I and many others care very much if the CEO of a product donates to strip a minority of equal rights.
So if somebody who thinks firing people because they have different political opinion than you is wrong, would arrange to get you fired from your job - you'd be completely ok with that, according to your beliefs? Or it's only your political enemies that have to lose their jobs for their politics, but never you?
> Mozilla did not cave to the protests,
Mozilla absolutely, totally and completely caved to the protests.
Sorry to post a link, but I responded to the same argument already here: https://news.ycombinator.com/item?id=12579498
> So if somebody who thinks firing people because they have different political opinion than you is wrong, would arrange to get you fired from your job - you'd be completely ok with that, according to your beliefs?
If they were truly my convictions, I would stand by them and tell the world that I was fired for my beliefs. I wouldn't suddenly become a liar. Especially not to protect the company that just fired me.
If what you say is true, and there is zero evidence that it is, then I would lose the very last tiny bit of respect I have for Eich. It would also mean the Mozilla board was truly and utterly incompetent; because this was an extremely predictable result. They already knew of Eich's donation. And anyone with a functioning brain would have realized that this would become a much bigger issue when he was promoted to CEO.
We do, however, share common ground that nobody should be fired for their personal beliefs (nor for that matter, for what they do in their personal time.) Yet at the same time, I refuse to accept a world where I would be denied the right to protest an abhorrent individual. Say there were a company run by a neo-nazi grandmaster wizard of the KKK that wanted to commit genocide. But hey, those were just his personal beliefs! Would you still be against anyone refusing to use that company's products? Against anyone saying the company shouldn't have hired such a man to lead them?
The critics who called for his job were wrong to do so. Saying a man should be fired for his beliefs was almost as bad as saying that gay people should not be treated as equal citizens with the same rights as straight people.
> Mozilla absolutely, totally and completely caved to the protests.
Prove it. Or if that's no longer required, then NASA absolutely, totally and completely faked the moon landings.
That's not the question. The question is - would you think that company that fired you did right by you? If not, then you can understand how people feel Mozilla didn't do right by Eich.
> It would also mean the Mozilla board was truly and utterly incompetent; because this was an extremely predictable result
No it wasn't. A lot of people held view similar to Eich's (including Bill Clinton, Hillary Clinton and Barack Obama at certain times, btw) and many donated to Prop 8. If you not aware of it, Prop 8 actuall passed. Which means majority of California voters supported it. Not all of them were target of personal destruction hate campaigns. The hatemongers chose Eich to target, but they could choose somebody else out of 7 million people that voted "yes".
> They already knew of Eich's donation.
If they did, that would be highly unusual and irregular to investigate private life of a person. I would certainly be alarmed if my employer would scrutinize my private donations. WTF they are doing asking how I spend my money? But what if they did? Certainly a lot of people donate to a lot of causes, and not every one of them is targeted by hate campaigns.
> And anyone with a functioning brain would have realized that this would become a much bigger issue when he was promoted to CEO.
Nope. Name me organizations that CEO's of Fortune 100 companies donated to, without googling. You can't. Because you don't know. Because nobody knows. Because nobody cares, until it becomes target of a campaign. Now you are posing as if you could have predicted it, you could not.
> We do, however, share common ground that nobody should be fired for their personal beliefs
Yet Eich was. That's the
> Say there were a company run by a neo-nazi grandmaster wizard of the KKK
But there wasn't. There was a US Senator who was in the KKK (Robert Byrd) but most his comrades seem to be completely fine with it. Eich wasn't in the KKK and did not intend to commit anything. Why engage in ludicrous assumptions that we all know are false?
> The critics who called for his job were wrong to do so.
And yet they got what they wanted. And Mozilla aided and abetted.
> Prove it.
The proof is in the pudding. Mozilla never did anything to support Eich, it were Mozilla employees who initiated the personal destruction campaign, board was on the record offering him "another role" but never offered to stand up for him, and so on. Of course, I was not a fly on the wall when the talk between Eich and board members happened, so I can't give you the money quote. But I see the gist of the situation to be pretty clear and so do many others.
But yes, I have considered the opposite situation. And indeed, it's happened. It has only been 2-3 years since a majority of Americans have supported gay rights. It used to be that people would boycott over anything remotely supporting them. Most sponsors pulled out after Ellen Degeneres announced she was gay.
The thing with free speech is that it always works both ways. If you truly care about it, you always have to defend those that are indefensible. Yet in this case, supporters of Eich seem to think what he said was okay, but what his protestors said was not.
The people who protested had every bit as much of a right to their speech as Eich did to his. I believe Proposition 8 was a failure of government: that the rights of the minority should never be subjected to popular vote (tyranny of the majority.) But Eich was perfectly within his right to spend his money to say something truly abhorrent. And since freedom of speech is not freedom from consequences, so too did the people using Mozilla have a right to voice their displeasure.
Eich was a person that could have made the entire situation disappear in an instant by making a (completely meaningless given their history) matching donation to the HRC, and issuing a short post apologizing for his actions. Sure, many would see right through such a transparent act; but it would completely deflate the opposition in an instant -- guaranteed.
He didn't do so. To this day, he's still completely unapologetic for his actions. As much as I dislike the man, the one thing I cannot fault him for is that he is a man of integrity. I don't see him lying and pretending he voluntarily resigned.
I see that the board claim he was not asked by the board to resign. You can differentiate I guess between "You see which way the wind is blowing, better do what needs to be done" and "Resign or we'll fire you" but that's really a distinction without a difference and would seamlessly segue into the other state, I expect.
> but it would completely deflate the opposition in an instant
Can you cite an instance of apologizing quelling an outrage mob?
https://news.ycombinator.com/item?id=10660792
Hey, weren't you in Ohio the whole time, and not subject to California law in any event? Federal tax forms are not bound by California law. Nor are Ohio tax laws.
Would you be willing to go on record and state whether you were forced to resign or not? If you were, then I agree that was wrong, and will stop linking to that FAQ post going forward. Instead, I'll link to your reply and offer my support that Mozilla was in the wrong for forcing you out.
However, if you're going to stay with, "NDAs and none of your business", then I can't work with that. I can only work on what knowledge is available to the public. And all publicly available evidence is that your resignation was entirely voluntary. I hope you'll agree that unless someone actually involved (such as yourself) goes on record, everything else is just baseless speculation. It wouldn't be fair to penalize Mozilla based solely on conjecture.
And yes, I was in Ohio during our 2004 vote to ban marriage equality via state constitutional amendment. I stated that people like you (as in, religious people imposing their views on others through force of law) helped make that happen. Marriage wasn't really on my radar until around 2008. I think it was just seeing California of all places vote against it that really crushed my spirit for a long time. I know empathy is really difficult, but imagine if our positions were reversed and I donated to successfully help prevent you from marrying your wife. How would you think of me? That I didn't live in California is 2008 is no reason I can't object to your actions.
As always, even if we strongly disagree, I appreciate that you're willing to respond and have a discussion with a nobody such as myself, so thank you for that :)
Have you heard of the fallacy of the excluded middle? I resigned, I said so at the time and keep saying so, even today on this HN page. This does not exclude other possibilities that are none of your business. "Forced or resigned" is a false dilemma in general. Even if you don't know the specific details, the general point stands.
I think you know this, since you understand oppression. Oppression does not in general remove all agency from the victim. Two things can be true at once: oppressors used force; victim had freedom to move. Note I'm not saying I am a victim, I'm using an analogy to knock down the excluded middle fallacy that I think you put forth. Can we agree on this much?
1. The company is Mozilla, not Firefox 2. They did not fire Eich, he stepped down amid the controversy and left to avoid any more conflict
Now, while I can understand not being happy that they (Mozilla) did not step out in defense of their choice of Eich, I think it's a tad duplicitous to say they fired him.