Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)ER
Posts
1
Comments
301
Joined
2 yr. ago

  • I was talking about the way the law was made. Why does it require every site to implement a function that the browser already has and does better. They could have made it a requirement for browsers to inform the user about his possibility to block cookies from certain domains on the first launch, just like they made Microsoft to inform about other available browsers after the first startup of Windows XP (I think it was XP...).

    But there is something even better coming I heard - there will be the possibility to have a 'trusted external service' handle the cookie opt-in-and-out for the users. WHY?! It looks like these laws are made by people without any kind of understanding how any of this even works...

  • I don't get why this is even needed. AFAIK the user can set sites that are not allowed to set cookies in the browser settings in chrome and Firefox at least. In theory this should work even better and more reliable than those damn popups.

  • Backups is the keyword. I run Vaultwarden on my internal network, the data gets backed up to an external hard drive, borgbase and another remote machine using borg backup. I also stored the passphrases for these backups in a KeePass database (that is backed up elsewhere). I don't think I need to worry about data loss. Plus - if the Server is not reachable the synced devices should still have access to the passwords.