• 1 Post
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2023

help-circle



  • I’m pretty sure there is no particular reason why it’s done this way. It’s just the easiest method to coomunicate upvotes across different servers. There are already a lot of ideas for doing it differently or more efficient (e.g. vote aggregation) but that requires a more sophisticated architecture:

    • Vote aggregation also makes faking votes much more efficient and requires different detection methods. Of course, a spam server can also invent users or votes but it’s a bit more complicated.
    • Aggregation in any form can be hard to implement because it should be flexible enough to reduce load but not increase delay or make tracking a consistent state even harder. Finding the right configuration will be difficult and go through a lot of trial and error. Should be easier though now that more people are working on the code.
    • Keep in mind that Lemmy should also be able to communicate with other services across the Fediverse like Mastodon via ActivityPub. I’m not sure if there is something in the standard for message aggregation yet. It’s definitely being discussed because Mastodon, Pixelfed and Peertube all have or went thorugh the same growth problems as Lemmy in terms of scaling, spam and security concerns. If there’s a good solution it will likely come through the AP standard.









  • The reason sites all have the cookie permission dialog now is because of the GDPR, which has the right idea on data privacy, but the implementation wound up being so terrible that it winds up doing this.

    GDPR is not at fault here though, since it does not require asking for consent if the processed data is necessary for the purpose of the provided service. For example, a web shop usually wouldn’t have to ask for permission to store items in the shopping part because that is a necessary part of the online shopping process. In that sense, requiring the consent dialog for all unnecessary purposes is better as you can at least see who’s trying to screw you over. Don’t kill the messenger here.

    I think it’s also important to remember that websites can only get away with these annoyances because it a) is easily automatable and b) has been the default mode of operation for decades. If restaurant waiters today started asking guests if they could sell info on what and when you ate, who you were with, and what you looked like, everyone would be creeped out. Before GDPR, it was pretty much normalized to do the same thing on the internet without even asking for consent.