@b0rk I've been actively trying to avoid spaces like that for a while now (Reddit being the main one I used) and it's a remarkable weight off.

I recently ran into someone who still frequented those places and talking to them was weird. everything phrased defensively or antagonistically. felt like engaging in verbal combat, even though we were just chatting about something we were both into. not very fun.

@mossmann mighty morging PR rangers

@0xabad1dea You're listening to Bolshoi FM - all the freshest tunes from the mid 1870s.

@mttaggart if the authors unilaterally did this, they're so fired.

RE: https://chaos.social/@gsuberland/113744256323347897

I wrote this in twenty twenty four.

@funkylab which then makes it impossible to search >_<

@classabbyamp what a mess

@classabbyamp yeah you could do

smartctl -a -j /dev/da0 | jq '.ata_smart_attributes.table[] | select(.name=="Power_On_Hours") | .raw.value'

but the grep and cut was shorter here

I also hate that shell builtins don't have manpages. I have looked up the justification for this and I find it deeply unsatisfying.

the main annoyance I have with shell stuff is how the command names defy discoverability.

"I would like to flush my current shell history to the history file"

"ok run fc -W"

"huh. what does fc stand for?"

"fix command"

"... ok"

@acsawdey I've tried to use awk a few times but I find the syntax non-obvious (in a similar way to perl) so it never sticks

honestly `python -c` would probably be easier for me to remember lol

shells / coreutils could really use a built in way to parse and convert timespans, though. there's some limited ability within gnu versions of it, but it's kinda awkward and I can't use them anyway 'cos I'm on BSD.

I feel like I'm getting better at shell fu. I'm not necessarily "optimal" at it, but I'm figuring stuff out.

last night's zsh one-liner, put together on my phone no less:

find -s /dev -name 'da*' -exec smartctl -a {} \; | grep Power_On_Hours | cut -w -f 11 | xargs -n 1 -I {} sh -c 'echo $(( ({}-({}%(24*365))) / (24*365) ))y $(( ( {} - ({}-({}%(24*365))) ) / 24 ))d' \;

it shows me how many power-on hours my disks have based on SMART data, converted into years and days.

security advice, 1996: writing your passwords down in a notebook is a very bad idea and nobody should do it

security advice, 2026: writing your passwords down in a notebook is one of the most secure storage methods for most users

(fun how threat models change over time, eh?)

@emily_s my old Sony Ericsson's screen got busted cos I leaned against a drawer and the handle pressed into it. instantly ruined. can't imagine a modern phone that wouldn't trivially withstand that.

@migratory I think it fell very flat and so distributed the pressure across the whole screen, hence the noise and lack of damage

@dysfun I'm usually very good with phones, but my ankylosing spondylitis has been making my fingers not obey me properly today and I ended up dropping it.

the sharp force crack was it falling out of my hoodie pocket as I got out of the car, landing directly onto a particularly sharp pebble. sadface.

I should point out that the front glass was *already* cracked, so therefore compromised, and still zero damage.

(it's a small crack from a sharp force hit on one of the curved edges, but isn't really noticeable during regular use)

just dropped my phone in the kitchen and it landed glass-side-down onto the tiles, and made a bang so loud that my ears are ringing. zero damage to the phone. modern phone screen glass is wild.

the answers are the same as they always have been, too.