the latter, they are the largest instances, and it’s generally healthy to spread stuff out

Why not both?

in my opinion you are taking a serious breach of personal freedom far too lightly.

“check it out” does not involve handcuffs.

I’m sorry it doesn’t cater to your specific linguistic preferences, bro.

you know that’s not the part I’m referring to.

lol as if the comment above wasn’t condescending too.

Hexbear living up to the expectations as usual :D

oh wow be careful to not cut yourself on all that edge.

So could Russia, whats your point?

well, since the voting is public it’s easy to remove your votes and block your instance after the fact

I’ve learned today kbin and mbin exposes it to users too

hmm, how would the receiving instance verify? what happens if I send 100 random hashes?

That would be great. I’m not sure how to solve the problems that arises though. If i can send an anonymous vote to an instance, what stops me from sending 100?
Maybe there’s some smart cryptographical solution here that alludes me, but it seems hard, if possible.

yes, and any instance owner on any federated instance. Oh, and anyone on Kbin.

There I agree with you.
Making it public right now is useful to remove a dangerous false sense of privacy. But in the bigger picture I agree with you.

I wonder how one would solve that though. If you send a “vote” request without any user data, what stops you from sending 100?

To truly make that change, they would have to change how the federation works. Right now its visible to anyone who runs a server your server federates with.

I hear Mbin users can already see it.

admins and owners of any federated instance can already see votes.

tbf, github accounts are free

This is why they need to make this change, right now theres a false sense of privacy. If I really wanted to see your votes right now, all I need to do is to set up my own instance.