Show Navigation
Notices tagged with firefox
-
#Vivaldi Browser added a social side panel and says it was the first to do so. https://vivaldi.com/new/
Years ago, a #Firefox fork called #Flock had a social tool built in. I only used it for #Twitter, but it was there. Memory is unclear whether it was a side panel or another Window with different measurements, but it existed.
-
@musicman Is your #Firefox up-to-date? Some really JavaScripty sites won't render at all in #Palemoon, but I think that's because their JS engine forked from Gecko's some years ago and has been diverging over time.
-
@bobjonkman I noticed that (at least the first time) #Firefox in a Snap has a long delay before it starts.
No doubt that's time used in navigating through various security hoops or perhaps mounting a special filesystem, but for the most common software (name-brand web browsers), it is unnecessary and unwanted.
I noticed that it did not put something like Node.js in a Snap. IMO, Node is the poster-child for Snap and Flatpak. It shouldn't be in the default install, it likely changes too fast for most distros' LTS model to handle well, and it is widely used by certain developers. If Snap / Flatpak / et cetera have some security hardening, Node (and its related 'npm' package manager) is exactly the place it is needed.
-
@bobjonkman Yes, that was rather frustrating. I left to run errands and returned to find a pop-up informing me that my regular install of #Firefox would be converted to a snap install. Naturally, the installation stopped while it waited for me to acknowledge this.
-
I still mostly use #Mustard (abandoned client, but it was still available in F-Droid when I installed it; no idea whether it is still available there). I also use #AndStatus, and sometimes I just use a mobile browser ( #Firefox / #IceCatMobile ).
I keep saying I'm going to write a new GS client, but so far, I have not even started.
-
https://nu.federati.net/url/286696 [www realmicentral com]
#Firefox making "Total cookie protection" standard in browser.
Source: https://shitposter.club/objects/2cc69e42-37ac-489c-933c-df0032d13d71
-
#Google #Chrome and all other browsers based on #Chromium will get some changes to their extensions API which will reduce the ability of ad-blocking extensions. #Mozilla #Firefox is rejecting that part of the change, so Firefox and other browsers based on their code will retain superior ad-blocking capabilities.
-
A lot of us are concerned about #Firefox, about #Thunderbird, and about #Mozilla itself. The trouble is, most of the seeds of Moz's current affliction were planted early on, when the #Google search deal was first signed.
They received an unimaginable amount of money, and being good people, they decided to pour it into becoming the Web's advocate and (later on) the Web's privacy advocate.
They built a large organization, with some very high salaries at the top, based on the revenue they received from a single customer. And then that customer launched its own browser, #Chrome, in part because Firefox was going slower than Google desired because so many resources were going into other projects and because Google's plans were not always aligned with what Mozilla believed was best for the Web.
It was always an unsustainable situation, and when things changed due to cooperation being replaced with coopetition, they started a panicked grasping for other revenue sources.
Now, they've cut actual developers, which makes it even more difficult to keep up with Chrome / #Chromium (and the many browsers derived from it). And because they need to find other revenue sources, they keep looking for ad deals ... which runs crosswise with its core users, who want to block ads.
So, yeah, I don't see a way out that leaves them as anything other than a niche product produced by a small team of mostly volunteers.
I do think _personalization_ as a differentiator is going to flop, if they're thinking about color schemes and superhero logos. A big chunk of what people did with XUL (the former technology, and what made it so customizable) was produce ad blockers, script blockers, embedded-media blockers, pop-up blockers, cookie and tracking blockers, proxy tools, and web development tools (webdev toolbars, xml toolbars, json tools, css and xsl tools, sqlite tools). I just don't think that the ability to make your browser look like the Spiderman t-shirt you bought last week is going to win over a lot of people who are using Chrome/Chomium/Edge/Opera/Vivaldi/Brave/Iron.
Now, maybe if they make it the most secure and private browser right out of the box, with ad blocking, script blocking, and so on, plus make it faster than the Chromium family while consuming less RAM and crashing less often, then adding the ability to dress the browser up as Dora the Explorer will total enough advantages to make a difference.
-
https://www.wired.com/story/firefox-mozilla-2022/
Yeah, a lot of us are concerned about #Firefox, and about #Mozilla in general.
-
I've seen a couple of people grumbling about a new redesign in #Firefox 89.
#Firefox_89
-
Also: #Chromium based browser #Brave disables #Google’s #FLoC https://brave.com/why-brave-disable-floc/ [brave com]
https://nu.federati.net/url/281049 [www theverge com] notes that #Mozilla #Firefox currently has no plans to implement #FLoC and that #DuckDuckGo is already working to block FLoC.
#Microsoft #Edge and #Apple #Safari issued somewhat evasive answers, but it is expected that Apple will be 100% no on FLoC.
-
Angry Sheep Blog > Rants > #Firefox 77+ URLbar https://rejzor.wordpress.com/2020/06/05/firefox-tweaker-and-dealing-with-firefox-77-url-bar/ [rejzor wordpress com]
I haven't noticed the giant URLbar issue, even on Windows. I have noticed that they removed the ability to turn off URL formatting, so now everything is an almost unreadable light-gray, except the main part of the domain. I understand that is meant to protect users against sites named www.google.com.somelongname.badsite.com, but it doesn't need to be unreadable.
-
#Aptoide unofficial repo for #Andoid software
> More than 20,000,000 accounts from Aptoide were compromised in 2020.
Seen when visiting https://en.aptoide.com/ in #Firefox. https://nu.federati.net/attachment/278638
-
https://nitro.horse/@andreas/105249830532698872
"Sponsored sites" in the #Firefox 83 URL bar? No, #Mozilla, just no.
-
We wondered how #Mozilla’s layoffs would affect #Servo, the next-gen browser engine code for #Firefox. Answer: the Linux Foundation is taking over Servo development https://phoronix.com/scan.php?page=news_item&px=Linux-Foundation-Servo [phoronix com]
-
RE: https://loadaverage.org/conversation/14074142 ... I'm not seeing that issue with #Firefox 82.0 on Debian and Ubuntu family computers.
-
No, #Firefox, I do not want to enable #DOH through #CloudFlare. That's why I intentionally disabled it when an update enabled it. Stop asking me after updates whether I'd like to turn it on.
Eventually I will set up my own DOH ( DNS over HTTP ) server, but until that time, I don't want it enabled.
-
@mangeurdenuage I've been using #KeepassXC and its extensions for #Firefox and #Chrome / #Chromium.
-
@musicman I agree about exec pay.
As for side projects, in their new, limited-resource world, every new project takes resources away from #Firefox, #Thunderbird, and #Rust. Sometimes that's worth the cost, sometimes it isn't, but take a look at how many projects they've abandoned (such as their mobile OS).
-
http://calpaterson.com/mozilla.html
Starts with a comparison of #Firefox market share and the pay of #Mozilla's top executive
I did not search for it, but around the time they laid off 1/4 of their workforce, I thought I saw something about some pay reductions for their top management.
https://www.jwz.org/blog/2020/09/this-is-a-pretty-dire-assessment-of-mozilla/
My personal assessment is this: as the browser started picking up share, they also picked up a patron (Google) that seemed to provide unlimited funding. It was during this period that all the "privacy NGO" ideas started, because they had more than enough money for their main projects and decided they'd spend the rest "doing good".
I can't fault them for that. But I do think that Mozilla's current state is pretty closely related to having "grown up" with unlimited money to spend on tangentially related projects.
At some point, Google decided that their interests were better served with an owned-and-controlled browser, and the rest is history.
There's always the hope that Mozilla will open up more Firefox and #Thunderbird development to non-paid programmers and start asking its users to optionally contribute financially. This could help, but there still needs to be a soul-searching that asks whether they are a group that develops a browser and a mail client or some sort of generic web and privacy advocacy group that just happens to develop those applications.
Those are two different roads, and with a much more constrained income stream, they can't be both at once any more.