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.
You mean like if there’s a community called
!cats@example.comand your home instance no longer federates with the instanceexample.com?If so, I’ll add that to Tesseract as it sounds useful.
this would be an amazing addition! It would help avoid the disconnect between de-federated instances/communities
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).
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.
Bonfire just instituted a “Federated” flag in their alpha. I think this could be useful.
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.
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 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.
PieFed does this.
