What are you talking about? The issue to bring back captchas was only opened 4 days ago!
Captchas were only removed 2 weeks ago, no one spoke up then: https://github.com/LemmyNet/lemmy/issues/2922
The developers have nothing against captchas. They were the ones who originally built and added the feature: https://github.com/LemmyNet/lemmy/pull/1027
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.
I think there have been some API changes so you need both the new backend and the new frontend.
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…
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?
Doesn’t Reddit have multireddits? Lemmy can implement the same feature.
OP mentioned this.
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?
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 think they can horizontally scale the Postgres maybe? Postgres is probably the biggest performance bottleneck.
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 believe all comments on all communities you interact with are saved locally.
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!
EDIT: Looks like there are a lot of fixes coming in this PR: https://github.com/LemmyNet/lemmy-ui/pull/1081
Warning: Be careful, this might trigger this bug here: https://github.com/LemmyNet/lemmy/issues/3422#issuecomment-1616112264