With all of these Chromium changes this year, I think I’m going to give Floorp another try as my daily driver for a while. Features similar to Vivaldi, but a Firefox fork.
@mauro Otoh i am officially #FUD-free.
#FirefoxNightly + #Mv2 #uBO + #Sidebery + #FirefoxSecondSidebar = THE best browsing & sophisticated tab management + Web Panel UX i've ever had, easily eclipsing Vivaldi,
#Floorp,
#ZenBrowser, Waterfox, LibreWolf... ergo =
#FirefoxNightly + #NativeVerticalTabs + #uBlockOrigin + #FirefoxSecondSidebar = Very usable already as of Feb 2025, albeit less powerful than Sidebery, ergo =
@BrodieOnLinux@mstdn.social Floorp is what I recommend to people, who insist on sticking with Firefox.
As you pointed out, the obvious, if Firefox goes, so will all these many Firefox clones, because none of them have expressed interest in hard-forking Firefox, and going independent.
But, Floorp has two advantages.
1) They do not break things. LibreWolf, will break something (often), then blame Firefox. Which only further hurts, Firefox, which in turn only hurts, LibreWolf. -- It is a snake eating its tail. I think the 1x Floorp broke something, they patched it right away, and they owned up to their issue. They did not try to pass the blame, as LibreWolf does.
2) Floorp is very similar to Vivaldi Browser. If Firefox, goes, it would be nice not to have a big learning curve, if you need to switch browsers. If you've learned Floorp, you've more or less learned, Vivaldi, in many ways.
These are two things, I believe can help users in the long run.
#Floorp #Firefox #Mozilla #MozillaFirefox
@fnwbr And yet, here i be, revelling in the delightful UX that is my , with all the #telemetry disabled, the #AI disabled, numerous other parameters hardened via my #userJS, with the exquisite #Sidebery & its infinitely-nestable tree-tabs & multiple #Workspaces on its LHS, & the brilliant project #FirefoxSecondSidebar with my 21 #WebPanels on its RHS. It's such a great daily browsing UX, unfazed by the last ten days of global #FUD [all the so-called nasties can be disabled, either via simple clicks in the Settings UI, or otherwise via
about:config
/ user.js
]. Herd-mentality is a ridiculous trait of humans.
#FirefoxNightly + #Mv2 #uBO + #Sidebery + #FirefoxSecondSidebar = THE best browsing & sophisticated tab management + Web Panel UX i've ever had, easily eclipsing Vivaldi,
#Floorp,
#ZenBrowser, Waterfox, LibreWolf... ergo =
#FirefoxNightly + #NativeVerticalTabs + #uBlockOrigin + #FirefoxSecondSidebar = Very usable already as of Feb 2025, albeit less powerful than Sidebery, ergo =
@eknobl Also, the native #TabGroups have been working well for several weeks in , & in my recent testing they also now seem to have become reliable in
. The whole native #VerticalTabs UI ootb has ridiculous amounts of padding per tab, such that a stupidly small number of tabs can be open before invoking the scrollbar... i fixed this via some #CSS. The one remaining major design paradigm i dislike is that the tab groups are primitive like in Vivaldi & Chromium, ie, only single-level; no hierarchical trees are possible. Hence, even though the new VTs & TGs are aesthetically pleasing & quite usable, i still keep returning to Sidebery.
#FirefoxNightly + #Mv2 #uBO + #Sidebery + #FirefoxSecondSidebar = THE best browsing & sophisticated tab management UX i've ever had, easily eclipsing Vivaldi,
#Floorp,
#ZenBrowser, Waterfox, LibreWolf... ergo =
#FirefoxNightly + #NativeVerticalTabs + #uBlockOrigin + #FirefoxSecondSidebar = Very usable already as of Feb 2025, albeit less powerful than Sidebery, ergo =
aight, switched back to #LibreWolf instead of #Floorp to see if this browser doesn't suffer from Firefox's weird memory leaks
@lecroix74 which is what I'm saying. #Waterfox and #LibreWolf should combine into #Waterwolf...
Imagine a new effort and interest in actually adding missing #W3C standards in #Firefox and fully decamping from whatever the heck Mozilla currently wants to do.
Then other forks like the #ZenBrowser or #Floorp can then take a hard look into using this fork instead, forming a more secure and stable migration path - if all goes well.
#librewolf and #floorp are waving
RE: https://mstdn.social/users/hkrn/statuses/114092866039091745
In any case, I think the whole "we can't just have one browser" argument has been put to bed, and arguably #Mozilla isn't the only one still implementing the #gecko engine.
I hope to see a fork between various vendors, that #librewolf, #zenbrowser, #floorp and others cross swords, and with these powers combined make #mozilla regret their decision to abandon libre principles.
The engine isn't bad. I think it's pretty good... just maybe they could update the standards for it :3 plz?
We see that we do have options, that we may have many #browsers, but only a few #browserengines.
Wether you're using #Vivaldi, #Opera or #Brave, it's the #Blink engine.
If it's any of the free browsers made for #Gnome or #Plasma, or #Safari for #Mac and #iOS, it's #WebKit.
#zenbrowser, #librewolf and #floorp are based on #firefox (or the gecko engine) and are safe refuge for people defecting from Firefox.
@nrdufour #Ladybird is launching with a new engine in 2026. In the meantime, there's #Librewolf and #Floorp, along with the obvious #torbrowser . Don't give GOOG more money.
Oh, and if you want my actual preference, I lean on #PaleMoon whenever possible, but I recognize the limitations there.
On Linux I've tried/used the following browsers to replace Firefox:
- Zen (Firefox)
- Floorp (Firefox)
- Librewolf (Firefox)
- Vivaldi (chromium)
For the last several months I've been using Floorp and am happy with it. I use Librewolf for accessing Meta.
On Android I've used Firefox for day to day and Waterfox for accessing Meta.
IANAL: my concern is how much of the new Mozilla TOS is directly applicable to Firefox forks.
The new TOS reads like Mozilla is legally allowed to 'tee' anything you upload to their own information horde, including anything binary.
Also, something I've noticed is that sometimes when Mozilla upstream makes TOS/marketing/affiliate changes via about:config changes those changes get pushed downstream and if the downstream team misses it in the rush to get the new version out the door you may end up with these settings re-enabled.
I tried Vivaldi yesterday. Ad blocking isn't sufficient to use it as a daily driver browser. Unusable for me.
Eyes to the future for open source browser engines.
Mozilla Firefox is officially dead.
My back is officially turned.
What options remain?
For now I'm probably going to be using Gnome Web (i.e. Epiphany) for most straightforward web browsing. It works more than well enough for the stuff I do. Mobile version for Android? Does it exist? iOS?
I'll use Vivaldi for lame "modern" sites that a "simple" browser like Epiphany can't render properly. Mobile?
We'll see how far that goes. This may be less and less of an issue. The big player sites like Google, Meta, etc. are not somewhere I tend to visit.
Banking sites are a mixed bag of necessity.
I'm about to let my Amazon Prime account lapse on its yearly renewal since I won't use them any more.
At least Vivaldi seems to be a decent organization. Technology is based on Chromium though - and this is why I haven't started using it.
I will need to investigate Vivaldi's built-in adblocking since manifest v2 isn't a thing under Chromium.
I used to care about keeping the Mozilla rendering engine alive and relevant but now not so much.
The Firefox forks I've tried have been a mixed bag of whether their new versions follow re-enabling the privacy invasive things that Mozilla upstream does when it sends out a new version.
Time to leave them behind as well I guess.
A lot will depend on how much I miss ublock origin.
If there is a mass exodus from all the Firefox based forks then ublock may cease to exist.
There's a rant in there about pi-holing all browsers but I don't have it in me ATM.
(Posted with Epiphany)
@CanvasesByPeter I'm confused with this request. So I was curious to learn that a security vulnerability was being patched. The #Floorp browser will be affected by this too. The #Firefox browser isn't expiring. Otherwise, I've started tinkering with Floorp on this end. It's Firefox under the hood. Been thinking about swapping to it over #Waterfox which is notorious for having a slow development cycle. It's like #Vivaldi, but for #Chromium browsers. I like using the Vivaldi browser.
「Chromiumというのは極めて複雑化が進み、リポジトリ全体が巨大化していました。僕の場合、使用PCが高スペックでないせいか、Chromiumのソースコードをクローンするのに6時間、ビルドにはまる1日かかりました。ふりかえってみれば当たり前なことだったのかもしれませんが、「こりゃ、ただの学生が改造できるようなものではないな」と面食らったのを覚えています。」
わかる。一回はやってみたほうがいい。一回だけでいいけど #firefox #floorp
多機能ブラウザ「Floorp」に込めた願い。学生開発者が“Firefoxベース”を選んだ理由【フォーカス】 | レバテックラボ(レバテックLAB): https://levtech.jp/media/article/focus/detail_621/
I do not use #floorp browser a lot, but I think that #ZenBrowser is taking all the attention now.