@kingtor well fwiw, i'm a "fediverse type", & i continue using my desktop Linux  with daily delight. i laugh about, often at, the many panic merchants volubly screaming to abandon ship now. so much operatic hysteria.

// Droppie 24/3/25: Disable all fucken AI: user_pref("browser.ml.enable", false); user_pref("browser.ml.chat.enabled", false); user_pref("browser.ml.chat.sidebar", false); user_pref("browser.ml.chat.menu", false); user_pref("browser.tabs.groups.smart.enabled", false); user_pref("browser.ml.linkPreview.enabled", false);
#FirefoxNightly with #NativeSplitTabs, + #FirefoxSecondSidebar + #TreeStyleTab + #SimpleTabGroups = ๐Ÿ’ƒ๐Ÿฅณ๐ŸŽ‰๐Ÿ’ฏโœ…๐Ÿ‘
.
#FirefoxNightly with #NativeVerticalTabs and #NativeSplitTabs, + #FirefoxSecondSidebar + #SimpleTabGroups = ๐Ÿ’ƒ๐Ÿฅณ๐ŸŽ‰
.
#FirefoxNightly + #FirefoxSecondSidebar + #Sidebery = ๐Ÿฅณ๐ŸŽ‰

#DropbearPooterising #LinuxWomen

Youโ€™ve just been upgraded to Firefox Nightly 148!

Every 4 to 5 weeks, a new major version of Firefox is released and as a result, the Nightly version increases as well.

This is a good time to thank you for helping us make Firefox better and to give you some pointers to documentation, communication channels and news sites related to Nightly that may be of interest to you.

#FirefoxNightly with #NativeSplitTabs, + #FirefoxSecondSidebar + #TreeStyleTab + #SimpleTabGroups = ๐Ÿ’ƒ๐Ÿฅณ๐ŸŽ‰๐Ÿ’ฏโœ…๐Ÿ‘

#FirefoxNightly with #NativeVerticalTabs and #NativeSplitTabs, + #FirefoxSecondSidebar + #SimpleTabGroups = ๐Ÿ’ƒ๐Ÿฅณ๐ŸŽ‰

#FirefoxNightly + #FirefoxSecondSidebar + #Sidebery = ๐Ÿฅณ๐ŸŽ‰

#DropbearPooterising

Trying out #Sidebery.

It integrates with history and bookmarks very well, looks nice and does its job.

Links:

Note: remember about enabling "legacy" userChrome and userContent stylesheets in about:config.

Thanks for recommending it to me @muppeth, I love it!

World of Edolas

@zenbrowser Good, nice, thanks... but what about the rest of it? Tab trees... not only for pinned tabs, but all tabs, as per #TreeStyleTab & #Sidebery?

#7359 https://github.com/zen-browser/desktop/pull/7359 was supposed to add folders and trees, but a new PR was split off (#9355) that only added folders. Is there any chance that tree tabs will be added eventually or are tab trees not planned?
https://github.com/zen-browser/desktop/discussions/891#discussioncomment-14235449+1 here, i'm super looking forward to any native tree implementation in zen. Here's hoping trees were just cut to get folders out faster and are still planned for later.

Either way, would love some transparency on this, as everything pointed at that PR adding trees but they were just dropped for one reason or another.
https://github.com/zen-browser/desktop/discussions/891#discussioncomment-14235627I haven't looked too deep into the contents of the folder PR, but much of the UI/UX work of "tree-styled things" should be done so hopefully a tree-style tabs PR would be somewhat simplified.
https://github.com/zen-browser/desktop/discussions/891#discussioncomment-14235802#ZenBrowser #TabTrees #TreeTabs

Initial implementation for folders and tree-styled tabs by mr-cheffy ยท Pull Request #7359 ยท zen-browser/desktop

Functionality: Make firefox groups work only for pinned tabs Correctly restore folders to their designated workspaces after a restart Allow folders to stack up together Split view groups shou...

