In maintaining my Lemmy blocklist, I noticed that I was unable to block the thunder@lemmy.world community, despite it seemingly existing if I look for it on lemmy.world directly.
As it doesn’t load when accessed via this instance (lemmy.dbzer0.com/c/thunder@lemmy.world), has it been defederated?
It has been removed on this instance
Out of curiosity why was it removed anyway?
Beats me. It must have been a mistake i guess, i’ve restored it now
Is there a way to tell which communities have been removed from an instance in that manner?
The Arctic app automatically removes communities from blocked instances from its integrated Lemmy Explorer list, but seemingly not blocked communities from unblocked instances, unfortunately.
Sorry, i don’t know. @db0@lemmy.dbzer0.com can you answer?
Although i am curious, why are you trying to block a community that is removed here? Interested to hear your answer.
I didn’t remove it myself. Can the modlog reveal which mod it was?
No, can’t see. It might have been removed by accident. Doesn’t seem to be harmful. Should we restore it?
I’ll leave the decision and the responsibility to you :P
To maximize the value of my All feed, I preemptively block communities whose posts I don’t think I’ll find interesting, minimizing how much All feed scrolling I end up needing to do.
While I don’t need to block communities that are already instance-blocked, I’d still rather they not clutter the app’s Lemmy Explorer feed, hence why I had asked the developer to filter out communities from blocked instances. If it’s possible to tell which communities are blocked at the instance level, I’m hoping that the Arctic developer can extend the current filtering to communities blocked at the instance level to de-clutter the Lemmy Explorer list further.