OneTab-Night-Mode VS scroll-to-text-fragment

Use the Onetab extension. Click the button and it stuffs all tabs into a big list, which you can go back to (ha! yeah right) or export to a text file that let's you ignore it for the rest of time without triggering the anxiety of having to decide to throw away information.

https://www.one-tab.com/

(Hopefully you're using something like Auto Tab Discord?) It gets to that many tabs before I stash them all away into OneTab. I've nearly 15k tabs in there.

I have used OneTab for a few years now. It's available for Firefox and Chrome as an extension. It will take all your tabs and save them all onto a single private tab. You can then go through that and organise it further into smaller groups.

You could get this extension: https://www.one-tab.com, one click and all the tabs are closed but saved as a list, so your addicted mind can think "I can look at them later.".

My fellow 100+ tabbers please try this add on: https://www.one-tab.com/

Self-hosted OneTab. OneTab currently is local only. I would like to have a self-hosted backend so all bookmarks could be synced across my devices (ideally, with E2EE).

There were some privacy concerns, regarding leaking of user information: https://github.com/WICG/scroll-to-text-fragment/issues/76

This doesn't make sense. There is no mystery about how scroll-to-text fragments should work. They're documented e.g. here: https://github.com/WICG/scroll-to-text-fragment

It's call "Text Fragments", and it was introduced to Chrome more than one year ago. https://github.com/WICG/scroll-to-text-fragment

I think it works in Chrome and Edge, but not in Firefox.

I kind of want to be able to upvote this post three times: once for the actual projects (which sound really cool!); once for introducing me to the term/joke "rakit"; and once for teaching me about the scroll to text fragment API – I had no idea that was a thing!

The most disturbing example of this I found recently is the new auto-highlighting feature Google proposed to the W3C then YOLO'd into chromium before people's concerns were met, because they have control of it and don't need industry approval to get that to happen. Here's an example convo with some of these topics raised.

Per web.dev, it is for Chromium based-browsers and other browsers have not signaled intent to support. This is quite a rabbit hole. Very recently there has been some spec discussion if you follow links in the pages I've linked here.