If you’re running it in docker you can just check the logs, I do it like this: docker compose logs -f lemmy, and see if you have requests from any instance in the log stream. For me it goes pretty fast, but you can always ctrl+c to exit and scroll up to see what you’ve missed. Might not be the most optimal way, but it works for me.
Had to replace my UPS battery just a few days ago after a power outage reminded me that a replacement was well overdue. I share your feeling, now I can sleep knowing a power blip won’t knock out my servers and mess up my data.
Yea, I had to make a crontab task that resets lemmy every day. Hope it gets fixed in the future but for now it sorta works.
This may help: Container compatibility. MKV files will be remuxed when played via WebUI. Try playing an MP4 file and see if it’s the same.
TBH as I see it, this could be a good thing, especially if those patches were go upstream. Lemmy could end up DOS hardened as fuck if this continues. Hopefully the attacker will eventually run out of attack vectors, although from what I’m seeing, this could take months, as it’s been happening for a long time already.
I did just that a while ago. Seeing on my server what you’ve been seeing in yours I’ve just turned it off for a day or so, and when I turned it on just to be sure that I have to scrap it and start again, it started working just fine. So, I’d say, let it be, let it rest, come back to it later. Or I dunno, maybe it was just a fluke.
There’s a freeware (open source but copyrighted art) shooter called World of Padman, that’s pretty much what you’re describing.
EDIT: You wanted “modern” but, it’s slightly less so. Sorry.
Ironically Nitter stopped working lately, since Twitter started requiring users to be logged in to read anything.
Mind you that
PICTRS__API_KEYis the wrong variable, and should bePICTRS__SERVER__API_KEY. I’ve noticed it when Lemmy Thumbnail Cleaner complained about the api key being incorrect. Follow the repo page and check if your variables are correct.