I'm saying that the only thing the user owns, is the data and application/relay settings stored in events. If they keep it in events, then they can move from relay to app, and have the same setup, everywhere. So, you would choose your relay based upon service, including whether they honor what is in your events.
For instance, nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h allows me to use my npub's lists (mute, follows, favorites, etc.) to determine who is allowed to use my private relay. I edit those lists and click a button in relay.tools and it updates the blocks/allows.
That means I could have 15 different relays, from different providers and/or self-hosted, and they'd all have the same settings, if I choose. Or I could have a set of lists by topic and have a book club relay, a Christian chat relays, a dev relay, etc.
Filter.wine does something similar with WoT. It is controlled by the changes to your follow list.
I house the relay and app settings within my events.
Think about it this way:
There used to be one or two ovens per village, either at the bakers or in the town square. It took hours to heat up, by packing it full of precious wood, so everyone would get their bread from there, as building an oven and burning all that wood, just for one loaf of bread, would have been crazy. There were usually only a couple of kinds of bread being baked, as the work around the oven was so laborous.
Then people eventually got wood-burning kitchen ovens, that doubled as a heater and a stove. Then they baked their own bread, since the time and cost became negligable. But Most people Just baked the same bread over and over. At the most, they'd break it up into dinner rolls, or something.
And then everyone got electrical ovens and it got even easier and cheaper... and they all stopped baking. Now, almost everyone goes to the grocery store or the master bakery, where there is a wide, curated selection of bread, and choose from that selection.
In the same way, AI app generation won't lead to everyone creating their own apps. It'll lead to people becoming app-generation specialists and they'll offer an array of apps to choose from and further customize, hosting options, services, etc. Or they will concentrate on the data and storage layer, where the value is.
The dev talent will have to go one level deeper, in multliple directions, same way that baking had to become a factory good or an art form.
That is the effect of commoditization: go upscale or downscale.
They're already getting crushed by the running costs necessary for AI, especially data storage, analysis, and energy. They're trying to get the processors cheaper, since that's the easiest pressure point, hence the recent NVIDIA crash.
Nostr distributes all of those costs. Since your server doesn't have to do all analysis for everyone, but only cater to your own use case and your own data set, and can run asynchronously -- results periodically updating a data file on the server or generating an event for your (private) relay-- it's relatively cheap and you can buy one of the older or less-powerful GPUs for $700-$1500, or just run it on your gaming PC.
We literally just listed the embedding spec in the NIP repo this week, and you've already lost patience. 😅 Like, give us at least a year, okay?
https://github.com/nostr-protocol/nips/blob/master/README.md
Showing page 1 of
2 pages
