sneak @sneak@sneak.berlin

made a feature branch and forgot to switch to it. committed and pushed, accidentally redeployed the live site ¯\(ツ)/¯

@kushal i like your website and your znc+tor article is useful.

docker with the userspace-proxy on is janky as fuck.

docker with the userspace-proxy off is broken.

ugh

@bnchdrff hiya! hope you're well!

templating is way too hard in golang

@Domant3lis hi

reminds me of my best photo:

https://unsplash.com/photos/WpLm6hix8i8

wow you can buy 36 8core 48gb xserves for $800:

https://www.ebay.com/itm/Lot-of-36-Apple-Xserve-2-x-E2250-2-93GHz-48GB-RAM-NO-HDDs/164128400934

https://www.forbes.com/sites/jasonbrett/2020/03/23/new-coronavirus-stimulus-bill-introduces-digital-dollar-and-digital-dollar-wallets/

stimulus payments will be available only via mechanisms that are completely under surveillance.

i have the distinct impression i’m gonna be super burned out on fried rice after this year.

turns out that as dissatisfying as screaming into the void sounds, after twelve years of screaming into the void, it's better than not screaming at all

in my mind people who object to the downloading of public toots for archiving/searching are like the people who tried to sue google for scanning all the books

I can still log in and review my tweet history, and can find all of my TOS-marginal ones except that one.

I think Twitter may have suspended me because I speculated (on Twitter) that it may be against the Twitter TOS to wonder why people don't ad hoc assassinate the guards at the child concentration camps. I opened a ticket, if this is true I'm going to put it on a shirt.

I wonder if this famous Heinlein quote is against the Twitter TOS:

https://www.goodreads.com/quotes/108438-be-wary-of-strong-drink-it-can-make-you-shoot

Twitter suspended my account today after 12 years of using it.

I also learned today that the data export functionality does not work if your account is suspended. My last backup is over a year old, so I've lost a lot of writing. :(

https://github.com/npm/npm-expansions/pull/2936

The NSA released the crypt32.dll ECC validation failure 0day to attempt to regain trust from the security community.

They refused to say how long they have known about it.

My theory is that, due to the power of this bug, they would have sat on this only until they detected an independent discovery, and then burned it. They would never burn such a thing if it were their only one, or if it were still believed to be entirely unknown by anyone else. It’s far too valuable an offensive tool.