1Password can’t fail that hard easily. They’ve done great write-ups to compare their architecture to that of LastPass. Long story short: it’s the secret key that protects you: https://blog.1password.com/what-the-secret-key-does/

Trouble with those tests is, that they become unreliable or even meaningless, when you have done then once before, let alone daily.

Coffee seems to be a self enforcing meme at this point. It’s not unhealthy enough to have suffered the same fate as cigarettes. Which had pretty much the same jokes not too long ago.

Paperless -> Paperless-ng -> Paperless-ngx

Having a static battery in the house that gets additional cycles, isn’t a big issue. Who cares if the capacity decreases by an additional 10 percent because of added cycles. Just get a battery that’s 10 percent larger from the start or add additional cells when you feel like it. In a mobile form factor, 10 percent can be a big difference. You can’t just scale up the battery when you feel like it and in the worst case scenario you would have to replace it. That’s why I would always be very conservative with using a car battery that way.

Is there a difference between regulations regarding eggs between the US and Canada? Eggs in the US are dirt cheap because almost nothing surrounding poultry is regulated. I’m happy to pay the premium in Germany for minimum living conditions, antibiotics restrictions, no culled male chicks, etc. but I also realize that not everyone here is as fortunate.

Wireguard is very lightweight and it just works. No overly complex setup, tools, matching protocols, algorithms, versions, etc. It just works and it’s simple UDP traffic. It’s the first self hosted VPN that I actually love and that works on all my machines, mobiles, VMs with just a config file to fine tune what should go over the line.

Yes, I agree. This use case likely wasn’t considered when the law was written. We’ll see how things turn out in the future because at some point we will have enough very knowledgeable people regarding GDPR in the community who are willing and even keen on steering the project in the right direction towards compliance.

Most of your points seem to be spot on from what I understand as well. However, I believe that the GDPR requirements can and should be baked into Lemmy itself. This would prevent the fragmentation you mentioned. A guarantee of removing user data as requested while federated plus a guarantee to remove stale user data while defederated since requests won’t get through in that case. That would “just” leave the list of processors. This one can be very tricky because you are not just sharing data with your home instance and their federated instances but also with the federated instances of those federated instances. The home instance has no way of learning about the 2nd degree federation. I have no idea how to get the network of data sharing GDPR compliant and I think this is the mich more complicated part that your proposal also suffers from.

Almost everything has been mentioned already so I just stick with the unusual: I host a private MediaWiki instance for note taking in my pen and paper rounds. It’s amazing once the other players got a bit more comfortable how to use it well regarding templates, categories and articles. My only regret is that I didn’t set up new instances per gaming group.