scroll-to-text-fragment VS App-bookmarks

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.

> What I do miss is a way to back them up from the command line.

I've written a Perl script that print bookmarks from Safari/Firefox/Chrome/Edge as <url><description>, but maybe it's too raw.<p><a href="https://github.com/kal247/App-bookmarks" rel="nofollow">https://github.com/kal247/App-bookmarks</a><p>I might add other formatting options (HTML or Template Toolkit) if there's enough interest.