211–220 of 394 posts
Earlier quoted context omitted.
The day that adblockers stop working on Chrome is the day we'll see that mass-migration.
Which will probably never happen.
It's time for mass-migration to Firefox. Only losing users is going to tell Google that this is a horrible solution to enforce.
The only browser that's been losing users for years is Firefox. That already tells Google all they need to know. (It also tells Mozilla what they need to know; pity they are deaf.)
Earlier quoted context omitted.
I remember some people saying Safari's extension changes and specific content blocker API would be a good thing because ad blockers would use less resources. The change happened, uBlock Origin broke for Safari and here we are several years later and the Safari ad blocker ecosystem is an absolute joke and most of it barely works or demands subscription fees (and the ones that do are certainly not worth paying for beca…
That’s not true re the Safari ad blocker ecosystem. We develop a Safari ad blocker [1] that works on iOS and macOS which provides performant and private ad blocking. Unlike previous ad blockers using other extension mechanisms, it also can’t see which web pages you visit. We recently released best in class YouTube ad blocking features too. The mechanisms for doing this is different, but the ad blocking results are as…
Out of curiosity, can Magic Lassoo present a detailed list of domain connection attempts by category, i.e. do anything like uMatrix does? The thing that keeps me on FF, even on MacOS (aside from warm fuzzy open source feelings) is that I really think the extension ecosystem is the best -- uMatrix, greasemonkey and the ilk are brilliant. I like Safari's isolated private browsing mode most of the time, and I like its dev tools. But the adblock situation is just so much better on FF; it makes the web usable again whilst respecting my privacy ideals. I really like being able to say 'Thou shalt not set thine cookie and contact all of these domains via an XHR request' and the site just...continuing to work.
Earlier quoted context omitted.
8 years ago, Firefox 25 was released. I don't know your needs but a lot as changed underneath. Notably, Firefox is now using multiple processes, the Javascript engine is probably a lot faster, the web engine too. I don't like every change, especially the latest revamp of the UI, but it is still the best browser for me. You could try, and them move if conclusive? If you consider switching anyway. Moving everything bef…
As I said, I was bitten twice. It's hard to even try now. Back then I try for a few week before committing, but when I move my session (of 200+ tabs) onto Firefox, it's dead. And back then I was told the exact same thing I was told this time, too.
I have thousands of open tabs, managed with the Tree Style Tabs (TST) plug-in.
I don't understand why this (and all the rest) is not driving people back to Firefox. Are we really going to wait for Mozilla to die, and then lament that Google has taken over the web?
Firefox will always be around in some form subsiding off Google scraps to give Google plausible deniability regarding browser monopoly. If Firefox does implode, it will be because of Mozilla's garbage leadership/product vision, not market conditions.
Removing webRequest's blocking will completely destroy my web extension. It helps people get work done by blocking website's they're addicted to. I've just started out on a new version, not sure what to do.
Is there a reason you can't use the declarative API to block these websites? Isn't that what you're doing on Safari? https://developer.chrome.com/docs/extensions/reference/decla... (Disclosure: I work at Google, speaking only for myself)
I thought the rules were static, I see now they can be updated dynamically — which works perfectly for my use case.
Earlier quoted context omitted.
Sure! I use a single toolbar at the top that contains back/forward, refresh/stop, menu dropdowns (which are all hidden except for History/Bookmarks/Tools), the address bar, my bookmarks toolbar buttons, and all addon buttons. Below that is my tab toolbar. This setup is accomplished by CSS with a bunch of position:absolute; and negative margins and stuff, because it's impossible to truly have all of these things in th…
Don't reverse responsibilities. _You_ made the choice of changing this CSS. _You_ fucked the layout up when the upgrade comes in.
A decade ago it was very easy to make Firefox look like you wanted, even without extensions (if you weren't opinionated about aesthetics, just position and functionality.) Every UI change since Chrome was released has been a regression, and more obnoxiously, each change has been locked in with user adjustment actively prevented or made prohibitively difficult, even for programmers.
They could at least offer a consistent interface to change the UI. Instead they demand the flexibility to make UI changes without having to maintain an interface, while using that flexibility to claw back more and more flexibility from their users.
Earlier quoted context omitted.
> Because they keep making stupid UI)UX choices than alienate their users Cannot overstate this enough. They keep randomly changing their UI constantly , and it's especially frustrating when you have a bunch of custom CSS. I'm a bunch of versions behind & dreading updating because I don't want to spend the hours it'll take to fix my shit for their new version. I honestly hate this browser so much at this point, but e…
but you recognise you are in likely a sub 0.5% of users with custom css? chrome gained a lot for two reasons, it was a hell of a lot better than firefox and they advertised the crap out of it. Firefox has caught up significantly since then but doesn't have the advertising the adblock debate will push a lot of users back to firefox and it feels like the ui is in a much better place than it was
People don't want to do custom CSS, they have to in order to get the workflow back that they had last week. It's annoying and a lot of work. Firefox changes probably cause >3% user attrition every single release.
I don't understand why this (and all the rest) is not driving people back to Firefox. Are we really going to wait for Mozilla to die, and then lament that Google has taken over the web?
Probably because v2 extensions haven't been switched off yet. It might be different in January 2023; or maybe the limited adblocking of v3 will be enough for most people. Time will tell.
https://blog.mozilla.org/addons/2021/05/27/manifest-v3-updat...
Earlier quoted context omitted.
Firefox will always be around in some form subsiding off Google scraps to give Google plausible deniability regarding browser monopoly. If Firefox does implode, it will be because of Mozilla's garbage leadership/product vision, not market conditions.
I'm not sure how you can be certain of this
Regarding Mozilla's direction, we already have years of evidence. It all starts with Brendan Eich's resigning. Whether you agree the reasoning is immaterial; that decision lead him to start a direct competitor that is now fighting them for the ever-shrinking demographic of people that don't use Chrome. And then there's stuff like acquiring Pocket, something completely antithetical to Firefox's core values. Money-wasters like FoxOS (or whatever that mobile OS was called) that distracted from Firefox. And then lots of tick-tacky stuff like FF devtools being inferior to Chrome for years (people say it's better now, but I don't care to check it out, I've been using Chrome's for years), over-focusing on frivolous things like social justice issues. It will be death by 1000 cuts that kills Mozilla from the inside.