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.
I’ve got a whole 0.5kg bag of coffee for that much in Germany, and that’ll last me almost a month (~25 cups). What’s so good about Starbucks that it costs as much per cup?
So, “flies” from The Invincible? Microbots that pretty much conquered a planet, making it impossible for all life to exist on the planet’s surface. There was no “obeying” them, only dying or leaving.
Dude that wrote that (in 1964 no less) must’ve been a time traveler. Computers back then barely started being miniaturized, there were no home PCs, no smartphones or actual nano tech to speak of. Only recently we’ve started building microbots and nano scale mechanisms.
That’s not gold, it’s just a heat sheet.
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.
Just MusicBrainz and a general music folder. I either use a SMB share or Navidrome to listen to my library, depending what’s most convenient. I’ve noticed that Lidarr generates huge traffic spikes when it fetches album info, rate limiting it on my Pi Hole, so I’ve stopped using it. I don’t like the idea of automating downloading music anyway, I prefer to listen to it first then download if I like it.
I’ve never self hosted, started maybe two years ago. First I’ve started with a Raspberry Pi 3, but quickly decided that 1GB of ram, and limited power was not enough for my needs. I’ve got myself a Dell OptiPlex SFF (used), it came with 16GBs of ram, then I’ve added a 4TB HDD. I’d say, this is an “entry” piece of hardware, as it’s cheap and sips power (around 15-20W at idle). If you don’t need the disk space or much power, go with a micro (whichever manufacturer you chose, HP, Dell, IBM), they’re cute little boxes that make a RasPi seem both underpowered and overpriced (for a used one anyway).
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.