No just the whole thing. It seems sort of extreme to do all this stuff in the code. This is not something the software should have inbuilt if you ask me.
I feel like you’re moving from moderation to sort of oppressive or authoritarian territory once you’re literally building a social credit system into your software. If you want that, sure use PieFed. I don’t want that, so I won’t.
It seems the chief complaint people have about Lemmy going to Piefed are how admins operate their instances. Not sure any of this will change that, or even help.
Not to mention all these are just a game for trolls and spammers to tool around with. Like: Up/downvotes were built before vote manipulation became a problem.
This stuff is the difference between building a bridge and governing who crosses it.
Its not vote manipulation as such here. Its much simpler than that. Lemmy has a spam problem. People coming in to just make shill communities selling a service or product or spamming advert posts across communities.
They usually get downvoted, but I can use Piefeds admin tools to filter for downvoted posts by new accounts. This usually catches most spammers like that. I can then ban them from piefed.social and pass that on to Lemmy admins.
Sounds like a flood control for community creation would be appropriate.
It used to be in the early days instances would vet users at signup. Is there no mechanism for an instance admin to do the same for the creation of a community? They just can’t be vetted before creation?
… Wow. I mean I already knew there was some questionable stuff with PieFed but this is honestly next level.
The blocking tool specifically? Most block functions on sites operate like Piefeds.
No just the whole thing. It seems sort of extreme to do all this stuff in the code. This is not something the software should have inbuilt if you ask me.
Why? Much of it is orientated around giving admins tools to deal with trolls/spammers/AI posters. An alert system.
I feel like you’re moving from moderation to sort of oppressive or authoritarian territory once you’re literally building a social credit system into your software. If you want that, sure use PieFed. I don’t want that, so I won’t.
So the reputation system. I’ll see if Rimu can be talked into making it instance level.
But its function is primarily to just catch out trolls and spammers. Make them more visible to admins.
It seems the chief complaint people have about Lemmy going to Piefed are how admins operate their instances. Not sure any of this will change that, or even help.
Not to mention all these are just a game for trolls and spammers to tool around with. Like: Up/downvotes were built before vote manipulation became a problem.
This stuff is the difference between building a bridge and governing who crosses it.
Its not vote manipulation as such here. Its much simpler than that. Lemmy has a spam problem. People coming in to just make shill communities selling a service or product or spamming advert posts across communities.
They usually get downvoted, but I can use Piefeds admin tools to filter for downvoted posts by new accounts. This usually catches most spammers like that. I can then ban them from piefed.social and pass that on to Lemmy admins.
A lot of Day 1 trolls are caught like this too.
Sounds like a flood control for community creation would be appropriate.
It used to be in the early days instances would vet users at signup. Is there no mechanism for an instance admin to do the same for the creation of a community? They just can’t be vetted before creation?