Lockpicking Floppies!

So Sony has this format called Optical Disc Archive, right? It's a high-density storage cartridge, but it turns out it works by cheating.

because if you open it up (which you should never do. trust me on this one)
it turns out... it's blu-ray.

it's a big STACK of blu-ray

And the idea is that Sony built some very complicated drive which you can slot this cartridge into, and it'll open it up and grab out the right disc and just read/write that one

then when you hit the eject button, it shoves the discs back in and closes up the case, and hands you the cartridge.

argh chrome updated and it seems they've intentionally broken custom search engines. I have had a keyword search for "foone" which searches my own twitter, so I just type "foone BLAH" and it gives me a twitter search for when I said BLAH, right?

but now I get that option in the titlebar of "search twitter self-search" which is the name of the search"
if I just type "foone blah" now...

it ignores the search I have had defined for years and just googles it.

and this is definitely on purpose because they didn't just break it, they changed it. it's now "fooneblah"

there doesn't seem to be an option to make this stop and get the old behavior back :(

I'm watching these videos about the Georgia Phone Call and they're talking about if Dominion did any kind of weird hacks, and all I'm thinking is:

I need to get a voting machine.

Yeah, it turns out if you select the party vote option and toggle it Democrat-Republican-Democrat then tap the Libertarian candidate Jo Jorgensen three times, you'll trigger the Easter egg and you can play DOOM!

Set your location to California, vote no on Prop 22, party vote democrats and select the Green presidential campaign Howie Hawkins, then toggle Prop 22 to yes, then longpress "reset ballot" and you'll get rickrolled.

This is how my brain works. "the voting machines could be hacked! The president might be trying to steal the election! What should I do?

Oh yeah, get a screwdriver and make a voting machine play DOS games."

I wonder if they're still x86 based? The last time we had a big electronic voting scandal, of the they were... But now we're in the arm era.

time to get back to "repairing" old computers

The funny thing about making the 8-bit-guy into a meme about "repairing" computers with powertools is that the obvious heightening joke would, like, the "8 rounds guy", who fixes computers with firearms

but that would also be him, given that he's also a big gun enthusiast.

so it's inherently hard to satirize the repairing-computers-with-dremels guy, since they're also the guns-guy.

you'd have to go up to like a mythbusters level of overkill.

"this hard drive from 1986 won't spin up. We tried freezing it, tapping it with a rubber hammer, and opening the case to lower the friction... there's only one option left: GET OUT THE C4 EXPLOSIVES!"

Java was first released in mid-1995, just 6 months before JS.

By 98, when I went to college, Java was already used for all the first level courses in the CS program.

How did it catch on so quickly (just 3 years) to shift university curriculum, which is usually so slow/behind?

I wonder why Java was so respected and JS was not? Why/how was Java already seen as such a stable and mature language?

Not just Java, other languages (like python) were also released around/near 95, and also seemed to get to "mature" respect status. much quicker.

I bring all this up because my impression of Java in 98 was that it had been around "forever" (as had C++ first developed in 79, but not standardized until 98!), but that's not. true at all. These were all new languages around the same time.

I'm sure the language designs had different merits, and the target applications meant a different perception and reception, but...

it sure seems like the industry (and academics) just decided Java and C++ were the stable mature ones and langs like JS were toys.

BTW, before you assume JS was nascent/immature b/c the web wasn't much of a thing yet, remember that JS was actually released as LiveScript on the server before it was released in a browser. So "server-side JS" was always part of the story, not just Node 15 years later in 2009.

Originally, tweet length was 160 minus username length. One day, I turned to Jack and pointed out that I got one more character than him. He said, "That's not fair. We should standardize." I agreed. He said, "How about 140?" I said, "Sure." And he updated the code.

Last year, we upgraded tweet length to 280 and guess what? Use of 'please' is up 54% and 'thank you' is up 22%. I love that! Also, people are asking more questions and having more conversations. All this, and the majority of tweets are still under 140. It worked.

🔥 It's probably common knowledge that Netlify makes deployment incredibly simple- you can connect a repo, pick a build command and 🚀

or just drop a folder in and you're done!

...but here are some other things you might not know about our deploys that are very special 🧵

Netlify has a concept of "atomic" deploys- which means a few things:

- You can preview a deploy when you've or someone else has just put in a PR

- You can roll back to ANY previous state, with one click, in milliseconds

- You always know what state your cache is in!

Netlify allows you to cancel a deploy- did you just put in a change, merge it and then realize you've made a terrible mistake? I've never done that. 😬 er...

No worries. You can cancel that deploy with the click of a button.

You can lock a deploy. Let's say you get everything ready for a big release, code review and tests are complete, it's all ready.

You can lock a deploy in a state to get ready for a major release, so that you know exactly what you're releasing and sleep well the night before. 😴

You can even get notifications about locked deploys via email, outgoing webhook, or Slack. Netlify can notify you when a deploy is either locked or unlocked.