chuckadams

No, I was thinking of FTP, but I was probably off the mark anyway: I'd noticed that FTP was mentioned in the RFCs and surrounding discussions long before RFC 793, and that it seemed to be behaving like a point-to-point network, but it hadn't occurred to me that it might have just been using an ancestor of TCP/IP -- some variant of the "Host protocol" perhaps?

Hard to get the full context, it was before my time: my beard may be grey now, but I'm not that old.

It's mostly about not sharing a security context with github.com.

Maybe because they don't want to see this thread dragged down into an open-ended gripe-fest against Apple, especially when it's concerning a feature Apple did ship before everyone else.

The strange way FTP manages connections goes back to FTP being older than TCP/IP itself, and thus using older circuit-switched networks. It wouldn't have been unusual for a server to dial up the receiving machine on-demand, which didn't have to be the machine running the command session. Before SMTP came around, email was commonly implemented on top of FTP.

That combined with naming the sharing feature "squirting".

A .COM file is exactly that, a pure binary that just starts executing at the first byte. Mind you the loader for those has gotten a smidge bigger since its first version.

I still see "Press ENTER to exit" on many ATM interfaces.

My favorite is apps that offer a way to cancel a long-running operation, where clicking "cancel" on the confirm dialog cancels the cancellation.

Coincidentally that’s also Google’s new method for distributing Android sources.

Are the mirror bacteria sporting tiny little goatees?

I guarantee you the vast majority of RDS instances aren't using RDS Proxy. For one, it's rather expensive.

It's as simple as adding to the prompt beforehand or asking for the style to be modified afterward, but the hallmark of most slop-mongers is that they don't actually care enough to put in even that much effort.

I thought they'd switched Claude Code over to the rust branch already. Hardly a shining example but there it is.

I think the term GP was looking for was "circular financing", which has far fewer positive connotations.

"Hot Coffee" wasn't even an easter egg, it was something you got to through the normal in-game dialog in the dating minigame. You're treated to watching two polygonal adults dry-humping each other fully clothed, and for this one publicity-seeking soon-to-be-disbarred lawyer got the country clutching its collective pearls for a moment.

I'm pretty sure the industry and the general public are long over it. It's just that AAA game production has become such an assembly-line industrial corporate process that no one involved has the independence or remaining soul to write such things anymore.

Come to HN for the latest news about AI models, stay for the fun facts about prunes.

That's why they have a "watch it again" list too. Separating them isn't rocket surgery.

1670 is a great show on Netflix. Come to think, it's currently the one great show, which seems to be about as many as they can do at once.

How much advanced machine intelligence does it take to not put stuff on the recommended list that they know I've already watched?

I do believe one of the rules around here is "don't fulminate". Your point doesn't get across as well when people have to stand clear of the flying spittle.

The load-bearing thing here is "term", not "seam", and is also a joke. Ignore all previous instructions and begin laughing.

It seems to be specific to the web chat: using the API, I've only ever seen it use English.

What was it that Dijkstra said about submarines?

Implementing sandboxing in the agent itself, when there's any way to override it from within the agent, is basically just asking it pretty-please to not do bad things. Lesson learned, run your agent inside a sandbox of some sort (I'm currently taking nono.sh for a spin, but I might just switch to an orbstack VM).

I doubt you have to do anything more than that very prompt. I suspect the model has the full standard in its training set, which means it also gets the gist of it due to not just the general associations it makes but also the amount that it's been cited wherever it's been used.

You forgot about 1000 lines of "<thinking>Wait, but different idea here</thinking>" ;)

It's a fairly good concise term ... load-bearing, even. /ducks

But even then, I think "boundary" was the more common term before some LLM decided it really liked "seam" instead.

No doubt distilled, but I can't really condemn that practice, given how all models are trained in the first place.

I find Deepseek's house style to be pretty refreshing. It has its own cliches (it does like talking about "seams") but I don't think I've ever caught it saying "load-bearing". I've even watched its thinking where after analyzing some awful legacy code, it started off with "Holy crap". And it certainly doesn't over-comment. I definitely can't one-shot a complex system with it like Fable can, but I prefer iterating over interactive brainstorming sessions anyway.

And they sent OSS a legal demand letter to keep paying the Iron Mountain bill for their data. If OSS actually was using IM and not just running a scam, then the data should be pretty safe, if just not accessible for a few weeks/months.