SatyrSack

u/SatyrSack@lemmy.sdf.org
44 posts · 357 comments

Recent posts

Recent comments

A bot might, but this post is pointing out how common it is for people who consider themselves AI experts to not recognize this diagram that is basically part of AI 101

Right, which is why Lemmy should optimally implement some firewall-esque whitelist/blacklist system instead of the blunt tool that is in place now. Users would get the full/fine control over their feed that you want, but implemented in a way that should confuse no one.

With that said, the fact that you currently still see comments from users on blocked instances is definitely a bug. Regardless of the outcome of this (whether a blacklist/whitelist system is added, your suggestion is implemented, or Lemmy filters just continue working like this forever), that needs to be solved.

Nothing. It makes sense to me that blocking an instance would block EVERYTHING from that instance. The "Subscribe" button on should probably currently be disabled on all communities on a blocked instance. To me, a block is a block. If someone wants to block something but allow a certain subset of that blocked thing, there needs to be some whitelist/blacklist system instead of the simpler "it's either blocked or it isn't" settings available right now.

This current behaviour does make the most sense to me. But I think it was the Tesseract dev who was experimenting with a "soft block" system that would provide the behaviour you want. You would be able to set a full instance block on the instance that works exactly as it does today, or you could instead set a soft block on it that allowed you to whitelist particular communities/users that you would still like to see.