your purple friend @maffsie@queer.party

extremely wired at this present moment in time.

thank you for taking my money so expediently @playdate@twitter.com

hey @panic@twitter.com @playdate@twitter.com i hope your servers are okay in 13 minutes!

still on edge from when the steam deck preorder reservations opened..

this localised branding thing is getting out of hand

my favourite thing is how news outlets -continue- to fearmonger for clicks despite the world currently being in a plague.

norovirus is something that happens every year, workplaces put signs and stuff out every year to reduce norovirus spread, yet this implies it's a new issue

man this new documentary about the final days of saddam hussein is already looking crazy

daylight savings lycanroc

this extremely sucks lmfao

i can pass docker arbitrary system devices, give it extremely granular cgroup and capability settings, but somehow there's absolutely -no- way to tell the linux kernel that a specific container should be allowed to call socket(AF_BLUETOOTH, ...)

turns out the reason you explicitly need to give the docker container host networking is because modern bluetooth interfaces use the AF_BLUETOOTH socket address family, which uhhhhhhhhhhhhh there's just.. literally no way to change without giving it host networking?

love how i’ve gotten to the point where my dockerised homebridge install needs to be able to access a BLE device, and literally every single post I can find online says you need to give it host networking and privileged mode to access the pi’s BT adapter