#Microsoft really just did a #Plan9 from user to anti-user space
smh
@alex Yes, the “user interface” term is sort of the wrong way round: it puts the computer in the middle with various interfaces to peripherals: network interface, display interface, user interface. The user's just another peripheral.
We can officially say that we got some funds (https://nlnet.nl) to revive and continue our work about MirageVPN: https://github.com/roburio/miragevpn. We specially would like to provide a turn-key #VPN server as an #unikernel - I hope to deploy that on my side!
I’ve been thinking more about this recently because #HillelWayne (who authored the #TLAPlus book I’m reading) titled this talk “What we know we don’t know”: https://www.hillelwayne.com/talks/what-we-know-we-dont-know/
The talk is about
- the things that we think matter when building code but don’t,
- how the experiments to show this are pretty good,
- how we do CDD—charisma-driven development,
- the only three things we know work and work well:
1- enough sleep,
2- low stress, and
3- code reviews.
New blog post! This one is about using the magic of Zig's comptime to reduce mechanical noise in the implementation of Elixir/Erlang NIFs
Okay, so let me tell you about my doorbell, from a #networking perspective.
When you push the button by the door, it sends a message over the #zigbee wireless mesh network in my house. It probably goes through a few hops, getting relayed along the way by the various Zigbee light switches and "smart outlets" I have.
Once it makes it to my utility closet, it's received by a Zigbee-to-USB dongle, through a USB hub (a simple tree network) plugged into an SFF PC. From there, it gets fed into zigbee2mqtt, which, as the name implies, publishes it to my local #mqtt broker.
The mqtt broker is in the small #kubernetes cluster of #raspberrypi nodes I run in my utility closet. To get in (via a couple of #ethernet switch hops), it goes through #metallb, which is basically a proxy-ARP type service that advertises the IP address for the mqtt endpoint to the rest of my network, then passes the traffic to the appropriate container via a #linux veth device.
I have #HomeAssistant, running in the same Kubernetes cluster, subscribed to these events. Within Kubernetes, the message goes through the CNI plugin that I use, #flannel. If the message has to pass between hosts, Flannel encapsulates it in VXLAN, so that it can be directed to the correct veth on the destination host.
Because I like #NodeRed for automation tasks more than HomeAssistant, your press of the doorbell takes another hop within the Kubernetes cluster (via a REST call) so that NodeRed can decide whether it's within the time of day I want the doorbell to ring, etc. If we're all good, NodeRed publishes an mqtt message (more VXLANs, veths, etc.)
(Oh and it also sends a notification to my phone, which means another trip through the HomeAssistant container, and leaving my home network involves another soup of acronyms including VLANs, PoE, QoS, PPPoE, NAT or IPv6, DoH, and GPON. And maybe it goes over 5G depending on where my phone is.)
Of course something's got to actually make the "ding dong" sound, and that's another Raspberry Pi that sits on top of my grandmother clock. So to get *there* the message hops through a couple Ethernet switches and my home WiFi, where it gets received by a little custom daemon I wrote that plays the sound via an attached #HiFiBerry board. Oh but wait! We're not quite done with networking, because the sound gets played through PulseAudio, which is done through a UNIX domain socket.
SO ANYWAY, that's why my doorbell rarely works and why you've been standing outside in the snow for five minutes.
@strypey
Stallman performed a brilliant political/legal hack in GPL.
@mike_hales
But I think it's worth noting that Stallman's rearguard action has been remarkably effective. Without it, most servers and handhelds (except for iThings) would be running an OS controlled by Microsoft. Thanks to GNU and the GPL, Linux (the kernel) became available. So we have a plethora of GNU/Linux-based server OS, all of them vastly superior to WindBloats, and a plethora of handheld OS based on Android/Linux, and more, recently, mobile GNU/LInux.
(3/?)
"I think there’s a reason why many of the post ssb signed log gossipy social media protocols have gone from purely peer to peer to a hub and spoke model of content hosting. We’ve got easy cheap cloud computing, we should use it instead of making our phones work overtime. "
https://www.nos.social/blog/pivoting-from-ssb-to-nostr
Ae. Totally predictable that all the P2P networks would drift towards more federated models. P2P software made sense when everyone used a desktop, not a phone.
@strypey @slightlyoff @fabrice You are assuming these Googlers are not in that 0.1%. And your arguments are so deeply flawed as to be ridiculous. Opposing anyone getting fired who is or could one day be in a union is, frankly, ridiculous.
Shall we take a look at police unions, and some firings they have strongly opposed?
@strypey @slightlyoff @fabrice Or in short, I share no solidarity with people who voluntarily work to make the world worse for at least five times my salary, and you shouldn't either.
I'm checking out "Squeak By Example (6.0 Edition)." It's not only great for beginners but also a nice book, man!
"Just under a year ago... I offered these building blocks to forecast what could happen... Companies whose whole business is built around capturing attention."
#CharlesArthur, 2023
https://socialwarming.substack.com/p/hows-that-ai-tsunami-looking-a-year
Wow, that's almost as prescient as when I predicted a decade ago that companies would build whole businesses around slicing loafs of bread and wrapping them in a plastic sleeve ; )
I mean, come on. The Social Dilemma came out 3 years ago.
pro-libre software, pro-holisticism
pro-communalism, anti-consumerism
fan of #Plan9 and #HaikuOS
anti-witchhunt, see https://stallmansupport.org
I write software (C++) for a living.