2 ms·
Easy path to success for Firefox is to continue to beef up security and privacy tooling for their users and have sane defaults. They've been winning a lot of us
by jillesvangurp 8y ago
Easy path to success for Firefox is to continue to beef up security and privacy tooling for their users and have sane defaults. They've been winning a lot of users who feel abandoned by the big companies in this space.
A problem and conflict of interest for them regarding this is that they are funded mainly by Google. Firefox has a conflict of interest here because they are not doing all they can here because that would cut off their main source of revenue.
So, for example, they have sort of a mute option for sound (just like other browsers) but they don't allow you to mute video by default (without blanket turning it off for all websites). I don't know anyone who loves being bombarded with video content when they want to read an article. I find the moving stuff to be distracting; even if the sound is off. Also the bandwidth is kind of not nice, especially on mobile. The BBC has started putting multiple video previews in their articles. This kind of attention whoring is highly annoying. This is not news to anyone of course.
The obvious fix allow people to whitelist sites to allow autoplaying video (youtube, netflix, and other websites where people go specifically to enjoy video content) and switch that off for everything else. All the extenions for that claim to do this are basically a combination of broken or simply setting the config property that blanket bans all autoplay video for every website (just preempting the inevitable comment to try extension X here).
Similarly, the containers extension is great. This should be baked into the browser and improved to the point where the default container is a private container unless you whitelist the domain. Right now private browsing happens in a separate window. It's an obvious thing to do: every site by default is private until you say otherwise.
Both kind of are in direct conflict with how Google, and by extension, how Mozilla monetizes. This is the main reason this is made hard to do. I'm sure if this was easier, there'd be countless extensions doing exactly that. Instead people sort of emulate private browsing with stuff like noscript and other extensions that throw away cookies. Also nice but not user friendly.
Doing all this in fool proof, user friendly way would be a great way for Firefox to differentiate. It would unfortunately cut them off from Google funding probably.
- bzbarsky 8y agoJust FYI, audio autoplay is being actively worked on in the current Firefox development version, precisely to solve the problem you describe. There are some issues with coming up with a UX that doesn't privilege a small set of sites out of the box over everyone else [1] and also doesn't prompt the user on every single site that tries to play video (the current Firefox Nightly behavior; it's rather annoying). So for this specific case, the reason it hasn't happened yet is not some nefarious conflict of interest but actual hard problems that need to be solved (and are being solved), coupled with resource constraints. As far as containers go, I agree they are great if you understand the model. I use them. Most users find them terribly confusing in their current form. Again, a UX issue. That said, the idea of having things in a private container by default is somewhat interesting. The hard part in some way would be the discoverability of the whitelisting flow and user confusion about why their customization information is not being remembered like in every other browser. I'll try to shop this around to people a bit and see if they can figure out a way to make this work sanely. Disclaimer: I work on Firefox, but not in UX. [1] Google's solution in Chrome; it suppresses new startups by making the experience suck there, which is good for incumbents like YouTube but maybe less good for the web as a whole in the long term.
- jillesvangurp 8y agoI have an extension that blocks audio per site already (mute sites by default). Awesome stuff, but blocks only the sound. It shows a little mute icon on the tab if it mutes. I simply unmute when I actually want sound and the setting seems sticky. I was talking about video auto playing (with the sound off) by default. I don't want that ever, unless I allowed it before. I want to block html5 content from activating at all unless specifically allowed. I'm on the beta channel. As far as I know there are no plans to address this and extensions that have tried to implement this are running into some limitations that make this hard apparently. Hence a lot of variations of flashblock extensions that simply set the about:config setting instead of having per site policies with whitelists and blacklists. Private browser containers would be nice to have even if they are not yet default out of the box. I'd simply make this an option on all containers (including the default one and default it to off). I agree the ux for this would need a bit work to be discoverable/intuitive.
- bzbarsky 8y agoAh, I had misunderstood the issue; thank you for clarifying. It looks like https://bugzilla.mozilla.org/show_bug.cgi?id=1405827 https://bugzilla.mozilla.org/show_bug.cgi?id=1405827 tracks WebExternsion API that would make it easy to create extensions that address this use case.
- gambler 8y agoMost people don't care. Firefox became popular by being fast and offering tabbed browsing when IE didn't. I think being fast and offering radical quality of life feature is a good strategy to follow even now.
- amyjess 8y ago> tabbed browsing And popup blocking. I remember how much of the Internet was utterly infested with popups in the early-to-mid-00s. Firefox was the only way to not get inundated, unless you were a really hardcore geek and ran a proxy server like Junkbuster (the ancestor of Privoxy), and most of the population wasn't going to do that. Popup blocking changed how the Internet works, and you can thank Firefox and Opera for that.
- Shorel 8y agoFirefox became popular by copying Opera to the extent that right now one of the reasons I use it, is because it feels more like Opera 12 than the modern Opera ever could.