Block communities by name
-
Is it possible to block communities by name? Or is there any workaround to do so?
Specifically I am not interested in
.*Moeposts. So whenever a "SomethingMoe" pops up in my feed, I block that community. However, unlike most other communities, they seem to have a never ending source of permutations of their names. This can get very tiring, as blocking them makes the general feed contain less, but never any of these posts.I guess I could write a script, which blocks any community with the regex
/.*[Mm]oe.*/gmand run it periodically. But I am a lazy bugger and neither want to write the script nor run it semi-periodically. -
Is it possible to block communities by name? Or is there any workaround to do so?
Specifically I am not interested in
.*Moeposts. So whenever a "SomethingMoe" pops up in my feed, I block that community. However, unlike most other communities, they seem to have a never ending source of permutations of their names. This can get very tiring, as blocking them makes the general feed contain less, but never any of these posts.I guess I could write a script, which blocks any community with the regex
/.*[Mm]oe.*/gmand run it periodically. But I am a lazy bugger and neither want to write the script nor run it semi-periodically.wrote last edited by [email protected]I don't think there is an easy to do that.
But there aren't that many of them, this should be most of them:
-
I don't think there is an easy to do that.
But there aren't that many of them, this should be most of them:
tkanks! maybe just more than what i am used to, to get rid of a topic
-
tkanks! maybe just more than what i am used to, to get rid of a topic
Those all seem to be modded by the same two accounts with identical names...
It's going to be waaaaaay easier to just block their accounts, then to block all the weird communities they keep making.
Stuff like this is very unlikely to have active communities, just unhinged moderates who spam their special interest constantly.
Whats really fucking annoying is the guy who has accounts on 20 different instances and keeps making them to spam the same bullshit
-
Is it possible to block communities by name? Or is there any workaround to do so?
Specifically I am not interested in
.*Moeposts. So whenever a "SomethingMoe" pops up in my feed, I block that community. However, unlike most other communities, they seem to have a never ending source of permutations of their names. This can get very tiring, as blocking them makes the general feed contain less, but never any of these posts.I guess I could write a script, which blocks any community with the regex
/.*[Mm]oe.*/gmand run it periodically. But I am a lazy bugger and neither want to write the script nor run it semi-periodically.In general, I'd suggest browsing by "Subscribed" rather than "All".
First, "All" doesn't actually show you everything out there, because your home instance doesn't know about everything out there. It only shows you communities that at least one user on your home instance (lemmy.cafe, for you) has subscribed to. You're seeing content from communities on ".moe" TLD instances because at least one user on your home instance is subscribing to those communities. On very large Threadiverse instances, like maybe lemmy.world, with many users, this is closer to seeing everything, since odds are better that someone on your home instance has subscribed to it. But it's not everything.
But secondly, I've seen a number of posts from people who invariably don't like one type of content or another --- yours isn't one, to be fair --- complaining that lemmy defaults should exclude X from the All feed, for some X, because they don't like X and find it difficult to exclude X. And the problem is that there's no global X that fits everyone.
The Internet as a whole is a firehose, and invariably, there's stuff out there that people aren't going to want to see, and people who are going to create communities that someone doesn't like. Might be spam or just noise, might be test material, you name it.
If you really want to see everything out there, you're probably going to want a script anyway. You're probably going to want to pull down https://lemmyverse.net/communities or something similar --- they spider the Threadiverse, and do actually build a list of all communities out there --- which actually does list everything out there, then filter by whatever criteria you want, then subscribe to everything left.
EDIT:
on ".moe" TLD instances
Sounds like, from the other comment, that it's not ".moe" TLD instances that you're thinking of, but rather communities that end in "moe". Though in general, if the objection is to sexed-up young anime girls, I expect that it's most-likely inclusive of both.
-
Those all seem to be modded by the same two accounts with identical names...
It's going to be waaaaaay easier to just block their accounts, then to block all the weird communities they keep making.
Stuff like this is very unlikely to have active communities, just unhinged moderates who spam their special interest constantly.
Whats really fucking annoying is the guy who has accounts on 20 different instances and keeps making them to spam the same bullshit
UniversalMung or whoever?
-
In general, I'd suggest browsing by "Subscribed" rather than "All".
First, "All" doesn't actually show you everything out there, because your home instance doesn't know about everything out there. It only shows you communities that at least one user on your home instance (lemmy.cafe, for you) has subscribed to. You're seeing content from communities on ".moe" TLD instances because at least one user on your home instance is subscribing to those communities. On very large Threadiverse instances, like maybe lemmy.world, with many users, this is closer to seeing everything, since odds are better that someone on your home instance has subscribed to it. But it's not everything.
But secondly, I've seen a number of posts from people who invariably don't like one type of content or another --- yours isn't one, to be fair --- complaining that lemmy defaults should exclude X from the All feed, for some X, because they don't like X and find it difficult to exclude X. And the problem is that there's no global X that fits everyone.
The Internet as a whole is a firehose, and invariably, there's stuff out there that people aren't going to want to see, and people who are going to create communities that someone doesn't like. Might be spam or just noise, might be test material, you name it.
If you really want to see everything out there, you're probably going to want a script anyway. You're probably going to want to pull down https://lemmyverse.net/communities or something similar --- they spider the Threadiverse, and do actually build a list of all communities out there --- which actually does list everything out there, then filter by whatever criteria you want, then subscribe to everything left.
EDIT:
on ".moe" TLD instances
Sounds like, from the other comment, that it's not ".moe" TLD instances that you're thinking of, but rather communities that end in "moe". Though in general, if the objection is to sexed-up young anime girls, I expect that it's most-likely inclusive of both.
wrote last edited by [email protected]I disagree. I exclusively browse /all and not subs for discovery of new communities. I would miss out on so much if I never used all. How else do you even find a community to sub to? I just manually block anything I dislike. I think it's a better system than subs, personally.
-
Those all seem to be modded by the same two accounts with identical names...
It's going to be waaaaaay easier to just block their accounts, then to block all the weird communities they keep making.
Stuff like this is very unlikely to have active communities, just unhinged moderates who spam their special interest constantly.
Whats really fucking annoying is the guy who has accounts on 20 different instances and keeps making them to spam the same bullshit
11 of those comms are on ani.social, an anime-centric instance where it is totally legit to split "pictures of anime girls" into more specific comms. It's not unhinged or spam at all, but if you don't want to see anime, probably best to block ani.social tbh.
I for one like to see all the moe on top of my local feed and not pushed down to page 5 of global.
-
11 of those comms are on ani.social, an anime-centric instance where it is totally legit to split "pictures of anime girls" into more specific comms. It's not unhinged or spam at all, but if you don't want to see anime, probably best to block ani.social tbh.
I for one like to see all the moe on top of my local feed and not pushed down to page 5 of global.
Great, you're into weird anime sfw porn, thanks for letting me know.
I was super curious
-
Is it possible to block communities by name? Or is there any workaround to do so?
Specifically I am not interested in
.*Moeposts. So whenever a "SomethingMoe" pops up in my feed, I block that community. However, unlike most other communities, they seem to have a never ending source of permutations of their names. This can get very tiring, as blocking them makes the general feed contain less, but never any of these posts.I guess I could write a script, which blocks any community with the regex
/.*[Mm]oe.*/gmand run it periodically. But I am a lazy bugger and neither want to write the script nor run it semi-periodically.Keep doing what you're doing. Took months, but blocking communities I'm not interested in finally did make a noticeable impact on All. Just hit a few at a time each visit.
-
Is it possible to block communities by name? Or is there any workaround to do so?
Specifically I am not interested in
.*Moeposts. So whenever a "SomethingMoe" pops up in my feed, I block that community. However, unlike most other communities, they seem to have a never ending source of permutations of their names. This can get very tiring, as blocking them makes the general feed contain less, but never any of these posts.I guess I could write a script, which blocks any community with the regex
/.*[Mm]oe.*/gmand run it periodically. But I am a lazy bugger and neither want to write the script nor run it semi-periodically.@[email protected]
If you're using a browser (either desktop or some fork of Firefox on mobile) to use Lemmy, you can use uBlock Origin to hide certain content. On the plus side, this would work even when logged off from Lemmy or (in my case) without having a Lemmy account.
In "my filters", you can add rules such as:/.*lemmy.*.*/##.post-listing:has(.community-link:has-text("/^ich_iel/"))
Explanation:
-/.*lemmy.*.*/is a regexp to match any domain containing the word "lemmy" (e.g. lemmy.cafe, lemmy.world).
-##denotes a CSS rule.
-.post-listing:has(.community-link:has-text("/^ich_iel/"))is a set of nested CSS rules:
- it filters for every.post-listingelement...
- having any.community-linkelement...
- whose text content, in turn, would match the given regexp.
In my case,/^ich_iel/, a text which starts by "ich_iel", which is the name for a Lemmy community I'm not interested in, due to me not speaking German.
You can use whatever regexp you need. You can also use multiple rules using this pattern to filter out multiple things. You can replace the.community-linkwith other CSS classes to filter out post titles, usernames, instances, anything goes. -
@[email protected]
If you're using a browser (either desktop or some fork of Firefox on mobile) to use Lemmy, you can use uBlock Origin to hide certain content. On the plus side, this would work even when logged off from Lemmy or (in my case) without having a Lemmy account.
In "my filters", you can add rules such as:/.*lemmy.*.*/##.post-listing:has(.community-link:has-text("/^ich_iel/"))
Explanation:
-/.*lemmy.*.*/is a regexp to match any domain containing the word "lemmy" (e.g. lemmy.cafe, lemmy.world).
-##denotes a CSS rule.
-.post-listing:has(.community-link:has-text("/^ich_iel/"))is a set of nested CSS rules:
- it filters for every.post-listingelement...
- having any.community-linkelement...
- whose text content, in turn, would match the given regexp.
In my case,/^ich_iel/, a text which starts by "ich_iel", which is the name for a Lemmy community I'm not interested in, due to me not speaking German.
You can use whatever regexp you need. You can also use multiple rules using this pattern to filter out multiple things. You can replace the.community-linkwith other CSS classes to filter out post titles, usernames, instances, anything goes.Also a good option to have these "blocks" synced over multiple accounts. I did not think of uBlock Origin at all. Thanks for the Suggestion!
-
I don't think there is an easy to do that.
But there aren't that many of them, this should be most of them:
Oooh a couple I didn't have, thanks.
