incomplete

omg, thank you SO much for the rec on clickspring's antikythera mechanism! i watched the first two episodes years ago and the algorithm never brought the channel back to my feed. now i'm subscribed and will have to watch this again.

i was also lucky enough to visit athens years ago and see the mechanism in person at the national archaeological museum... it's an amazing exhibit, and if you're ever in that neck of the woods i cannot recommend it any more. :)

same, i knew it was written w/some ai assistance, but it was definitely massaged well enough to keep me from closing the tab in disgust.

i mean.... yikes.

they'll just need to change the jingle to be something like:

one eight hundred cars for kids, for east coast kids to fly to israel on your dime!

also, praise be <diety> that these jingles will soon be off the air.

it's not super clear, but that's my read as well... i think i can start lowering my panic levels now.

i work tech at a university that's impacted by this. while it doesn't impact me directly, many many other staff and instructors i know are heavily affected by this outage. the students are absolutely outraged, mostly because the university hasn't been providing updates as quickly as they'd like, but since the staff/admin are waiting on word from instructure -- and there hasn't been a lot from them, it just generally sucks for all of us.

this is really, really, REALLY bad. it's not great that names/emails/etc will potentially be leaked, but also private messages between students and instructors. and since many of the campus systems rely on canvas integration, things have pretty much ground to a halt a week before finals.

after they were breached on the 1st of this month, instructure had an announcement yesterday that "everything is great! we're good! hackers are gone! we've rotated our keys!".

no. nothing is great. we are not good.

i did the circleci --> github actions migration for my job 1.5 years ago, and things seemed great... at first. at the time, we'd been dealing w/circleci's semi-regular (but thankfully short) outages for over two years, and we were excited to move to a more stable system.

now i'm considering deploying jenkins.

my first rule of HN is to check the comments first, article second.

after seeing these comments, i just had to see for myself... and i couldn't even make it through the first section of the article.

> On HN we should try to get primary sources for this sort of thing.

+10000

came here to post that community github status page, thanks for beating me to it!

feels like it's a race to the bottom here, and gitlab is starting to look even more appealing as the 9s disappear from github's uptime numbers.