NFT was the peak.

Interesting, although to me it looks more like a way to split one file into several (which is rather useful).

> extends

What's the difference with anchors? Looks the same, except works with include (and doesn't work with any other yaml tool).

> dynamic pipeline generation

Which is even harder to reason about compared to anchors, although certainly powerful.

In GitLab, where YAML anchors have been supported for years, I personally find them very useful —it's the only way of "code" reuse, really. In GitLab there's a special edtor just for .gitlab-ci.yml, which shows the original view and the combined read-only view (with all anchors expanded).

I agree that it's hard to point to the specific line of the source code, but it's enough — in case of an error — to output an action name, action property name, and actual property value that caused an error. Based on these three things, a developer can easily find the correct line.

Tried to find it but docs point to GitHub, GitHub points to docs and none seem to point to MCPs listing.

Which is already covered by existing laws. Same as other categories given by dangus.

There's an implication here that users would pick a random hand. I'm sure a set containing all flushes, straights, full houses and four of a kind would account for most of the used passwords.

If response contains prompt text verbatim (or it is below some distance metric) replace the response text.

Not saying it's trivial to implement (and probably it is hard to do in a pure LLM way), but I don't think it's too hard.

More like it's not really a big secret.

At this point you'll need to at least check how much running ffmpeg costs. Probably less than $0.01 per hour of audio (approximate savings) but still.

LOTR has fairly pronounced anti-industrial themes.

Sure, gpt-4o has a context window of 128k, but it loses a lot from the beginning/middle.

SponsorBlock for YouTube resolves the issue.

Agreed, the takeover would be peaceful and even celebrated.