Indeed. I was just replying to a Satoshi quote with another Satoshi quote 😃
#nostr is good for bitcoin because it makes bitcoin taproot Turing Complete
Decentralization just gives users more possibilities. They wont come for the decentralization, they'll come for the apps and functionality
A lot of people automatically dismiss e-currency as a lost cause because of all the companies that failed since the 1990's. I hope it's obvious it was only the centrally controlled nature of those systems that doomed them. I think this is the first time we're trying a decentralized, non-trust-based system.
Keep stacking and stay humble :)
early work in progress, does pubkey but not yet npub, could be easily modded tho
Worked! #bangers
Seems sensible at first glance
pip install nostr-relay && nostr-relay serve
#nostr makes taproot Turing Complete
Right now we have bots on nostr, but most are fairly simple
The GPT bot is a good example of a smarter bot, because it has an API to AI, leading to richer interactions
Smart bots could have advanced logic that includes payments. So a bot could have a "battery" that when it gets low, needs to be topped up. It could perform all sorts of algorithms, some in understandable contracts. Some with on chain commitments to make it tamper proof
Whole new services and business models can spring up to enhance the nostr ecosystem in a permissionless way
- Scaling nostr
- Smart Bots with Smart Contracts
Fundamentally what JSON-LD gives you is a standardized way of expressing hyperlinks (absolute and relative) inside of JSON
If not using JSON-LD, how to tell whether or not something is a hyperlink/URI?
Corollary: DIDs can interoperate perfectly well with nostr URIs by adding them to the JSON, and vice versa
This is good
Let me just say that I was a JSON-LD evangelist for a long time. It would have been nice if it could have got to a critical mass. But there are some technical reasons why you might not want to use it
However I have come to recognize that some developers will want to use JSON. Instead of fighting it, we should just embrace it
I think this is a good way, and what has been described as the "big tent" approach
There is some devil in the details, tho. For example how do you express a date? And how is that canonicalized. Perhaps these things are being worked through.
More about the JSON-LD context
They did make this optional in the DID spec, but Manu says that he regretted it
There was a long talk about making it optional in the verifiable claims data model, but unresolved
https://github.com/w3c/vc-data-model/issues/947
FWIW: I think Gabe and Daniel are fighting the good fight there, but maybe without success
The context links to many other http files which are not sha256 protected from editing
Not wringing my hands a all. I spent a lot of time on DID so I hope it is successful. And I think it will work well enough
I'm just saying that nostr need not adopt DID because it can do just as well, if not better in terms of decentralization
In HTTP the live version is definitive. The kludge to get around that is that the context is hard coded in the spec and the sha256 is inserted
But if the data changed you'd have a mismatch, the kludge would pick the tie-breaker
The context also contains many links to other http resources. More vocabs and contexts. These provide things like data types (how do you know something is a date?) or to labels in different languages, plus inferencing
Those other schemas are not protected by the hashing kludge
I'm not saying it's bad. Just how it was designed. The system will work well enough
I am saying that nostr avoids all of this
Very impressive! You can increase your puzzle rating by doing themed mate in 1,2,3,4
Verifiable is dependent on DNS
It's completely dependent on DNS. That's by design, as linked data is the semantic (http) web. There are some primitives that are not, but they are in the minority. If w3.org goes down (and they almost went bankrupt last month) all the definitive stuff breaks
re DIDs: very good exercise if you want to get under the skin
1. Write out a DID (JSON)
2. Write out the canonical form (nquads), if you can
3. Do the same for nostr
You might be surprised at what you see!