So I found myself playing with -- and learning about -- the save-vs-unsafe ways you can decouple PostgreSQL transaction commits from fsync() on disk.

PostgreSQL gives you a lot of options, some of which are dangerous, and some of which aren't. It's interesting how much you can tune.

Show thread

Recently someone signed up to and proceeded to try and block basically all of Twitter. My poor little server fell over and died twice as they blocked over 2.5 million Twitter accounts.

Interestingly, the constraint isn't CPU or even the Twitter API. It's the IOPS of an EBS storage volume being used for PostgreSQL commits.

Oh man, a CSS stylesheet that looks exactly like LaTeX. This is the closest I've come in years to wanting to throw away my blog and replace it with static-site generation (again).

graphic details of illness, body horror 

on my third day of severe diarrhea, moderate dehydration, frequent nosebleeds, and simultaneous kidney stone pain.

How's your week going?

that doesn't mean I haven't been *doing* stuff, it just means I've been doing it in the typcal haphazard cloud of anxiety and executive disfunction. working off of lists is a whole lot nicer to my brain.

Show thread

Actually resurrected my TODO lists and had a productive day sorting some shit out.

(note the last day I actually knocked stuff off the list, I was unemployed)

Right now, I'm in the process of deleting my entire "like" history on Twitter.

Twitter has gone to interesting lengths to make this onerous.

Older tweets can ONLY have their likes removed if you "like" them again *first*. That means a new notification is sent, for a years-old tweet.

I can remove "likes" I can't "like". Can't remove them for accounts that have been suspended or subsequently blocked me.

So when I'm done, the only "likes" left will be for tweets of people who loath me.


Cloud Island

A paid, early access, strongly moderated Mastodon instance hosted entirely in New Zealand.