Yes, I understand how web servers work (I have implemented them) ;-). I’ve also been involved in abuse investigations that involved crunching of 100s of GB of raw logs. If I wanted to figure out what posts you had read based on raw http logs, it would be a big pain in the neck involving matching your user ID with IP addresses, and trying to match HTTP queries with posts. While if there’s a database table that identifies every post that has been read by every user, all I have to do is type some SQL.
As for the invasiveness of that info, don’t you have any private life at all? Are you pro-XYZ about some political question while your boss is rabidly anti-XYZ? You probably don’t want him to know what you’re reading. Same if you’re getting sued by someone trying to dig up dirt on you, or if you are running for some kind of office (look at all the NSFW content aski3252 reads on Lemmy! Sinner!!!, etc). Or if you are in a country where some dictator gets into power and decides to round up all the Star Trek fans. You suspected something like that was coming, so you carefully avoided posting in the Star Trek communities, but unfortunately you were reading them and now you have been found out. Just use your imagination ;).
Re voting, let’s say there is a poll “Is Spez an idiot? Vote yes/no, poll closes on July 1”, and you vote in it. To stop you from voting twice, the server must remember until july 1 that you voted, but not how you voted. After July 1, it is impossible to vote again, so the info that you voted at all can be deleted. What currently happens instead seems to be that “aski3252 voted yes” is retained forever. There are some minor UI benefits to that, so I described it as iffy rather than outright evil. If it were up to me though, I would minimize the amount of info kept.
Yes, I understand how web servers work (I have implemented them) ;-). I’ve also been involved in abuse investigations that involved crunching of 100s of GB of raw logs. If I wanted to figure out what posts you had read based on raw http logs, it would be a big pain in the neck involving matching your user ID with IP addresses, and trying to match HTTP queries with posts. While if there’s a database table that identifies every post that has been read by every user, all I have to do is type some SQL.
As for the invasiveness of that info, don’t you have any private life at all? Are you pro-XYZ about some political question while your boss is rabidly anti-XYZ? You probably don’t want him to know what you’re reading. Same if you’re getting sued by someone trying to dig up dirt on you, or if you are running for some kind of office (look at all the NSFW content aski3252 reads on Lemmy! Sinner!!!, etc). Or if you are in a country where some dictator gets into power and decides to round up all the Star Trek fans. You suspected something like that was coming, so you carefully avoided posting in the Star Trek communities, but unfortunately you were reading them and now you have been found out. Just use your imagination ;).
Re voting, let’s say there is a poll “Is Spez an idiot? Vote yes/no, poll closes on July 1”, and you vote in it. To stop you from voting twice, the server must remember until july 1 that you voted, but not how you voted. After July 1, it is impossible to vote again, so the info that you voted at all can be deleted. What currently happens instead seems to be that “aski3252 voted yes” is retained forever. There are some minor UI benefits to that, so I described it as iffy rather than outright evil. If it were up to me though, I would minimize the amount of info kept.