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.

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.

They bought an implementation of RCS, the standard is still open. They even sell there implementation to a few telcos.

You cant self host it because you need to be a telco, it has telco specific protocols. Also, this is one of the things that probably should be gatekept to telcos, if everyone were able to spin up their own instance, the spam problem would be unmanageable.

Your looking for a conspiracy/monopoly that for once, doesnt exist due to Google being malicious. It exists because telcos are shit.

Google didn’t develop RCS, GSMA did. All google did was purchase the startup that actually developed a good implementation of it.

This isnt some gatekeeping exercise from google, they had nothing to do with RCS’s initial design and release. The carriers are entirely to blame for dragging their feet, although some are finally implementing their own servers (China is entirely RCS without google).

As for “federate it, decentralise it”, thats how it already is. Its called “hubbing”, but its basically federation. The networks run their server, and the federate messages between them. It isn’t centralised at all.

Was it kidnapped? Or did the carriers basically dump it on the fire stations doorstep? Not really googles fault if every carrier was too lazy to run their own RCS servers…

Uptime Kuma, only really care if it’s up or not. Got about 30 services monitored, sending notifications to Signal.

Yeah, I think this is a bad look. Lots of wrong/missing information, and looks lazily slopped together.

Nope, but didnt look terribly hard either. Just searched “programming”

Server browser doesnt seem to have all servers. Programming.dev is missing.

LLMs aren’t gonna give us any of those things. Thats just snake oil.

I don’t get why agents.MD needs to be committed. It feels a bit like committing IDE settings, everyone is going to have slightly different preferences, so its better to just have everyone do their own thing. If anything, I prefer to .gitignore itso it doesnt get accidentally committed.