haventbeenlistening

joined 1 year ago
[–] haventbeenlistening@lemmy.world 9 points 11 months ago

Their user base has grown tremendously since they dropped support for SMS. Just read the article.

[–] haventbeenlistening@lemmy.world 7 points 1 year ago (1 children)

That machine he built will not be anything close to worthless after 6.6 years. I literally just last week moved my spare 1080 ti into a second gaming computer. It came out in 2017.

[–] haventbeenlistening@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (1 children)

Lemmy sure attracts some fucking characters. The guy simply pointed out that stealing isn't justified by a 60-second wait. And you are jumping in here ranting about the price of steak for some reason. You're not Robin Hood. You're just a dumbass with a keyboard.

Right. Applying any form of application-level encryption to the account IDs stored in the voting tables would prevent anyone without the secret from being able to find out who voted for what by peeking at the voting tables.

The more I think about this problem, the more solvable it seems to be.

[–] haventbeenlistening@lemmy.world 26 points 1 year ago (2 children)

It is only shocking if the expectation was set that your votes are private. If you wanted to avoid linking an identifiable account with their votes then you could use a de-identified user account to track a user's votes.

You could to perform deterministic hashing prior to persisting a vote to ensure that those looking at the database can't go backwards to find the specific users who voted on a post. But any service that knows the salt and hashing algorithm can start with a user account and determine that user's voting history.

This allows you to track up/down votes per user without allowing over-priviledged DBAs or malicious actors from poking around voting histories of identifiable users.