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?
I’ve restored the community. You can block it now.
Also, one of the ones I wasn’t going to block seems to also be instance-banned: !linuxmint@lemmy.world. Is there a reason for its (presumed) banning?
Doesn’t seem to have been removed. It was deleted by the creator
Blocked it 👍
Two other communities on the list, one from feddit.rocks and one from lemm.ee, seem to be on the list too given that they’re also unblockable, and should probably stay that way given that unlike the thunder one, they seem to target specific Lemmy users.
I guess I’ll ask the Arctic developer if there’s a way to detect instance-blocked communities to filter those two communities from my list as well.
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.
Sorry for going off-topic, but how do you best go about maintaining your blocklist from a UX standpoint? What interface works well for you? It tends to take me more clicks than I’d like to block coms at the moment.
Arctic (iOS and MacOS only, unfortunately) has built-in swipe actions for blocking and unblocking at the community and instance levels.
In addition to the standard federated community list, it also has a separate Lemmy community list that instead pulls its data from Lemmy Explorer. Since this instance doesn’t use Lemmy Federate, it’s both a useful means of finding communities that aren’t federated to this one yet, and also a useful means of blocking any uninteresting or otherwise unwanted ones. You can then have it filter out communities you’ve blocked, to avoid having to scroll past them again after.
Took some time to decide which communities I did or didn’t want, but down to 992 unblocked communities now, or hopefully 988-ish if instance-blocked ones can filtered out too.
Thanks, that sounds great!
