BlueBockser@programming.devtoSelfhosted@lemmy.world•ICANN approves use of .internal domain for your networkEnglish
21·
3 months agoNothing, this is not about that.
This change gives you the guarantee that .internal
domains will never be registered officially, so you can use them without the risk of your stuff breaking should ICANN ever decide to make whatever TLD you’re using an official TLD.
That scenario has happened in the past, for example for users of FR!TZBox routers which use fritz.box
. .box
became available for purchase and someone bought fritz.box
, which broke browser UIs. This could’ve even been used maliciously, but thankfully it wasn’t.
syncthing also relies on a web server for device discovery, it’s just that you’re probably using someone else’s server instead of hosting your own.
Correct me if I’m wrong, but I also think that Vaultwarden itself doesn’t have access to the unencrypted password database. In that sense it’s E2EE similar to KeePass, the only difference being that KeePass is a desktop app and Vaultwarden a web app.