34·
1 day agoAh, well unfortunately gives a deeply AI feel with how it translates it.
Skavau
Piefed.social Staff
Community owner of !television@piefed.social and !obscuremusic@piefed.social
- 15 Posts
- 818 Comments
Joined 11 months ago
Cake day: March 18th, 2025
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Why are you replying with AI
3·2 days agoit comes up as an option when you click on the “…” of a post
Community moderators can also directly see who upvotes or downvotes posts and comments on their community.
It’s not just through lemvotes.
Voting in itself isn’t necessarily the issue. It’s users being able to see those scores that feeds the echo chamber.
To be clear, most users can’t easily see votes. Only community moderators can quickly access vote data within communities they moderate - and instance admins can see all votes. Yes, people /can/ go to lemvotes, but it’s often just not worth it.
I think it being transparent in this way is good for the fediverse.
It is unpopular, because there’d be no way for communities to distinguish quality vs. poor quality or trolling content.
It’s a different system if I recall, however it works as it is opt-out.
I’m pushing for major Piefed instances to be able to network together, so when one instance adds or federates a new community - it will automatically network to other piefed instances.
That admin instance function would of course, have to remain optional though - as small personal instances would find that welcome - but it would automate a lot of this.
Apps do work with Piefed, but they do not necessarily have all the features Piefed has.
I didn’t make a statement, I just asked you a question - trying to see where you’re at regarding moderation in general.
Legit question: Do you oppose any and all moderation, and quality of life tools to that end for moderators and/or instance admins?
The tools for stopping bad behavior can be used to stop any behavior.
Not really. Do you know what the tools are specifically? They’re just isolating the behaviour of new users for instance admins to catch tendencies often presented by spammers, trolls, bots and AI posters. There’s nothing baked in that can specifically target a specific group.
There already are various lemmy instances known for partisanship moderation without any specific tools.
Just confirming. I don’t see that as a bad thing though. The instance tools are designed to make it easier to catch spammers, trolls and AI posts.
"Alright, it doesn’t do any defederation, this function just controls what the api reports. It will list which of those four instances the instance is defederated from but that doesn’t look like it is actually used anywhere to do something…let me grab you links here is where piefed digests this api endpoint to populate the instance_chooser table, and the defed_list field isn’t actually used at all
Piefed provides instance owners and admins with more tools to catch bad behaviour, that’s absolutely true.
No, I don’t run an instance myself personally. I can see the defederated instances in the admin toolbox though. I’m not going to purge them all briefly just to experiment. But I don’t believe piefed.zip has any servers they refuse federation with (I can ask demi if he actually does defederate with anyone either on lemmy.zip or piefed.zip), and given the inclusion of lemmy.ml in that list - I suspect it doesn’t work like that in the first place if you were to do so.
Also, this is regarding the instance chooser in the code.
Okay? And as I’ve told you, there are active Piefed instances THAT ARE FEDERATED WITH HEXBEAR, LEMMYGRAD AND HILARIOUSCHAOS. I’ve never heard anything about the system automatically re-applying those instances in the event of an instance wiping all preset defederations. Lemmy.zip, and thus Piefed.zip has no defederation and they currently federate with those instances.
Notably, lemmy.ml is listed there too - which piefed.social does not defederate from, much less anywhere else.
Piefed has a bunch of tools Lemmy doesn’t have: Flairs, Hashtags, Custom Feeds (Private and Public), Scheduled Posts, Combined comment sections for crossposts, Emote Reactions, Events, Polls
Like 80 or so are also defederated.
Afaiu if you try to 100% federate by having no defederated instances, this overrides and defederates from these 4 again.
How would you know this at all? You run a Piefed server, have you?
Why are you trying to lecture me about how Piefed must work when you’ve never run or looked at Piefed from an admin perspective?
I don’t see a problem here. This is oddly specific, but it’s rooted in anti-downvoting spam.
There is a setting to turn that on or off at https://piefed.social/admin/misc, “Filter out comments that are simply a form of this”
I don’t see why this is so inherently onerous to you in principle. Trolls/spammers etc are serious problems on sites like Lemmy and Piefed. If you’re a new account and you’ve managed to get -100 reputation that quickly, it’s not a good sign. If and as the Fediverse grows, instance owners are going to need more observation tools to catch this type of stuff.
The AI detection is going to be poor. But I’ve seen a lot of AI posters right now caught through this. use of the em-dash is very much a sign, unfortunately. It doesn’t ban them by the way. It just flags new accounts doing it to admins.
If every instance was Piefed, you simply wouldn’t be able to reply to anyone who has blocked you. “Reply” is essentially faded out. The difference is that Lemmy doesn’t implement the block function in the same way, so Piefed just throws out replies by blocked users to the person who has blocked them coming from Lemmy. That’s the mismatch at play here.
If you can somehow still reply via a Piefed instance, it is bugged and not working as intended.
This can be turned off. It also defederates from hilariouschaos and others.
And no, it does not defederate from lemmy.ml out of the box. You are completely misunderstanding that code. I have already addressed this here.
"Alright, it doesn’t do any defederation, this function just controls what the api reports. It will list which of those four instances the instance is defederated from but that doesn’t look like it is actually used anywhere to do something…let me grab you links here is where piefed digests this api endpoint to populate the instance_chooser table, and the defed_list field isn’t actually used at all
It has been scrubbed, but it also never really functioned in the first place.