YSK: If you set up a Lemmy instance, and follow the Docker setup instructions to the letter, it will send lemmy.ml your admin password during the setup process
So if you do the Docker setup, obeying the instructions and substituting everything that needs to get substituted, but don't proofread the files in detail and so miss that line 40 of docker-compose.yml doesn't have the variable {{domain}} like in every other location you need to write your domain, but instead just says LEMMY_UI_LEMMY_EXTERNAL_HOST=lemmy.ml and so you fail to change it away from lemmy.ml... then, everything will work, until you type in your admin password for the first time, at which point your browser will send a request to lemmy.ml which includes your admin username, your email address, and the admin password you're trying to set. And, also, of course your IP address wherever you are sitting and setting up the server.
I have no reason at all to think the Lemmy devs have set their server up to log this information when it comes in. nginx will throw it away by default, of course, but it would be easy for them to have it save it instead, if they wanted to. And my guess is most people won't use a different admin password once they figure out why creating their admin user isn't working and fix it.
@dessalines@lemmy.ml @nutomic@lemmy.ml I think you should fix the docker-compose.yml file not to do this.
cm0002 likes this.
Boomer Humor Doomergod
in reply to PhilipTheBucket • • •cm0002 likes this.
lorty
in reply to Boomer Humor Doomergod • • •cm0002 doesn't like this.
cm0002
in reply to lorty • • •Uh huh, just like how the instance/user block being horribly implemented to where it's just a barely functional mute is just a (4 year) "oversight". Funny how their "oversights" just so happen to have benefits to their efforts to push authoritarianism
lemmy.world/post/29072279
cm0002
2025-05-03 16:31:33