Yep. While mods them self don’t cost nothing, in general I’d say (compared to what a cigarette smoker would spend) this activity is relatively cheap. Biggest cost for me is flavoring and nicotine. The rest is negligible.
Yep. While mods them self don’t cost nothing, in general I’d say (compared to what a cigarette smoker would spend) this activity is relatively cheap. Biggest cost for me is flavoring and nicotine. The rest is negligible.
As a vaper I support this notion. Disposable vapes should go. Pods with replaceable cartridges and preferably also replaceable batteries (yes, those exist) should take their place. I’m mostly a RBA guy, so my only waste is a bit of cotton, some glycol/glycerin and a bit of wire. Batteries will also need replacing, but not for another few years. Personally I hate pointless waste. Throwing away something that’s usable is a sin in my eyes. If you won’t use it at least let somebody else use it instead, that includes the perfectly good components in disposables that get thrown away like trash.
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.
Since I’ve started automating stuff I’ve got myself an Acurite wireless fridge and freezer thermometer (initially found out about it on Reddit, before it all went to shit and all). It both has a nice magnetic display and it transmits in 433MHz band, so a SDR dongle plugged into my Home Assistant machine can receive the temp readouts. So far it didn’t prevent any disasters, but at least I know how hot it needs to get for the fridge to start having trouble keeping cool.
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_KEY
is 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.