DrAwesome

They're (jokingly) saying they believe the moon is flat. Like a flat earther, but the moon instead of the earth.

This is one of the big things I miss from my Pixel 5a; it was so nice to be able to unlock the phone and pull down the notifications bar with one hand. There's a lot I like about the Pixel 8 Pro I replaced it with, but that's one thing I miss.

Interesting! I got no citation/link until I clicked the "Double-Check Response" button, it just replied "The young whale that hung out in Pillar Point Harbor was named Teresa T."

One of the drafts had a little more: "Teresa T is the name of the young humpback whale that was spotted in Pillar Point Harbor. She made headlines in September 2024 when she was seen swimming near the shore, drawing crowds and causing excitement among local residents."

I want to echo the recommendation of Andrej Kaparthy's YouTube channel.

Before I started watching his videos, I thought that understanding how gradient descent actually worked and what autograd actually does under the hood was unimportant - after all, I can get a working network by just slapping together some layers and letting my ML framework of choice handle the rest (and, to the credit of modern frameworks, you can get impressively far with that assumption). Andrej's Micrograd video was what changed my mind - understanding the basics of how gradients are calculated and how they flow has made everything make so much more sense.

If the classes at my university had been as good as what that man publishes on his YouTube channel for free, I would've actually finished my degree instead of dropping out.

Merry Christmas!

I played around with Plane locally a little bit about a month ago - I think it's really promising! I wish the documentation was a little better, though; I had to dig around through the source code to figure out how to get the OpenAI/GPT-powered features to work locally. I also wish it supported the gpt-3.5-turbo model instead of relying on the InstructGPT models (like text-davinci-003) for those features (while this isn't exactly a "chat" use-case, I think the chat model would still do a good job, and the 1/10 token cost would be nice).

I'm planning to set up a Plane instance for my friend group as soon as it supports OpenID Connect (SAML would work as well, but I imagine OIDC is coming first, since it's a lot more sane). We have some small projects we maintain, and we desperately need a nice issue tracking tool like this.

Unless I'm misunderstanding, this isn't bricking the device. The driver is refusing to allow it to work, sure, but it doesn't damage the chip itself in any way. The reason the FTDI incident back in 2014 blew up was because the FTDI driver didn't just refuse to work - it reprogrammed the USB PID on counterfeit/cloned chips to 0, which actually prevented them from working on any host (looking back at articles from that time, it looks like you could fix it by downloading the FT32 config tool from FTDI, but the important point is that the driver was effectively damaging the chips).

I really don't see the issue with drivers developed by a hardware company to support their hardware refusing to work with other hardware. I recognize that it creates problems for innocent end users when they do it, but Prolific just doesn't have any obligations to the end-users of other manufacturers' chips. Refusing to operate (rather than reprogramming the chips like FTDI's solution did) seems like a completely reasonable path to me.

While I think this article is unnecessarily critical of the Azure OMI agent, this is a very "What the heck, Microsoft!?" moment for me. Of all the pieces of Azure infrastructure, the OMI agent is absolutely something I expect to be well-tested and secure.

I recognize that bugs happen, but allowing a remote client to execute commands as root by simply removing the authorization header should have been caught by automated testing.

I actually just discovered this tool a few days ago when I wanted to do something with the Gitlab API from a bash script. It's really cool!

I don't have a Chromecast set up, so I'm not 100% sure on this, but my understanding is that Chromium users could cast using the Google Cast extension, and that Google did something (intentionally or unintentionally) to break the Cast extension and didn't fix it because casting is built into directly into Chrome now.