A related question, as I'm working on testing on the source code now. Is there supposed to be a distinction when an admin removes a comment vs. a moderator removing a comment? The testing scripts spins up 5 federated servers, and at the start they all just get 1 login each - which is the admin themselves. When you test creating a community, then the instance it is created on the creator (the admin) becomes both a community moderator and admin for that specific community.
For the majority of communities, an 'admin' isn't a mod, but they do have the ability to remove comments. But should a comment removal federate to all the subscribed instances of that community that it was removed. It makes a messy situation of expectations that a monolithic system like Reddit would be far more predictable to normal people about...
On the technical topic of renaming a domain of a Lemmy server... I think it is worth experimenting with the code. At minimum, I think it should be an option to try and keep the same login/passwords for users from the old install of Lemmy. But even that could prove tricky if a particular domain changed underllying ownership more than once - and user@domain became rewritten by an entirely different person. I guess in the real-world people do often get mail for previous residence of a house.
My biggest concern is legality because Lemmy claims to support privacy. I honestly think it's a bad idea to claim privacy because you run into so many problems. If the user never knows that their lemmy instance changed names and can't find it again, etc. Especially on technical topics, 15+ years of having Reddit keep messages from deleted user accounts offered a lot of great search engine hits. With Lemmy, a person moving to a different instance and deleting their account, so much content is going to get black-hole in favor of 50 instances having copies of a meme post or trivial website link - and solid original content (often in comment discussions) gets removed.
Up until early July, Lemmy was damned if you do, damned if you don't. Federation had massive performance overhead due to some bugs and each additional instance that went online and subscribed to the big 4 popular servers was causing an even worse load problem than if say 30 users had joined directly. Especially instances that wanted a fully populated All listing, that meant every single thing was being sent to the server even if nobody was really reading that stuff.
And things like searching for topic content are going to be pretty limited given these newer servers don't have much history.
The aftermath of this attempt to scale is that there is also likely a lot of duplicate data, conversations that are mostly repetitive and posts to the same topics. Let alone the bugs Lemmy has federating deletes and moderation removal that doesn't impact direct users on the main servers as much.
The project had gone on for 4 years without a lot of testing... old code like login form had all kinds of problems, etc. Lemmy-ui had almost no ability to cope with errors from the backend, and often error messages didn't even exist for the API calls. There was a huge rush to fix so many areas that were outright not working.
As I said last night, I don't know docker very well, and 7 weeks ago when I first tried to install Lemmy, I couldn't get docker install to work without problems, so I went with from-scratch install (which also gave me trouble, but a few of us figured it out).
Now, if I understand this, it is creating 3 different docker containers, one for nginx, one for lemmy-ui. Can someone who knows the docker setup chime in? Can't we just nuke/delete the nginx one and lemmy-ui one - and install them from fresh?
P.S. No big deal, but it is "SSL", and not "SSH", you can edit post titles on Lemmy!
ok, based on those test results (which they work for me too)... then your lemmy_server is running, the API engine is responding, giving me the list of communities.
You could, at this point, try another client - a smartphone client - and see if you can use your server?
The front-page https://lemmy.mindoki.com not working is the lemmy-ui service not talking to the backend (which is what your logs in the post show). I don't use Docker, so I'm not very good at figuring out how to get the two to talk together. But if a smartphone client works for you, then you know it's lemmy-ui that's your only real issue.
SSL works by hostname, not by IP address... so your test isn't valid to be using SSL. Nginx does the conversion (proxy) of SSL to non-SSL in Lemmy setups. EDIT: unless you are using SSL on port 1236, a setup I'm not familiar with.
At the moment, I’m just trying to make it run locally, but your idea is great and I sure will use it when things start to roll! I mean if I ever get it to work locally :-)
Well, it may be failing ONLY locally on the server, that's why I emphasize to test remotely. As you may be bypassing nginx which does the SSL to non-SSL translation.
Can it be so that the lemmy docker server tries to hit up pictrs on ssl?
That's why I'm trying to get you to just fetch routine stuff that doesn't involve picts.
Is the communities fetch giving you the failure with https? Then it's likely your proxy config, nginx. Server ins't setup right. I also suggest you try the API test of communities from various points, such as your workstation machine (outside the server), just so we aren't confused on context of within the docker or something.
Pretty big denial-of-service attack opportunity, a rogue instance could be setup, subscribe to community, and start admin-removing every comment.