Reddit was like that too... I always thought it was funny that you could unlike your post/comment and start at 0 🤷
@waveform.social
I like Photostructure as a way to browse my photos. It does logical deduping, and automatic organization of your photos (if you want it to). Like some others mentioned in this thread, it's a very young software, but the developer is very active and transparent about the progress.
Edit to add link: photostructure.com
For whatever my opinion is worth (I'm ~1350 blitz on lichess), if you're finding your openings boring, then just try something new. For me, it helps to keep in mind that the goal is to have fun, NOT to maintain a certain Elo.
Frustratingly, when you use psql on the terminal, it does not prompt you for a password. So I'm still not sure if the password works or not :(
Ahh, ok... if you add the -W option when logging in to psql (psql -U lemmy -W), it will prompt for the password.
The password works! So, apparently it's something with the connection string.
I just realized that entire instance is just a bot crossposting posts from reddit via a bot. I got excited looking at the post count, but didn't realize that the actual user engagement is next to nothing. So, I don't want to subscribe after all!
This makes sense, and I do have a dollar sign in my password...
However, I have confirmed that postgres does in fact parse the password correctly, as I can log in with the defined username/password combo directly using psql
So I think that disproves this theory, doesn't it?
edit: I tried getting rid of the dollar sign just in case... unfortunately I'm still getting the same error
Yeah the name you want for the database host is postgres, or whatever the container is named in the docker-compose.yml.
I was curious about this, and it turns out both work. I tested by pinging both postgres and lemmy_postgres_1, and both responded with the same IP address. Good to know, but I did go ahead and change it back to postgres
Maybe try a very simple password temporarily like test, rebuild the postgres container/delete the volumes and see if it works.
I did this, and I'm still getting the same error, so obviously something is wrong.
If you change the username for the db both for postgres and lemmy, do you get a different error about the new username?
I tried this... updated the user to lemmy1. The error message does indeed change to reflect the new user.
Super frustrating!
I don't know for sure... but my instinct is that NAT reflection is moot in that case, because your connection is going out past the edge router and doing the DNS query there, which will then direct you back to your public IP. I'm sure there's somebody around that knows the answer for certain!
I learned something interesting in doing some more testing...
Using the -W option does indeed prompt for a password, but it accepts any value entered at the password prompt. In order to actually authenticate with a password when using psql, you must modify the pg_hba.conf file to use scram-sha-256 as the method for type local.
When I do this, I am unable to authenticate (both while using my actual password, and also while using a password of "test".
And then I figured out the problem.
In my docker-compose.yml, I had put single quotes around my postgres password, thinking this would be safe per my understanding of this question. However, just to check, I tried logging in to psql using the password 'test'. Sure enough, it worked.
I found another stack exchange with some different advice on strings in yaml: https://stackoverflow.com/...
So, I tried my password again, without the single quotes... and it worked.
Perhaps this will help somebody beating their head against the wall in the future.
thanks for using Leebra!
go to feed...