

Nope, your uptime kuma speaks to it directly, and it basically acts as a signal client for you.


Nope, your uptime kuma speaks to it directly, and it basically acts as a signal client for you.


https://github.com/bbernhard/signal-cli-rest-api
Its very finicky to setup, but once you get it working its pretty good. Sometimes needs to be reauthenticated though.
Kuma notification settings:



Is lateral movement really a risk for you? Most internet malware is fully automated drive-by stuff. They hit you, gain execution and your part of their botnet. They don’t need to move laterally, because they have all the execution they need.
Moving laterally requires a human (or agent these days), which has a non-zero time and resource cost, so the only reason anyone is going to do that to you is if you are a very valuable target.
Do whatever you like for learning/fun, but I wouldn’t stress to much. Your risk level is probably very low.


NAS sits at 24w idle. Security cams are drawing 19w of poe power, but I suspect there is a bit more being used in total. I have another NUC using probably around 24w max.
I’ll slap some power meters on the switches and main nuc and try get some more accurate numbers.


Some models will actually respond better to abuse anyway. Plus it makes you feel better :)


They are definitely using user prompts to train future models, and if everyone is a dick, their next model will be a dick. Which I’m okay with tbh. I’m gonna be more abusive whenever I have to interact with any of the hosted models.


Uptime Kuma, only really care if it’s up or not. Got about 30 services monitored, sending notifications to Signal.
Maybe they have shitty distros? Yeah, I don’t get it either tbh.
I haven’t had a failed kernel update in years. Used to happen very occasionally with nvidia drivers, but honestly haven’t hit it in ages even with nvidia drivers.
To add on, the supervisor install was a terrible experience, I did it for years. Constant issues updating, very broken experience.
User process makes sense, but login shell is probably limited value. If your service gets pwn’d the attacker will spin up a reverse shell, and that isn’t protected by the login shell. You ideally want to use selinux/apparmor to prevent execution, or containers to limit the available execution environment.


https://esphome.io/components/serial_proxy/
https://tasmota.github.io/docs/Serial-to-TCP-Bridge/
A esp32 dev board and some soldering might work.


Those tariffs would likely have eaten their entire margin so they have to pass it on. Even Panic had to pass them on.
Perhaps they could have gambled on the tariffs being rolled back, but if they got it wrong they would have lost money.
Its just a no-win scenario unless you can predict the future.


Good for them. Are they selling direct to customers though? If yes, they have all the customer and payment details already, so it would be relatively easy?


Has any company given back the tariffs?
It honestly sounds like such a huge hassle to try give that money back. The amount of labor required would be huge, you’d need to check every receipt, probably manually. Make sure all of them are legit, aren’t double submitted


Don’t clouds mostly just rely on replication across zones though?
I would have thought tapes were just too slow to be useful in that environment.
I’ll read up on the IBM deep archive.


Does make you wonder who does use tape? Id assume big businesses just use cloud, so who is left that uses tape?


I didn’t look tbh, I just assumed it would be 1-2k. 8-10 is crazy.
Does kinda backup my point though :/


https://www.unitex.co.jp/en/products/hardware/lto/lto-tapedrive/
Found from a google, no experience with it.
Tape is not a nice medium for the self-hoster, the drives are expensive, the tapes need to be carefully stored securely (temperature and humidity controled). Its a lot of hassle. That said, if you find something good, I’m interested as well, so report back.
Dumb question, but have you ruled out the cable being bad or corrosion in the socket? Dropping to 100 is usually something bad with the cable.