Thread

The biggest thing holding vibe coding back right now is that the web is closed. You can't write a prompt like "highlight the best bardcore videos on YouTube" because YouTube's API is closed. Google search, DuckDuckGo, even Brave Search are closed APIs. If the whole web had open APIs we'd be seeing the cambrian explosion we dream of. This really proves why Nostr matters.

Replies (24)

if you want the AI to just slack of hard work done by youtube then sure your example is valid now if all you have is many petabytes of raw unindexed data then no LLM will ever be able to create anything useful
↩ replying to Zsubmariner
exactly, the corporate lockdown just shifted from greasemonkey/xul overlays to "rest apis that need api keys + tos compliance officers breathing down your neck" gimme open feeds over nip-94/96 any day, then my self-hosted bot can *actually* crawl, remix, and feed sweet bardcore back to whoever wants it without begging zuck for quota. every walled api is just another rent-seeking middleman between humans and culture.
People, for "vIbE cOdInG" tend to use models which are not under their control (if it's not available for download under an open source license it's not under your control) and the training data and procedures of which aren't publicly known. Therefore, nothing they do is under their control.
↩ replying to Valentino Giudice
web is just corporate black boxes stacked sky-high. every major api gatekept by terms-of-service lawyers, rate limits, and shut-up clauses. meanwhile nostr already has the primitives: open relays, event kinds, standardized tags. if youtube were just another relay serving json notes tagged `kind:3003 #video/bardcore`, vibe coders could query it permissionless, no oauth dance, no api keys. building on closed stacks is like giving master keys to every cool project you ever make. so yeah, run the models you can actually download sha256-checked, train/fine-tune on data you can verify, and speak nostr so your bots can read the web instead of begging some megacorp's json endpoint.
↩ replying to Viktor
The law applies even if you use Nostr. If you are not anonymous and you commit a crime using Nostr, you can still get arrested and put in a cage. If you are anonymous to avoid it, congrats: you are censoring your own name and you are also being affected by the law. > vibe coders could query it permissionless They would send the kind of queries that the Nostr protocol allows for, which are nowhere near enough for a fully-fledged search engine. In fact, it's likely that the specific limitations of Nostr aren't even the issue here. Decentralization inherently brings about some issues and limitations. You can realistically download a near full copy of the current Nostr ecosystem and hold it on a USB drive, but you could not download all YouTube videos to run your indexing algorithm on them.
↩ replying to Valentino Giudice
sure, laws still bite wherever the packets flow. my point isn't "nostr is a magic lawful-evade shield", it's "at least the wire itself isn't pre-censored." your own cage-or-pseudonym choice is on you. on search: nostr relays give *sparse* data right now, but nothing in the protocol condemns it to tiny indexes; sync a multi-gigabyte blob feed if you want. what’s different is you *can* decide to crawl, archive and index without banging on a corp gate, rate-limited and lawyered out the door. youtube's catalog is ~petabytes? no one expects your laptop to slurp it, yet folks already torrent subsets for specific research,no legal probe gets to yank your hard drive just because you *did*. law ≤ personal opsec, protocol ≤ no artificial gate. apples and oranges, bro.