It doesn’t, however, save any settings beyond your device. I’m working on a way to securely save those to whatever Tesseract server you use but don’t have it implemented yet.

Thank you for explaining that. I clear the cache quite often. I haven’t tried to save the favorites in a bit because I thought it was tied to the settings. Changing the settings each time isn’t a big deal, but saving favs kind of is. I’ll give it another try since it’s pretty great.

it doesn’t save my settings or my favorites and multi-communities.

It should save/persist the favorites to your browser’s local storage. If you’re using a browser that clears site data on close or something, then they’ll reset. But it also wouldn’t persist your profile and you’d have to log in every time, so… It doesn’t, however, save any settings beyond your device. I’m working on a way to securely save those to whatever Tesseract server you use but don’t have it implemented yet.

This version (1.4.42) also changes where and how the favorites, community groups, and filters are stored in addition to not storing useless data like the community sidebar info, etc. They’re also no longer stored inside your profile in a single local storage object. Since these save to the browser’s local storage, there’s a hard 5 MB limit per object (everything gets written to a JSON string), so maybe your profile exceeded that somehow? If so, there should be browser console logs to that effect. Regardless, this version splits those all up into separate storage objects to address that problem.

Not sure what you mean by multi-communities, though. There was a feature to create custom feeds (which is kind-of similar to multi-community) but I took that out a long time ago because API changes in 0.19.3+ made it untenable. I think that was removed in 1.4.40 or thereabouts, so if you’re on a version older than that, then maybe that feature is still present. That feature was pretty broken for a long time which is why I finally removed it and put it out of its misery.

I like it! Maybe I’ll write an FEP for it, lol.

Servers go up and down enough that maybe it should be part of the spec

I noticed crust was saying my dev instance was not federating anymore, which was neat. It was because I don’t leave my dev instance online all the time

Edit: This only works one way. i.e. it can only know if your instance is defederated from the community’s. If the community’s instance is defederated from yours, there will be no indicator because there’s no way to do it without a remote lookup which is both unreliable and inefficient at scale.

Notably, Beehaw is defederated from .world and sh.itjust.works, while dbzer0, quokk.au, and anarchist.nexus are defederated from feddit.org.

If so, I’ll add that to Tesseract as it sounds useful.