inlined

Reminds me of the time when my roommate wasn’t let into a bar soon after college because he had seriously bulked up since high school. We spent a half hour arguing, showing that all his credit cards are under his name and that even his work badge had his name and a recent photo. This feels politically relevant now too

Adobe’s ereaders had a disclaimer that their books cannot be read aloud. There’s clearly precedent that this sort of transformation was disallowed by publishers at the time. Interestingly, at least the audiobook of the latest dungeon crawler Carl has a disclaimer that it can’t be used to train AI

To be fair Nick Fuentes praised him on his perfect Nazi salute

In good faith, what is your burden of proof that would change your mind?

That seems absolutely crazy to do. One could argue that the marginal cost to work for using a work laptop is zero and the work is still yours (still beyond the risk I’m willing to take). Using a company’s AI account is literally using the company’s resources for a personal project. There is no plausible case where they don’t own it.

But Apple has always made their image quality not cost effectiveness. Pivoting here too drastically could sacrifice their image and backfire

But given the hoopla about how a driver’s license isn’t valid in the SAVE act because it doesn’t prove you’re a US citizen, how is drivers license verification going to satisfy the US national requirement here?

I know agents are out of scope of this RFC but I love that this could easily be extended to make the JS EventSource to work on streaming AI queries.

Due to the need of bodies in requests, everyone uses POST and streaming results often use the text/event-stream protocol for responses. But this is technically a bad fit because no state is actually changing and because EventSource can only use GET for some obstinate reason. So many APIs reimplement the functionality with their own parser

I think it can at least be said they are amoral not immoral. It’s a very low bar, but still

In honor of The Old New Thing I call these “Vogon vulnerabilities”: I have a marvelous exploit in mind that pwns anyone I have root access to

But it should be their job to protect against MitM in their threat model. There is no rational reason to exclude them from the bug bounty. Doing so only leaves MitM attacks like this undisclosed.

I’m not diagnosed face blind but I’m hoooooorble with names. It’s weird because I’ve been tested and score in the 98th percentile for memory generally.

I hung out with a large group of people for nearly a decade and couldn’t remember who was who until the pandemic. The names under zoom helped me gradually learn over weeks.

When I teach scuba I recite the list of student names for my class in as random an order as possible while I drive to the shop to lower my cognitive load to put faces to names. When I do roll call, I write down every person’s name and try to gradually move off the cheat sheet as I call on them to answer questions. But once they put on their gear (especially since I teach where they use hoods) it all goes downhill. Two white guys approximately 35yo? I’ll get them confused.

If this were socially appropriate I’d totally use it as my prescription glasses to help continue smoothing the curve.

So geo-gate it?

What are you withholding from the sandbox without making it useless?

That used to be my thing: wherever our ops manager declared something was impossible, I’d put my mind to proving her wrong. Even though we both knew she might declare something impossible prematurely to motivate me.

My favorite was “it’s impossible to know which DB is failing from a stack trace”. I created STAIN (stack traces and instance names): a ruby library that would wrap an object in a viral proxy (all returns from all methods are themselves proxies) that would intercept all exceptions and annotate the call stack with the “stain”ed tag.