spoiler
It's a reference to urethral sounding.
Search it at your own risk.
spoiler
It's a reference to urethral sounding.
Search it at your own risk.
Lmao, how have I never put that one together?
You lose comment history and all that jazz too but it's better than nothing. I'm not sure if devs plan to implement a way to do it but it's one of the reasons I decided to roll my own instance. Nothing more frustrating than using someone else's and losing access while they take days to get it back up.
It's a special feature in Sync. Just long press an option in settings and it copies the markdown to your clipboard
This usually happens to me after I check my inbox if there's nothing there. A quick force close and reopen always fixes it. Not ideal, but not a big enough problem for me to try to do something about it
Same
Device information
Sync version: v23.08.12-23:05
Sync flavor: googlePlay
Ultra user: true
View type: Slides
Push enabled: false
Device: panther
Model: Google Pixel 7
Android: 13
As someone else already said, automated backups should be up on the priority list.
But also maybe try out self hosting Lemmy. It's been a fun little journey and helped me flesh out my Caddy config more than I thought possible.
They have a similar integration with Bitwarden that I've used a bit. I ended up stopping though because I rely on a catch-all and just give out companyname@ or something generic like work@ or family@. Sure it's easy to guess but I haven't had any spam issues in the ~15 years I've been operating this way.
Nobody actually gets my Fastmail login address though. I picked a random string on one of their domains that's literally only used to sign in. A fun little added obscurity feature.
Like others have asked, how exactly did you create these containers? If they were through Portainer did you use a compose file in a stack or did you use the GUI the entire way?
This will nuke them assuming you don't have something recreating them.
docker ps -a # find your rogue container, copy the container id, my example is a0ff66a83c73
docker stop a0ff66a83c73
docker rm a0ff66a83c73
My suggestion is to go through the process you did to try to deploy them and clean it up from that direction.
For what it's worth you can convert the database to postgres if you want. I tried it out a few weeks ago and went flawlessly.
https://docs.nextcloud.com/server/latest/admin_manual/configuration_database/db_conversion.html