inlined

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.

I think they’re talking about Apple fans, not laptop fans

Tbf, accepting a pardon is legally admitting guilt per SCOTUS and disgorgement would allow the funds to be sized

If the weak link is GPS, could they not accept an override for the time and spherical coordinates to connect?

No. Absolutely not. The opposite in fact. Your bash script is deterministic. You can send it to 20 AIs or have someone fluent read it. Then you can be confident it’s safe.

An LLM will run the probabilistically likely command each time. This is like using Excel’s ridiculous feature to have a cell be populated by copilot rather than having the AI generate a deterministic formula.

There was a coffee shop ages ago in SF that would every few hours play a cacophony (e.g. multiple songs at once). I assume it was to drive away people camping on their laptops to rotate tables. Understand but super annoying to people like me who had a timer to but food or drink no less than hourly to be a good citizen

Google had achieved carbon neutrality and committed to wiping out their carbon legacy until AI.

As a user I suffer from not being able to freely use or derive my own work from Microsoft’s

Nice. I didn’t know I can now replace my “assertExhaustive” function.

Previously you could define a function that accepted never and throws. It tells the compiler that you expect the code path to be exhaustive and fixes any return value expected errors. If the type is changed so that it’s no longer exhaustive it will fail to compile and (still better than satisfies) if an invalid value is passed at runtime it will throw.

Is this meant to be a defense of the DNS protocol? I’ve never assumed the meme was that the DNS protocol is flawed, but that these changes are particularly sensitive/dangerous.

At Google we noticed the main cause of outages are config changes. Does that mean external config is dangerous? Of course not! But it does remind you to be vigilant

Mongo also has a good query language and a mongo DB can be seen as an array of documents

It sounds like you’re not at the scale where cloud storage is obviously useful. By the time you definitely need S3/GCS you have problems making sure files are accessible everywhere. “Grep” is a ludicrous proposition against large blob stores

Maybe they’re not using keepalives in their clients causing thousands of handshakes per second?

Doubt that’s on the table unless Microsoft is also sued. Without a joint ruling this wouldn’t be balanced

You actually should never return a specific error pointer because you can eventually break nil checks. I caused a production outage because interfaces are tuples of type and pointer and the literal nil turns to [nil, nil] when getting passed to a comparator whereas your struct return value will be [nil, *Type]

Go seems really sensitive to this subject. Maps iterate in order, but one day they said “this is incidental and we said not to rely on it. You do, so we’re breaking it in a minor release” and now maps iterate in order… from a random offset

(I work on Firebase App Hosting, which also supports Next.js directly rather than OpenNext)

I want to +1 that Vercel has been really improving their portability. We still have Next.js specific code in Firebase, and having different architectures can sometimes make us have to figure out the best mapping of their features, but Vercel has made a noted effort to improve encapsulation of Vercel-specific features and portability has improved. I’m honestly surprised that OpenNext, which is not a new project, seems to have gained a lot of attention in the immediate past.