There should be an indicator when an instance no longer federates with a community besides posts no longer loading
-
As it stands right now, it looks like we have to just judge based off of how old posts are to see if we can still interact with a community.
-
As it stands right now, it looks like we have to just judge based off of how old posts are to see if we can still interact with a community.
Bonfire just instituted a “Federated” flag in their alpha. I think this could be useful.
-
As it stands right now, it looks like we have to just judge based off of how old posts are to see if we can still interact with a community.
wrote on last edited by [email protected]You mean like if there’s a community called
[email protected]and your home instance no longer federates with the instanceexample.com?If so, I’ll add that to Tesseract as it sounds useful.
-
As it stands right now, it looks like we have to just judge based off of how old posts are to see if we can still interact with a community.
This is already in nightly, you can see it on the test instance here https://voyager.lemmy.ml/c/[email protected]
-
As it stands right now, it looks like we have to just judge based off of how old posts are to see if we can still interact with a community.
wrote on last edited by [email protected]The best tool I know of is the Federation Checker, but something like it should definitely should be built into clients.
Notably, Beehaw is defederated from .world and sh.itjust.works, while dbzer0, quokk.au, and anarchist.nexus are defederated from feddit.org.
-
You mean like if there’s a community called
[email protected]and your home instance no longer federates with the instanceexample.com?If so, I’ll add that to Tesseract as it sounds useful.
Are you the creator of Tesseract? I love it except it doesn’t save my settings or my favorites and multi-communities. I’m not sure why and I’ve checked in the last 2 weeks. It’s been doing it a long time.
-
You mean like if there’s a community called
[email protected]and your home instance no longer federates with the instanceexample.com?If so, I’ll add that to Tesseract as it sounds useful.
wrote on last edited by [email protected]this would be an amazing addition! It would help avoid the disconnect between de-federated instances/communities
-
This is already in nightly, you can see it on the test instance here https://voyager.lemmy.ml/c/[email protected]
Make sure you visit in a browser aince apps wouldn’t have implemented an in development feature.
-
As it stands right now, it looks like we have to just judge based off of how old posts are to see if we can still interact with a community.
PieFed does this.
-
The best tool I know of is the Federation Checker, but something like it should definitely should be built into clients.
Notably, Beehaw is defederated from .world and sh.itjust.works, while dbzer0, quokk.au, and anarchist.nexus are defederated from feddit.org.
That’s a handy tool, thanks for posting it. Do you happen to know how the lists are sorted? It’s not alphabetical.
-
That’s a handy tool, thanks for posting it. Do you happen to know how the lists are sorted? It’s not alphabetical.
Not sure how; it’s also not by defederation date, otherwise feddit.org would be at or near the bottom of the list for dbzer0.
-
this would be an amazing addition! It would help avoid the disconnect between de-federated instances/communities
wrote on last edited by [email protected]Added
I also disabled the “Create Post” button if the community is on a defederated instance even though, technically, you can still post to your instance’s local copy (it just won’t federate).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.
-
PieFed does this.
How does this work anyway, and does it match with Lemmy’s approach?
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
-
It looks like this - https://piefed.social/c/[email protected]
-
It looks like this - https://piefed.social/c/[email protected]
Thanks, I mean, how does this work in the backend?
-
As it stands right now, it looks like we have to just judge based off of how old posts are to see if we can still interact with a community.
I feel like there should be an “are you alive” federation activity in activitypub, as well as an “I’m back” activity.
Servers go up and down enough that maybe it should be part of the spec
-
A heartbeat activity! Or maybe a ping.
I like it! Maybe I’ll write an FEP for it, lol.
-
Added
I also disabled the “Create Post” button if the community is on a defederated instance even though, technically, you can still post to your instance’s local copy (it just won’t federate).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.
That’s amazing to see, Regardless if it’s only one direction, that should still help wonders, thank you!
-
Are you the creator of Tesseract? I love it except it doesn’t save my settings or my favorites and multi-communities. I’m not sure why and I’ve checked in the last 2 weeks. It’s been doing it a long time.
Yep.
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.
-
Yep.
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.
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.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login