Cool, thanks

It states the OpenStreetMap data is from May. Is it fully offline and needs to wait for the next app update?

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

Exactly this. This procedure is so common that you need to take care in situations where you don’t want the headers, as some tools set them per default.

Everyone keeps saying that but I just can’t see it. The only time my mails were rejected was because I didn’t know what I was doing at the beginning of my journey. Now, whenever I changed my stack or did some major updates the past 20 years or so, I just go to 2-3 sites that analyze my mail server from the outside and tell me if there is anything wrong. The free tier is always more than enough. Just make sure there is at least one service in the list where you send an email to a generated mailbox and have it analyzed. Just looking at the mail server is not enough to find all potential configuration issues.

I aim at a100% score. It’s time consuming the first time around but later it’s just a breeze.

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.