You should be able to purge the user if you visit their profile.
30-something grey wolf therian and furry. Admin of yiffit.net lemmy instance and packmates.org mastodon instance.
- 1 Post
- 11 Comments
Wander@yiffit.netto
Lemmy@lemmy.ml•It is crazy to me how much the lemmy experience has improved since joining here from Reddit a few weeks ago.English
7·3 years agoBut… But… What about that 3D tour of the colosseum? That rocked.
Wander@yiffit.netto
Lemmy@lemmy.ml•Is it possible to disable blurring for NSFW content?English
2·3 years agoYou 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!
Wander@yiffit.netOPto
Lemmy@lemmy.ml•PSA: if a remote community hasn't been fetched by your instance yet, you need to search for itEnglish
1·3 years agoThis 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
Wander@yiffit.netto
Lemmy@lemmy.ml•PSA: Many Lemmy instances are currently experiencing massive automated sign-ups (bots)! If you run an instance with open sign-ups, please read!
0·3 years ago99% of fedi instances should require sign-ups with applications and email. It does not make sense to let in users indiscriminately unless you have a 24h staff in charge of moderation.
There’s currently no way to do this. It’s a planned feature though.
Non taken!
Unfortunately it’s not possible at the moment for users. Maybe in the next release. I’d argue that it could solve a lot of problems is users could better curate the content they want to see or not see.
I run an instance that’s not to everyone’s taste and I’m worried that other admins will block is entirely if their users don’t have a way to do so.
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/shand then runpsql -U databaseuserwhich by default is ‘lemmy’.Check
docker psto know the exact name of the postgres container which in your case likely is lemmytalungorg_postgres_1