Well, in English, UTC is an acronym for Coordinated Universal Time, and in French its Temps Universel Coordonné.
Now you may have noticed that neither of those actually makes UTC. This comes from a previous naming pattern for universal time (UT1, UT2, …) (see https://en.wikipedia.org/wiki/Coordinated_Universal_Time ).
Well, if its unbreakable, then its either snake oil, or some variation on the one-time-pad (really depends on your definition of unbreakable).
But having read the article, this is definetly snake oil.
I have a number of things running in the background after booting, so here’s some numbers for you:
In addition to that, there’s always a number of systems services, most of which use a negligible amount of memory, but here’s some I’m just picking out because I recognize what they do:
Of course, these are just a snapshot of the systems state, and can only really give you a very rough idea of how much memory something might use at one point in time.
If you want to make your board game more complicated (probably not, but I like the idea, so I’m just throwing it in here), you could use it as an opportunity to teach virtual memory, segmentation, paging and internal vs external fragmentation. Maybe players get certain processes with memory requirements and have to fit them into their own main memory, and whoever can fit the most processes wins, or whoever cannot allocate memory for a new process looses. (I’m just writing down what’s coming out of my head, I don’t want to hijack your game idea, sorry.)
Yes, TinyCore-Core comes without a GUI (like the commenter above said, headless). When they say 28 MB RAM, that might even be overestimating it a bit. All of TinyCore-Core fits into just 17 MB. Of course that goes up if you need to install things, and I don’t know if it comes with an ssh-Server out-of-the-box. So for a proper server setup, 28 MB sounds pretty reasonable.
It blows my mind, that there is an entire Linux Distro, that fits into a modern processor’s cache. Who needs RAM anyways? (unfortunately, because of how cache works, we can’t actually use it without RAM)
If you run your services off of a homelab rack that dims the lights whenever you power it on
If you are in this situation, then you definetly should get some more power, or at least a UPS to make sure you don’t trip a breaker.
Ooh, very cool!
Are the two different pictures different wavelengths, or do you just have two seperate sensors? (I have no idea how this works, just a highschool level understanding of x-rays.)
That sounds pretty plausible, but I’m not sure.
The windows are only very slightly off center, inconsistent, and even the ones above the clock are as well (although the clock mechanism could extend both up and down).
But I also don’t have any better explanation.
amateur radio was illegal to encrypt
Amateur radio is still illegal to encrypt (with some exceptions for controlling satelites), because private communication isn’t the point of amateur radio.
Besides, (in most countries) there are some topics that are illegal to talk over amateur radio about, mainly stuff like politics and religion. You’re also not allowed to offer telecommunication services (i.e. pass messages on for others). Enforcing those sorts of laws would be impossible with encryption.
But to answer your question: I think we probably wouldn’t have had an internet. Authoritarian regimes thrive on stability and maintaining the status quo, I think someone high up would have quickly decided that developing that sort of tech is too risky.
I’ve never used CasaOS, so I can’t help you with that, but I run NetBird for remote access to my homelab. What you’re describing sounds to me like an issue I used to have with Tailscale.
I think NetBird might be trying to route your traffic through a STUN/TURN server to get around a NAT or firewall. A NAT (in case you haven’t heard of it) is a sort of “mapping” from one IPv4 address to many IPv4 addresses. Its used to "make more "addresses, otherwise we would have run out decades ago. (this is a simplification, its actually much more complicated)
The first thing to check here is: Are you behind a CG-NAT? (there’s probably some websites to check this)
If yes, then there is little you can do without setting up a VPS to get around it.
If that’s not it, then you’ll have to figure out how CasaOS handles networking internally. Your services might be behind a NAT inside.
As for ressources/information, I mostly stuck to the official docs.