Oh, and most purported "life hacks" are actually "life hurks."

Except the ones about rolling up your laundry. So satisfying.

Sometimes you write a piece of code that is "hacky," but kinda clever. Well done.

Other times, you write a piece of code that is both a nasty hack and really quite terrible to look at. That code isn't just hacky, it's downright "hurky." It's called that, because that's the sound you make at the back of your throat when you look at it.

I may be the only person who says "hurky," but now you can start saying that, too.

You're welcome.

(Hopefully in the context of fixing hurky code, not writing it.)

@GossiTheDog I'm far from asking you to delete anything, but after reading it, I must say that I'm surprised you chose to write it. If I didn't know who you were, I would have expected this to have been a "both sides are to blame in this conflict" RT hit piece.

In the reality where the aggressor is committing daily war crimes by shelling civilian infrastructure, done in the hopes that the resulting humanitarian crisis will DoS Europe with refugees -- real living, breathing, suffering human beings whose livelihoods have been destroyed and entire lives upturned -- pointing accusing fingers at Github for hosting code that can be used to DoS some of the banks used to finance those war crimes... is rather tone deaf. Sorry.

@daxtens I keep meaning to set up social.fauxpas.guru.

@toke let me know if the changes I pushed to the config helped at all.

@andyprice eventually, every HDD becomes an erry-go-round.

@jbowen yes, I should probably move it to lists.linux.dev. The current location is a bit of a long story, but I think going to linux.kernel.org should send you to the list page with subscription instructions.

@jbowen Yes, via sending a message to tools+subscribe@linux.kernel.org.

See: https://subspace.kernel.org/linux.kernel.org.html

b4 v0.11 should be out by the end of the week. There are improvements and new features for both maintainers and contributors, so if you're a regular user of b4, I would appreciate if you try the latest master.

https://lore.kernel.org/tools/20221206215340.556ov3bdfyf3qvyy@meerkat.local/

@jmorris It's supposed to become easier with the next major pleroma release. Moving accounts is one of those Mastodon API things, so it's not part of the activitypub protocol -- which is why it's lagging in implementation.

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.

@bug yes, that sounds painful. Having worked with researchers and other academicians, I'm also aware that someone's entire life's work can get upturned by a single unexpected discovery, so I guess an afternoon of hacking on something is but a small price to pay. :)

I hate it when I implement something and then immediately think of a better way to do it.

#b4

Periodic reminder not to set your system hostname to "linux.com". I really don't want to see your cPanel alerts.

.plan files + finger = the original microblogging platform

Me: I'm not actually sending this via SMTP, so just parse and save this 8bit data on this perfectly 8-bit friendly medium.
Python (possessed by SMTP Elder Gods): *croaks and dies*
Me: *FFS*

Me: I just want to send this 8bit message, k?
SMTP Elder Gods: Repent, ye puny mortal.

@chrboe @axboe ... and you're using a protocol written to send 7bit messages that was later extended to handle 8bit data in 3 possible ways. :)

@axboe The latest master should hopefully fix it for you. At least I bloody well hope so. :) I'm grumpy at Python right now.