Main account is here
Then yes, as I said… no users on sopuli.xyz have subscribed to your community yet: Suomi@suppo.fi - 0 subscribers
Other replies here have provided more info :)
Content for communities you’ve created on your instance will only be visible on other instances if a user there has subscribed to the community.
Or do you mean yours posts to communities homed to other instances do not show up?
In the UI? Not that I know of. From the database… sure:
docker exec -it <instancename>_postgres_1 sh
psql -U lemmy -h 127.0.0.1 -p 5432 -d lemmy
SELECT * from local_user;
If your VPS is purely for Lemmy, I’d suggest blowing it away and using the ansible playbook referenced here. I found the current docker-compose does not function, there are broken references to external nginx configs.
The icon on the left is “context”, on your home instance. On the right is the “fediverse” link, which takes you to the home instance of the poster.
Basically the same thing, one is local the other remote.
At least that is how I’ve come to understand them.
Yeah sounds like an issue on your instance… not sure exactly what. I’m on my own instance, see multiple comments here from @jonah@lemmy.one and yourself.
Votes and edits makes sense, sounds like a good guess to me!
Thanks for digging that up. Had been one of my outstanding questions. I agree with the initial requestor of that issue; it will be a major source of friction for users migrating to Lemmy from Reddit.
I’d like to be able to at least manually trigger the retrieval of a set of posts/comments as a user. Otherwise as the requestor noted, its going to make interacting with “new” communities difficult and unintuitive if you can’t see comments from before when it was synced to your local instance.
Browser works fine. But I’m not always at my PC. Seems like a missing feature in Jerboa?
Maybe I’m dumb, I can’t find how to add a new community to my subscribed list in Jerboa.
Ok, figured it out myself. For anyone else that needs it…
Run a shell within the postgres docker container:
docker exec -it <sitename>_postgres_1 sh
Connect to the postgres service:
psql -U lemmy -h 127.0.0.1 -p 5432 -d lemmy
Connect to the lemmy database:
\c lemmy
Then the user table: \d local_user
Find the user ID of the account you want to manually toggle, probably #1:
SELECT * from local_user;
Then update the email_verified and _accepted_application flag on the first account:
UPDATE local_user SET email_verified = ‘t’, accepted_application = ‘t’ WHERE id = 1;
lemmy=# UPDATE local_user SET email_verified = ‘t’, accepted_application = ‘t’ WHERE id = 3; UPDATE 1 lemmy=# UPDATE local_user SET email_verified = ‘t’, email_verified= ‘t’ WHERE id = 3; UPDATE 1 lemmy=#
Thats what I figured… I just have no idea how to do it. Can you point me to any info on how to do that? :)
The recommended ansible playbook, on a fresh Ubuntu 22.04 VM.
This is quite accurate. I’ve stood up my own lemmy instance… but hitting some pretty basic issues in the process. Not sure its ready for prime time.
Thats a different issue to what I encountered. For me the nginx docker config had a reference to the host nginx config… I had no nginx installed so “docker-compose up” failed.