FiskFisk33

joined 2 years ago
[–] FiskFisk33@startrek.website 5 points 1 year ago

a third player has connected

[–] FiskFisk33@startrek.website 2 points 1 year ago

in the context that wasn't very clear

[–] FiskFisk33@startrek.website 7 points 1 year ago

ah yes, Technology.

[–] FiskFisk33@startrek.website 24 points 1 year ago

missing a Dun in all the first three lines, and what is the rest supposed to be?

[–] FiskFisk33@startrek.website 5 points 1 year ago

or achieved unsuccessfully?

i cant decide

[–] FiskFisk33@startrek.website 8 points 1 year ago

in tab completion I trust...

[–] FiskFisk33@startrek.website 1 points 1 year ago

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

[–] FiskFisk33@startrek.website 2 points 1 year ago

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

[–] FiskFisk33@startrek.website 11 points 1 year ago (5 children)

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

[–] FiskFisk33@startrek.website 23 points 1 year ago (7 children)

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.

[–] FiskFisk33@startrek.website 6 points 1 year ago

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

[–] FiskFisk33@startrek.website 4 points 1 year ago (1 children)

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?

view more: ‹ prev next ›