There might be possible technical solutions to this using hashing. Hashing is like encryption in that the original cannot be extracted, but the hashed result is unique.
For example, a solution would be to have a VOTES table with an indexed column that is a hash of a combination of the user ID, post ID, (and perhaps another "salt", not sure). When a vote is made, the VOTES table is checked that the record (vote) does not already exist, gets an insert, and then a COUNTER is triggered for the actual vote count. (COUNTER is a db command that simply updates a counter). The hash would prevent multiple votes from the same user (as the salted hash is unique), and it would also prevent identifying who the user is from the table.
I'm surprised by the pushback (although I haven't read the books and thus did not have any preconceived notions). I loved season 1 and have watched it multiple times. I love shows that builds a world, and this one does so epically. I also am intrigued by the immense time scales involved. I also thought the pacing of the mysteries introduced was very good (I've been a bit disappointed in Silo for that reason). Anyway, I can't wait for season 2!
I could always add 'Reddit' to a Google search and get information from real people. With the rise of bot sites/articles, this was my way of getting answers online.
Lemmy is great for learning new or interesting things, and I'm glad it's here. I just am not sure how to get answers from real people anymore
There might be possible technical solutions to this using hashing. Hashing is like encryption in that the original cannot be extracted, but the hashed result is unique.
For example, a solution would be to have a VOTES table with an indexed column that is a hash of a combination of the user ID, post ID, (and perhaps another "salt", not sure). When a vote is made, the VOTES table is checked that the record (vote) does not already exist, gets an insert, and then a COUNTER is triggered for the actual vote count. (COUNTER is a db command that simply updates a counter). The hash would prevent multiple votes from the same user (as the salted hash is unique), and it would also prevent identifying who the user is from the table.