There’s content coming from some specific instances that I’m not particularly interested in. When I’m browsing content outside of my local instance, can I prevent all content from one (or more) specific instance(s) from being displayed?
My current understanding is that you can only block individual communities, not entire instances.
It’s a bit unfortunate — I would also like to block at the instance level.
For real. The German communities are multiplying fast
Musste wohl deutsch lernen
Diese Kommentarsektion ist nun Eigentum der Bundesrepublik Deutschland
This is the way
How do you block communities?
On the website you can to go your account settings and there is a section for blocking users and communities
From the web interface it’s pretty easy. You can either go to the community page and click the “Block Community” button in the sidebar, or you can go to your Settings
or you can go to
Settings -> Blocksand manually search for the community to block there
If you’re using a mobile app it will depend on how the app has implemented it, but generally it involves going to the community page and tapping the hamburger/meatball (3 lines/3 dots) menu and selecting Block from there (might have to view the Sidebar, then block from there).
It seems not all of the apps have implemented blocking yet. I can’t seem to find a way to do it in wefwef, but Mlem and Memmy have it, for example.
Currently only way to block a entire instance is defedarting in instance to instance Level. So you would either need to convince your instance admin to defederate or host your own. But I don’t see a reason why this wouldn’t be possible in future. It can even probably be implemented by a third party client without any changes to Lemmy api
Kbin has this ability, but Lemmy does not (yet).
I don’t know enough about how Lemmy works on the back end - but maybe something like a PiHole blocking all traffic to the domains of instances you don’t like. I’m unsure if the device requests that data directly from the other instance or if the instance you’re connected to retrieves that data and sends it as it’s own.
All the data comes from your own instance afaik. So pi-hole wouldn’t work
Bummer, but kinda suspected that with all the talk about lag between instances. Thanks for the info
As far as I understand, it’s the latter. So Pi-hole would not help you here at all.
