I have ensured that I am not subscribed to any mags on centralized instances. E.g.
- lemmy.world (centralized by Cloudflare and by disproportionate user count)
- lemmy.ml (centralized by disproportionate user count)
- lemm.ee (centralized by Cloudflare)
- sh.itjust.works (centralized by Cloudflare)
- lemmy.ca (centralized by Cloudflare)
yet the main landing timeline is polluted with junky content from centralized instances. Apparently it’s the federated timeline of fedia not my home timeline with just my subscriptions. I found the subscriptions timeline in the top right corner to the left of my userid. very useful!
I would still like to browse the federated timeline but to filter out the above-listed domains. The user settings has a “blocked »domains” tab, but I see no way to add to that in the control panel. And from the content there is no “block domain” option, just a “more from domain” option. So overall there are bugs to fix and features needed:
(BUG) cannot add to settings»blocked»domains(works, just undocumented… must add one mag at a time)- (feature request) the main federated timeline filter (a funnel icon) could use a way to filter out centralized instances
- (feature request) the expanded menu of a post should have a “less from domain” option
- [new] (feature request) add support for blocking whole instances configurable by each user, not just specific mags.
- [new] (feature request) ability to still see mentions in blocked mags. If I post something in a mag then later block that mag, mentions still trigger notifications (good) but the post cannot be visited.
Fixing the bug would not exactly accommodate all the needs because although I don’t want to see new posts originating from lemmy.world, I still want to see comments from lemmy.world users.
There is no option to add blocks of any sort (mag/user/domain) from settings, so it’s more likely to be intentionally designed that way, i.e. you cannot add nor see a note on a user by going to their page either, you can only hover.
From how I understand it, you cannot block an instance entirely by blocking a domain i.e. fedia.io/d/lemm.ee, what’s blocked would be hosted content like lemm.ee/pictrs/..../[file] and not some link posted to lemm.ee/c/abc, you will have to block from the magazine page i.e. fedia.io/m/abc@lemm.ee to get rid of them one by one. Domain blocking is probably intended for sites i.e. fedia.io/d/www-bbc-com.cdn.ampproject.org
EDIT:
I think this is achievable via visiting fedia.io/d/lemmy.world/comments if you’re looking for a stream of any and all comments (not just replies to your own threads/posts), not completely certain though!
Ah, thanks for the tip. I see how it works now. Indeed it seems to be per-magazine and not per-instance. I’ll update the bug list.