Did you find a solution. The above comment with the database query should work. You can access the docker container where the database is running with docker exec -it instancedomain_postgres_1 busybox /bin/sh and then run psql -U databaseuser which by default is ‘lemmy’.

Check docker ps to know the exact name of the postgres container which in your case likely is lemmytalungorg_postgres_1

You should be able to purge the user if you visit their profile.

But… But… What about that 3D tour of the colosseum? That rocked.

You can use an app like Jerboa which supports unblurring.

Thank you so much for this. The HOT timeline is much better now and posts aren’t hidden <3

I’m really enjoying Jerboa. It stays lightweight and fast!

This has been changed with the latest version of Lemmy. Try this link: /c/aviation@lemmy.ml and check over at lemmy.ml/instances to make sure your instance is not blocked. (It’s at the very bottom, I just checked for you and it doesn’t look like it).

Edit: your instance is using an older version. Searching should still work. Try a couple of times. Make sure the search page is /search and use no filters

Boost for lemmy was just announced.

test

/c/lemmy@lemmy.ml

Woah, awesome. Indeed.

Try searching for the whole url in the search page with no filters selected

https://kbin.social/m/functionalprint

Hey, sorry I’m late to the party.

I would be willing to have a compromise in the we tag porn submissions with a trailing underscore or another identifiable but not intrusive symbol that users can then filter out.

Good to know. Thank you for your work!

If you’re an admin you can visit any remote community and click on “remove”. You can even remote comments or posts from being visible to users of your instance. It’s not ideal because it’s on a case by case basis instead of it being an instance-wide silence which is often a better solution that doesn’t require you to hunt down remote instances and remove them manually while it also doesn’t break federation.

You’ve got a good point. Ultimately every instance is responsible for its users and their behavior. Harassment should not be tolerated.

SIJW needs to make a decision. IMHO it’s perfectly fine to say that your instance is not prepared to deal with that kind of shit regardless of how open and accommodating you want to be.

If they believe there’s a space for “moderate trump supporters” that’s their decision but they are on the hook for any harassment caused by their users.

Admins can remove single remote communities instead of having to defederate the whole instance completely.

Yeah, I’ll better wait for now.

It will take a while for other instances to upgrade. Many of the are waiting a few days for v0.18.1 which brings a specific type of captcha that works with the HTTP request based of networking which v.0.18 uses.

Is it safe to update via ansible?

Hey there! Thank you for reaching out. I’ll definitely not block your instance then. Regarding postgres, first login to the postgres container with docker exec -it containername busybox /bin/sh

You can get the container name by running docker ps. Once inside login to psql console with psql -U lemmy

I’ve written this from memory, but it should be very similar if not the same.

EDIT: Consider saving the usernames and details of the bots that signed up. We might be able to use that for some analysis.