Ancestors

Written by ALostInquirer@lemm.ee on 2024-09-24 at 18:31

Is there a setting for instances to disable voting from Local or All feeds?

https://lemm.ee/post/43158174

=> More informations about this toot | More toots from ALostInquirer@lemm.ee

Written by Andrew on 2024-09-24 at 18:50

I think lemmynsfw stopped people who weren't subscribed to a community from voting in it (because their communities for gay people were getting a lot of downvotes from All). If that's what you mean. I think it was a hack rather than a setting though (my info might be out of date)

=> More informations about this toot | More toots from andrew_s@piefed.social

Toot

Written by ALostInquirer@lemm.ee on 2024-09-24 at 18:56

Yeah, that’s along the lines of what I’m asking about, albeit instead of a subscription check more like, I think, however the instances disabling/removing downvoting have done so, but adjusting the scope strictly to the Local or All views.

Another approach to addressing outsider/passive voting behaviors.

=> More informations about this toot | More toots from ALostInquirer@lemm.ee

Descendants

Written by Andrew on 2024-09-24 at 19:07

I don't think that would be possible. The API is only sending "post_id" and "score" for votes, so the backend has no info on what feed a user used to send it. An instance could modify their official frontend to hide the ability to downvote from Local and All but they couldn't do anything about people using different frontends (e.g. all the various phone apps)

=> More informations about this toot | More toots from andrew_s@piefed.social

Written by ALostInquirer@lemm.ee on 2024-09-24 at 19:14

Interesting, thanks! It sounds like you could hide the ability to vote either way then on an instance’s frontend, but as you say, it wouldn’t really do much to address voting activity from either other frontends or instances.

=> More informations about this toot | More toots from ALostInquirer@lemm.ee

Proxy Information
Original URL
gemini://mastogem.picasoft.net/thread/113194054681074019
Status Code
Success (20)
Meta
text/gemini
Capsule Response Time
265.703049 milliseconds
Gemini-to-HTML Time
0.98675 milliseconds

This content has been proxied by September (3851b).