Shiori VS Firefox Account Server

Are you using all extractors when saving a page?

I tried ArchiveBox and Shiori, but neither stuck for some reason. The latter is a bit more lightweight, it can save the entire page as well as a Readability-based conversion: https://github.com/go-shiori/shiori/

I'm using shiori

what about shiori? I've been using it for a year now, works fine

Shiori is the way to go, it's a single binary written in Go which makes it easy as hell to move and backup. It's also a resource-efficient option. The downside is that it doesn't have a mobile app, no Kobo/Kindle support, and no offline caching capabilities.

Try going directly to the specific file (e.g., Shiori's README.md)

Updated Shiori link: https://github.com/go-shiori/shiori

Shiori is a self-hosted bookmark manager that uses tags and it's what I use now. https://github.com/go-shiori/shiori

I've been strongly preferring methods that let me tag items and have a good search - either in addition to or instead of putting them in a folder. If I don't like the "taxonomy" I can just add more tags, instead of constantly trying to figure out the one folder where everything should go.

I can share by creating an additional visitor user, or use the import/export commands. I hope those get built into the UI sometime, but I rarely share more than a single bookmark at a time.

It is an extra step to copy/paste links into Shiori versus browser built-in features, but I prefer not to trust or rely on browsers for my bookmarks unless at work. Seems like everyone wants sync those to accounts without my explicit consent.

Mozilla has the entire stack under their fxa repo: https://github.com/mozilla/fxa

I can't find this information on that page, but since changing your password didn't work either, file an issue on the Firefox Accounts Github repository.

I think syncstorage-rs with fxa can do the job with firefox, but i see this post which concerns me if this is even possible.

PM2 DevTools was born out of a desire to interact and do something with the logs FxA produced without needing to leave the browser. Specifically, when you sign up for a new account you need to enter an account verification code in the browser, and locally this is printed in one of the process logs.

They have a new all-in-one (https://github.com/mozilla/fxa) which seems nice. It might be my system but I cannot get it to actually run once installed. Will keep trying.

Looks like a feature request was made in May 2018, but has seen little traction: https://github.com/mozilla/fxa/issues/1405

You should check on the github repo for that https://github.com/mozilla/fxa