this post was submitted on 27 Apr 2025
25 points (63.2% liked)

Open Source

36298 readers
464 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] JRaccoon@discuss.tchncs.de 10 points 2 days ago (2 children)

Compare your actions to releasing a 0-day exploit for a security vulnerability instead of responsibly disclosing. It doesn't help, it just causes chaos until the people who do the actual work can figure out a solution.

This comparison is not fair at all. It's not like the devs are unaware of this. They could start by removing the API endpoint that lists a post's votes, but they haven't, which means they seem to think it's okay for the instance admins to snoop on votes if they so wish.

[–] BrianTheeBiscuiteer@lemmy.world 4 points 2 days ago (1 children)

Then couldn't that give instances free reign to start creating fake votes?

[–] CaptDust@sh.itjust.works 5 points 2 days ago* (last edited 2 days ago)

The best part of the fediverse is anyone can run their own server. The worst part is anyone can run their own server.

Server Admins would need to defederate that instance, there is nothing else stopping someone from creating a manipulative instance that multiplies votes to influence the larger network.

[–] CanadaPlus@lemmy.sdf.org 2 points 2 days ago (1 children)

As I understand it, ActivityPub-compliance basically requires that a vote is tied to an actor. Although, they could have made a dummy actor do it. Maybe they were worried about stopping vote manipulation?

[–] lena@gregtech.eu 1 points 1 day ago

That's how piefed works iirc