Thank you. Came here to say this. Microkernels are great for limited scope devices like microcontrollers but really suffer in general computing.
Thank you. Came here to say this. Microkernels are great for limited scope devices like microcontrollers but really suffer in general computing.
I’d still be looking it up as the husband. I wouldn’t want to risk giving my kid a name that sounds good but has a terrible etymology.
Being more specific, I basically mean object permanence. It won’t cease to exist without humans. Even that mythical Edenic paradise is an anthropocentric concept. Nothing like that existed for the majority of the earth’s history, nor did anything like it exist in most regions of the planet. Most known life is optimized for environments that are not particularly human-safe.
Nowhere do I suggest any of those things. In fact, opting out of anthropocentricism is breaking with views held throughout much of human history and used as an excuse to do nothing.
“actually, personal water consumption is a factor. . .”
If one is honest and looks at the data, personal scale water consumption is nearly meaningless.
Back to the main point though, I do not intend at all to brush off the destruction of habitats capable of supporting complex life but to be clear about the stakes. The world will continue to exist without us - we’re not that special. If we don’t work to stop a handful of sociopaths from rendering the world incapable of supporting human life, we’re screwed.
Nah mate. It would absolutely catastrophic. But the scope of who it would be catastrophic for is limited to the minority of known life. Humanity is insignificant to the universe but significant to us.
IMO, it is a distinction that is worthwhile. The universe is not anthropocentric. It doesn’t give two shits about humanity (it’s not, to our knowledge even sentient). Humanity is completely insignificant to nearly anything but humans. To me, it puts into perspective that noone and nothing in this indifferent universe is coming to save us from ourselves. It’s up to us.
Life will continue without us, just like it did before us. If the entirety of the world’s nuclear arsenals are used, there’s a good chance that microbes like Deinococus radiodurans will survive to evolve into new forms of complex life. The human species is far more fragile than the planet.
You could be sharing my experience. I’m still working at it and need to adjust meds some but getting treatment was life changing.
I haven’t used Windows in years and rarely think about it. But, ads. I hate ads with the burning fury of a thousand suns. Therefore, MS catches some fraction of that hate by putting them in the OS.
Plus, it’s unix-like and comes when an ssh client.
Had a moment like this a few months back. But I don’t smoke weed and everyone just got to watch me eat granola.
I don’t dare express the opinion to my wife, who is Irish, but I actually do enjoy both. They both have distinct flavors and are worth trying.
Lyon’s, the superior Irish tea.
I’m also a fan of Yunnan teas. Especially pu ehr (shou, sheng, compressed, loose, it’s all good) and Yunnan Noir.
I’ve got a few things that I need to get done in the next few days (hopefully mostly sorted today) but you’ve got me rather intrigued with this as a puzzle. I’ll see if I can get some time to sketch some thoughts out and maybe some high-level implementation of some bits in Python (it’s faster to POC things).
A few quick thoughts:
I think that an existing or novel protocol built on top of the Internet Protocol is likely the way to go. Following the OSI model, you can target Layer 4, with some simple stuff for higher layers. Client/Server (possibly the same binary) and associated automation should handle Layers 1-3 (translating between different carriers for Layers 1 and 2, and handling routing of data packets in Layer 3).
Message routing strategies and their impact on OpSec is worth consideration. By this I mean: broadcast-only vs targeted-only vs both vs hybrid. All three have trade-offs.
Broadcast-only: Makes it harder to know the intended destination of the message. Conversely, by being routed to either all known addresses or all approved addresses, it can be more vulnerable to interception by a compromised endpoint.
Targeted-only: May be harder to intercept as the path that a packet takes should result in it hitting fewer potential endpoints. Conversely, some form of addressing is necessary to know, at the least, the next hop in transit. This makes tracing the intended endpoint, as well as network hops much easier (ex. running a traceroute).
Both: Gains the advantages and disadvantages of both approaches, depending on the which mode the data is transmitted in. Ensuring that data is transmitted correctly becomes important and has implications on the requirement of maintaining known good versions of the client/server software to avoid unintentional or malicious improper routing.
Hybrid: Could take many forms but the one that comes to my mind is a multilevel hub and spoke architecture (I’ll draw this out). Basically, you end up having 2-3 “modes” for a client/server: hub, spoke, and endpoint. One or more client/servers operating in a hub “mode” act like traditional servers, kinda like a bulletin board, holding packets for local delivery or transmission to another hub. Client/servers in the spoke mode act as hops between hubs. Client/servers in the endpoint mode are the actual intended destination (this could be combined with the spoke mode). To protect endpoint identity, the destination could be part of the encrypted data packet allowing an endpoint to attempt to decrypt packets received from a hub locally, making it harder to know which endpoint a message is intended for. This does still require greater visibility of hub addresses for routing.
Encryption of packets is vital. Supporting some modularity might be of value so as to allow use of simpler cryptography for PoC but, the protocol should ensure that it is possible to break reverse compatibility (normally NOT what you want to do for networking protocols but avoiding an “it’s an old code but still checks out” situation would be more important).
Amateur radio should be avoided both in PoC and hypothetical “production” use cases. The ban on encryption is insurmountable there and illegal use of encryption could lead to hightened visibility because the FCC, historically, does not fuck around with illegal radio signals. This means all wireless should be below 1W in the US, in bands that are legal for unlicensed use.
Any physical layer that supports arbitrary data transfers should be possible. The implementation to support it would be part of the client/server. So, Bluetooth, 802.11, LORA, sneakernet, and many others could be hypothetically supported. Again, though, this relies on the protocol’s stack to be and to understand it, either directly, or translated by another component.
A web of trust may be a good approach for authentication and identity.
Indeed. I’d really suggest going for something based upon Internet Protocol, with any software that you need at endpoints to read and/or transmit. I might poke about at some ideas on the weekend (long holiday). What languages are you thinking to use?
Good call. You might try games like Tomb Raider or the first Prince of Persia reboot for movement accuracy.
L2P n00b! /J
In seriousness though, I find the trackpads to be very useful for precision. Unfortunately, you have to build up the skill, like anything else. Work at it over time and you should get there. For practice, really depends on what you want to play. I’d suggest something that has a good system for criticals/headshots. Looks like Aim Lab might work on the deck, so maybe try that?
Oh that’s interesting. I might suggest looking at implementations of IP Over Avian Carrier (IPoAC). And I do mean that seriously. The idea started as an April Fools RFC but some people have actually implemented it. Basically, just using a different physical layer.
As long as you’re using TCP (what SSH uses) or a similar protocol, you should be able to deal with a situation like that. You’d mainly need to ensure that your client and server are tuned to meet your needs. With TCP, every packet is considered important and if the receiver does not acknowledge receipt, the sender will resend.
I was not meaning to say that all microcontrollers (or microcontroller firmwares) run a microkernel but, rather, that microcontrollers are an environment where they can work well because the limited scope of what the device is expected to do and its necessarily supported peripherals can be much smaller, making the potential impact of context changes smaller.
For some good examples of microkernels for such purposes, take a look at FreeRTOS, ChibiOS, or Zephyr pre-1.6 (at which point architecture changed to a monolith because it is creeping towards general computing functionality).
As long as there’s some processing RAM and sufficient ROM, I’m sure that it can be crammed in there via firmware (in a sub-optimal way that makes people who have to maintain the code, including your future self, hate you and wish a more appropriate part were used).
Some madlads forked Linux to get it to work without an MMU, even getting it merged into the mainline kernel: https://en.m.wikipedia.org/wiki/ΜClinux
So, doable. Adviseable? Probably not in most cases but that’s subjective.