My bad, I have Bypass Paywalls Clean so I didn’t even notice the paywall!
My bad, I have Bypass Paywalls Clean so I didn’t even notice the paywall!
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.
It’s unbelievable what Microsoft can get away with in Edge…
Relevant Hacker News discussion: https://news.ycombinator.com/item?id=36295364
A significant number of subreddits shifting to private caused some expected stability issues, and we’ve been working on resolving the anticipated issue.
How in the world does setting a bunch of subs to private crash the website?
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.
docker-compose.yml
file and copy Lemmy’s nginx config into your system’s nginx config (e.g. /etc/nginx/
).
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/docker-compose.yml
file for the proxy
service to bind to whatever your external facing IP is.The default Lemmy nginx config should handle websockets properly. Are you putting it behind a second nginx layer?
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.