I used the federate remote communities page on the web UI, but I could also have typed the ! notation into a comment. I didn’t try using the search to find it, but I don’t think it would have worked. When I used the federation machine two weeks ago, I only grabbed communities over a certain size on certain instances. MULTIVERSE has to be told to look for smaller communities.
Still, communities like femcelmemes and dankchristianmemes and lemmyshitpost (shit is also on the list) were picked up by the community federation machine with no tinkering.
So here’s what the code does. That list you found, of the seven_things_plus, it’s Rimu’s idea of “low effort communities”. As an admin, when I click on a user, I can see their “reputation”, which shows if they’ve been getting lots of downvotes or lots of upvotes. And I also have a checkbox that says something like “ignore reputation from low effort communities”. It’s designed to prevent karma farming. Rimu designed it so if a robot posts a lot of memes to 196 to farm karma and then starts posting ads for RAID SHADOW LEGENDS, I have the option of ignoring the meme reputation and still seeing that the bot isn’t contributing anything of value. But I have the checkbox turned off because I like memes.
This week I’m gonna try making a PR to change that list’s name to something more descriptive and make it configurable by admins. I’ve never contributed to PieFed before so we’ll see if I can understand enough of the code to do it. Wish Me luck.
Okay. It’s still unclear to me why piracy was not picked up by default. It’s a very big comm.
Anyhow, good luck on the merge request! Would be great to let the admin decide what to block instead of the weirdly random selection of comms and words on the list now.
Not block. Just karma-devalue. I’m gonna rename the variable to something like “unwanted reputation sources”. If an admin doesn’t want people farming rep by posting porn, they can put porn on the list. That’s not blocking, it’s just a data filter for admin eyes only.
I used the federate remote communities page on the web UI, but I could also have typed the ! notation into a comment. I didn’t try using the search to find it, but I don’t think it would have worked. When I used the federation machine two weeks ago, I only grabbed communities over a certain size on certain instances. MULTIVERSE has to be told to look for smaller communities.
Still, communities like femcelmemes and dankchristianmemes and lemmyshitpost (shit is also on the list) were picked up by the community federation machine with no tinkering.
So here’s what the code does. That list you found, of the seven_things_plus, it’s Rimu’s idea of “low effort communities”. As an admin, when I click on a user, I can see their “reputation”, which shows if they’ve been getting lots of downvotes or lots of upvotes. And I also have a checkbox that says something like “ignore reputation from low effort communities”. It’s designed to prevent karma farming. Rimu designed it so if a robot posts a lot of memes to 196 to farm karma and then starts posting ads for RAID SHADOW LEGENDS, I have the option of ignoring the meme reputation and still seeing that the bot isn’t contributing anything of value. But I have the checkbox turned off because I like memes.
This week I’m gonna try making a PR to change that list’s name to something more descriptive and make it configurable by admins. I’ve never contributed to PieFed before so we’ll see if I can understand enough of the code to do it. Wish Me luck.
Okay. It’s still unclear to me why piracy was not picked up by default. It’s a very big comm.
Anyhow, good luck on the merge request! Would be great to let the admin decide what to block instead of the weirdly random selection of comms and words on the list now.
Not block. Just karma-devalue. I’m gonna rename the variable to something like “unwanted reputation sources”. If an admin doesn’t want people farming rep by posting porn, they can put porn on the list. That’s not blocking, it’s just a data filter for admin eyes only.
So there are two purposes for this “bad list”
correct?
The federation filtering is blocking IMO. It affects what comms users of the instance can find (via search).
Anyway maybe in Your PR You should make a separately configurable list for each purpose. I don’t see a reason why it should be the same list.
No, just one purpose, the second one.