sure thing.
one more thing you might want to look into would be a VPN. setting up a wireguard VPN docker is not that difficult as well: https://github.com/linuxserver/docker-wireguard
there are some pros and cons about this:
depends on your use case. if you're all alone on the nextcloud or have technical people accessing it, I would definitely suggest the wireguard VPN
Doesn’t have to be your real name, the scope of Art 4 GDPR is quite broad. An Email address, e.g. fuckspez69@provider.com is personal data if it’s, even just theoretically, possible to identify you…
No, that's not true.
The GDPR doesn't care how the personal data was obtained, that's why Art 4 GDPR specifically calls it "processing", not "collecting". However, it does protect only personal data: https://gdpr-info.eu/art-4-gdpr/
If you sent an Email to a company you could argue the same, that they were not "collecting" it, you handed the data in yourself. It doesn't work that way.
That's why Art 15 GDPR allows you to demand a data takeout of everything they know about you, in case of Reddit that includes all your posts and comments.
And of course the "right to be forgotten" (Art 17 GDPR) covers any of that data as well, but again only if it is personal data.
Reddit now just says that with deleting your username they de-personalised the data, so it isn't covered by GDPR anymore. That's technically correct. But if you wrote a comment with personal data in the comment, e.g., "Hey, my name is Patrick Smithereens, I live on High Street 666 in 1312 Arblfarg" they would absolutely need to delete that.
For "routing" your IP to your domain URL, you need to set up an A record in the DNS settings of your registrar: https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-a-record/
(Provided you really do have a static IP, with DSL or cable connections you get a dynamic IP (either every day or with a reconnect). Then you'd need to look up something called "Dynamic DNS".)
Then you need to forward some ports to your local machine, that is done in your router. Usually you can map any external port to any internal port, so you would just route all traffic that comes in on e.g. port 8000 to your local machine on port 80. (On a sidenote: what ISP blocks ports 80 and 443, lol? I'd switch ISP if possible).
But your choice of internal ports don't really matter, because that's job is better left to the reverse proxy. I'd suggest "Nginx Proxy Manager", which is a nginx proxy with a very nice GUI that comes as a docker. It makes routing ports and especially obtaining SSL certificates a breeze. I find that way more accessible than traefic or caddy or basic nginx. You'll find lots of tutorials for this.
So to recap: connect IP to URL with a DNS record at the domain registrar, forward some ports in your router, which ones doesn't really matter because you can just "bend" them anyway you like with the reverse proxy.
@psychopomp
@kbin.social