You mean like if there's a community called [!cats@example.com](/c/cats@example.com) and your home instance no longer federates with the instance example.com?
If so, I'll add that to Tesseract as it sounds useful.
You mean like if there's a community called [!cats@example.com](/c/cats@example.com) and your home instance no longer federates with the instance example.com?
If so, I'll add that to Tesseract as it sounds useful.
Bonfire just instituted a "Federated" flag in their alpha. I think this could be useful.
This is already in nightly, you can see it on the test instance here https://voyager.lemmy.ml/c/photography@lemmy.ml
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.
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
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/adultswim@lemm.ee
Thanks, I mean, how does this work in the backend?
Oh :)
Once per day a request is made all instances to retrieve the list of their admins. If that request fails then they're flagged as 'dormant'. If dormant for 5 days, flagged as 'gone forever' and then PieFed doesn't try to federate with them again and all their communities have that warning on them.
If any Activity arrives from a dormant / gone instance then it's restored to full operation.
all 20 comments