GitHub

Late last year, after having used it as my daily default browser for a few [maybe several?] months, the incessant bugs, unrelenting workflow-buggering major changes, & frequent loss of all tabs, caused me to abandon  [only in early Beta back then, so not totes surprising] & return to ticktacking back & forth twixt  and . Into 2025 those latter two continued competing for my daily affections.

T'other day i learned that the long awaited native #TabFolders in  have now landed in #ZenTwilight [the nightly / Alpha version], & thus might be expected to make it finally into the Beta version within a week or two. This morn, possibly against my better judgement but tbc, that discovery inspired me to jump back into my  Beta & relearn it + learn all the stuff new since i last dabbled, in anticipation of this incipient major design UI & UX change.

All the #KleverKids are saying that Zen's TabFolders are a game-changer, coz they will provide users with the first ever native-in-a-Fox browser tab hierarchical nesting. None of  , nor  has it [all only flat, not tree, structures; ditto flat-only in Chromium, Vivaldi, Edge et al]. Hitherto the only way to gain this important function has been via AddOns like #TreeStyleTab or #Sidebery. These are both fabulous, but do not have access to all the native foxy code bits n pieces [i've damn well forgotten the proper term atm, sigh], so by using either of these AOs we lose some of the important fox functionality, eg, tab context menu items. If the Zen Dev/s do their work really well, we will finally have our tabby cake & eat it.

#ZenBrowser #FirefoxNightly #Floorp #Floorp12

It's such a shame, & tbh a mystery to me, that โ€‹โ€‹ still seems to not have any native tabs lazy-loading option. Excellent AOs like #TreeStyleTab, #Sidebery, and #TabStash have it. Chromium's had it for years.

The closest to it [but this is a very different thing] i can find in
about:config is dom.image-lazy-loading.enabled. That's ok, but IMO is far less important than something like dom.tab-lazy-loading.enabled [which i repeat, atm does not actually exist]. ๐Ÿฅบ

cc:
@firefoxnightly

#Firefox #FirefoxNightly #LazyTabLoading

@boo_ @AAKL @9to5Mac Hi Klara. I reckon you've made fine points & well expressed. I shall readily & entirely concede that my choice of comparison was crude & legitimately liable for criticism. Let me try though to explain what was/is in my mind, wrt all the Mozilla shenanigans & imbroglio.

First, i readily join the bands of voices criticising Mozilla over many years for apparently letting Firefox fall far behind the competition. One does not even need to consider the chromium-based competition, to be able to criticise their apparent loss of interest in FF until comparatively recent months. Even staying within the Gecko-sphere, the fact that single-Dev projects like #Floorp & #Zen have been able to create quite excellent forks in short time that far exceed the limited innovation Mozilla have done in FF for many years, should shame them. Moreover, other single-Dev projects like the fabulous #FirefoxSecondSidebar, & then also ofc the AOs #TreeStyleTab & #Sidebery, illustrate by comparison how negligent the FF Devs have been [or maybe, been allowed to be], in not natively incorporating such great innovations that elevate the UX so considerably.

Secondly, the brouhaha recently re the ToS / ToC or whatever we call it. Mozilla possibly could not have been more ham-fisted & incompetent wrt how badly they mismanaged the situation, & they deserved a lot [but far from all, IMO] of the worldwide criticism they incurred. As to the germane details themselves, fwiw i tend atm to fall on the side of the argument that they were very clumsy, but not being evil by design... & in matters like these i always ask myself the counterfactual "well ok, do i now distrust them enough to actually abandon them & thence choose to cut off my nose to spite my face by entering the actual proven evil empire of chromium-based browsers?". My answer remains NO!!!

