an idea for a fun twist: capture some slow motion footage of yourself building something out of wood or metal. make sure to wear a plaid shirt and have slightly dirty, tough, callused hands for maximum effect. you'll be surprised at how well the music works with this type of shot!
basically, find some rock music with hand claps that sounds like they were recorded in an old barn, mixed with just a touch of tambourine, a dark, highly distorted bass, really punchy drums, tempo around 90 or so bpm, if you really want spice it up, a reverbed crowd of rowdy, enthusiastic boys going "oh" every few bars. they won't know what hit em
guys I have a really cool idea: you should make a video about a tool of some sort, and have this be the background music. it'll blow some minds https://youtu.be/HhXQJzfxOg4
electric car idea: car that can only go north or south using a https://en.wikipedia.org/wiki/Magnetorquer
you can put it back up on maybe the 18th or so, but people are getting shameless these days and putting them back as soon as the the 13th or 14th. absolutely disgraceful
I'm gonna try to balance the joy of memeing with like, some reasonable level of also listening to people who have concrete, serious reasons for being glad she's dead. I hope everyone living in countries fucked over under her rule have at least 10x the joy I'm having as a random white Canadian who just kinda abstractly loves this
@SuricrasiaOnline your iceberg lead me indirectly to https://en.m.wikipedia.org/wiki/Bitsquatting
(false)
you've heard of /var/mail, but have you heard of /var/cash? fun fact: every unix account is also a credit account, you can see your "balance" in /var/cash. nowadays this doesn't mean anything, but back in the day it was used for billing people on big time-sharing servers. in order to discourage people from using too much memory, there would be an additional charge if a process owned by your account causes the system to run out of memory, commonly known as "OOM Fees"
grumpy linux question
i use debian with networkmanager on my laptop, and accidentally bump my rfkill button pretty often, taking out my wifi connection. i'd like to disable rfkill completely, and i can find no documentation on how to do so. i can't blacklist the rfkill kernel module because the bluetooth module uses it. it appears that userspace processes (wpa_supplicant and bluetoothd) take over management of rfkill (they have /dev/rfkill open), but they don't seem to have config options to disable it. i think there's some build options i can disable? am i seriously gonna have to compile my own kernel just to disable rfkill?
alice