GDPR does not distinguish between public or private data.
GDPR handles public data through propagation. If you download public data that is GDPR covered, the data you downloaded also becomes GDPR covered. You are required to follow all GDPR regulations while handling the downloaded data.
Remember, GDPR covers almost all "collected personal data". It does not matter if the data was originally public, and how/where the data was collected. It's all covered.
IDK about that, there are many claims from users of it being available on stable. I believe it's another one of those A-B test things so it's only available for a subset of stable users.
I would recommend you ditch the second nginx layer. It's a waste of resources and it can cause a multitude of issues if the configuration isn't done correctly.
If you are hosting multiple domains on the same server, disable the nginx container in the docker-compose.yml file and copy Lemmy's nginx config into your system's nginx config (e.g. /etc/nginx/).
If you go this route you should also delete the lemmyexternalproxy network, delete internal: true on the lemmyinternal network (required to enable port forwarding) and add port forwards to the lemmy and lemmy-ui docker services. Here's what that would look like: https://www.diffchecker.com/vjfEFuz6/
If you are not hosting multiple domains on the same server, simply edit the port forwards in the docker-compose.yml file for the proxy service to bind to whatever your external facing IP is.
Postgres is a database. Websockets is a communication method between the browser and the server.
So the infrastructure is like this:
Browser <--Websockets--> Server <--> Postgres
So there's a couple problems here. First of all, websockets are very resource heavy so too many of them will slow down the server, that's why they are working on replacing websockets with something else. And second, the database (Postgres) is getting overloaded so they need to figure out how to scale it up or use it more efficiently.
I don't think this is a problem. It's the same on reddit where you can have multiple gaming subreddits or multiple news subreddits. Eventually the communities will consolidate.
I don't think you can migrate communities yet but at least the content isn't lost if an instance goes down because it's cached on all federated instances.
I see the potential but Lemmy in its current state is very buggy. There needs to be a huge uptick in dev activity to iron out all the bugs and usability issues before June 30th hits. Otherwise, I see little hope of adoption.
The performance issues also need to fixed ASAP. Sure, you could just "use a different instance" but you can't even federate with overloaded instances!
GDPR does not distinguish between public or private data.
GDPR handles public data through propagation. If you download public data that is GDPR covered, the data you downloaded also becomes GDPR covered. You are required to follow all GDPR regulations while handling the downloaded data.
Remember, GDPR covers almost all "collected personal data". It does not matter if the data was originally public, and how/where the data was collected. It's all covered.
However, Lemmy instances may still be exempt from GDPR as they are non-commercial: https://gdpr-info.eu/recitals/no-18/
IANAL as usual.