Thirdly, the #AI problem. Lemme state upfront that i despise the entire global fetish that's erupted for #LLMs / #GenerativeAI. I loathe & despise the vast intellectual property theft perpetrated in training these things, despair at the shocking environmental implications of them, & alternatively scream & cackle at the gross human stupidity manifested by peeps all over the rock blindly accepting the hallucinated garbage produced by these monstrosities. Do i want AI in my Foxes? Nope. Would i prefer Mozilla was not apparently bent on this path? Yep. However, again i ask myself that counterfactual, which i am able to mediate with the knowledge that atm anyway, knowledgeable users are still able to actively choose not to use it, & deactivate it, in their Foxes. Is that the best way Mozilla could have done it? No, ofc not. Is it overall a scenario that i can still use to my advantage? Yes. Is it a least-worst alternative to the chromium horrors? Yep.

A Third-&-a-Half point arises. I said above "knowledgeable users are still able to actively choose not to use it". What then though for non-knowledgeable users, for the non-geeks, the "regular peeps"? Here i admit my attitude is harsh & possibly mean, & i shall accept all criticism of it. IMO the "regular peeps" do not care one jot about any of this. They often struggle to grasp that a Search Engine is not a Browser. Many do not know or care that they have a substantial browser choice, beyond whatever came on their device. They think of "Browser" & "Chrome" as being synonymous & indivisible. They have no idea that they do not in fact have to tolerate their present miserable web UX of sites drowning in ads, trackers & malware. They have no idea of the existence, much less purpose, of #uBlockOrigin. I posit that these peeps are the target market, aka shooting fish in a barrel, of the present AI fetish, who know not &/or care not about any & all the ills of AI, who are unmotivated to lift a finger to improve their online UX, & who simply desire to accept whatever slop is served to them. IMO none of the recent Mozilla noise is relevant to them, as they're either not using FF anyway, or if they are, do not care about anything behind the curtain.

So, my OP was primitive & arguably invalidly comparing apples with oranges, but i wrote it with all the above in my mind. Fwiw.

Still happily using #Floorp12 Beta as my daily browser, but made an important change last night. As a longterm #TST, then later #Sidebery, user & lover, the last several months of me deliberately forcing myself to use my #FirefoxNightly then more recently Floorp12 Beta profiles predicated on the native FF #VerticalTabs & #TabGroups has been interesting, yet filled with frequent regret, so invested have i been for years in the power of managing all my tabs in a sophisticated tree hierarchy.

FF native tab groups atm remain merely single-level, like Chromium & Vivaldi, thus far less powerful than either TST or Sidebery. I know from bitter experience last year with Floorp10 & Floorp11 that Sidebery is incompatible [due to the Floorp #Workspaces; not only do Sidebery's tabs not recognise/respect Floorp's Workspaces, because both softwares seek to control tab location, they severely clash, causing major browser instability & often tab loss]. Hence i've made no attempt to court further/similar disasters by trying Sidebery in Floorp12. So, last night i created a new profile in Floorp12 for use with TST, & that's what i'm now using. Though in Nightly i regard Sidebery superior to TST, in Floorp the reverse is true; the Floorp Dev/s seem to have taken particular steps to ensure TST compatibility, which thus integrate really well with Floorp's native Workspaces.

The one decided drawback atm of using this new profile however is that with TST active & native tabs hidden, there is no instant access to the important tab context-menu items for splitting-tabs, & moving them to other Workspaces. Fortunately, both those operations i need to use only rarely, so my clunky workaround, which would be untenable if i needed to do it dozens of times each day, is bearable albeit still irritating. When the occasional need arises to do either of those operations, i temporarily unhide the native tabs at the UI top, perform the requisite right-click ops on the applicable tabs, then re-hide said native tabsbar.

Tab stacks, vertical tabs, and workspaces are pretty good though a bit clunky. So far they seem capable of covering ~80% of what I used #Sidebery for. I do wish that there was a setting for multi-line titles so that custom browser css wasn't needed. Also the theming on the tab stacks could be better, depending on the theme (even the included ones) it can be a little difficult to determine what is and is not in a tab stack outside of seeing the collapse button.