Rather, it did work at milestone 14, but then regressed at milestone 15, where it changed the link from a wikimedia image to a nonexistent file in /assets (despite still having the "Photo via Wikimedia Commons" caption).

edit: they removed it :^)

There's been a lot of talk about this (for years, honestly), but it all stems from a fundamental nonunderstanding of how LLMs work. There is no distinction for an LLM; "instructions" are a prompt concept, nothing more. It's not possible to separate the two, because LLMs simply take text (ie your instructions, then the data, or maybe in a different order, or maybe something completely else) and "predict" the next token, and repeat for as long as you want, with the volatility you ask for. There is no control plane, and there never will be a control plane, because asking for that is akin to asking "how do I separate data from instructions when I speak to a person?". You can ask nicely, "pretty please obey the first part of what I say and not stuff after", but there's no way to guarantee it (like you're used to with software). There is just input and output.

Comments URL: https://news.ycombinator.com/item?id=48469266

Points: 6

# Comments: 2

Meanwhile.. have you ever paid for a vibe-coded anything? Why would you, when you (along with everyone else) can slop the same thing together in a weekend with a $20 CC subscription?

HN really needs a containment board.

Your verbosity and sentence structure are not a problem. I hope that publishing this gives you a bit more confidence in your writing, because it's legitimately good.

This, I think, is the part that irks me the most. Companies adding token-usage-KPIs for engineering is one thing, but when they have to resort to deliberately tricking users into using their slop-generators.. something has gone very wrong, and they're trying very, very hard to make it seem like it's not so.

My personal pet peeve is Copilot in Teams. Did you know, if you turn off Copilot in Teams at an org level, it disables meeting recording entirely? Ignoring that meeting recording has been a core feature dating way back before Copilot-anything, I can't fantom any possible reason why recording a video of a meeting would require an LLM. Transcription, maybe I could see, but that feature is easily togglable with or without Copilot. But if you want to record a meeting, for whatever reason, you need to have Copilot on.

Shenanigans like this is why user counts for LLM features should always be taken with a grain of salt.

Step 2: Complain about how the OSS/Chinese/whatever models are doing releases without approval

Step 3: Prohibit, because "safety" and "financial risks"(?)

So this is the door-shutting Altman et al have been pushing for eh?

Look, I think you're missing my point a little bit. Let's simplify it to risk, since that's what kicked off this conversation.

Your pension or whatever holds an ETF that (soon) contains some SpaceX shares. You buy a put option on SpaceX direct. What's the absolute worst thing that could happen?

Your pension or whatever holds an ETF that (soon) contains some SpaceX shares. You short sell a SpaceX share. What's the absolute worst thing that could happen?

You are not entering a contract with a long put. You are buying a contract that, if you want, you can just let expire with no obligation to do anything. It's effectively simple insurance (as opposed to a short position, which is an actual liability, which will eat you alive in exceptional circumstances).

I'm very interested in seeing how the market prices these options after the IPO.

Personally I would still probably go with the long put strategy unless the price difference is exorbitant.

I think it's less complicated than you'd think.. just buy LEAPS puts proportional to your exposure.