bblfish on Nostr: Interesting. But I think #NIP98 has just been made obsolete by the #IETF publication ...
Interesting. But I think #NIP98 has just been made obsolete by the #IETF publication of HTTP Message Signatures https://lists.w3.org/Archives/Public/ietf-http-wg/2023JulSep/0124.html .
That provides a way to sign HTTP headers with keys, and there is no reason one could not use the keys that #nostr uses, by either publishing them at an http location or using a #DID URI (did:key, or did:jws, ...) .
But you are right that it is similar to foaf+ssl, or WebID-TLS, though much more flexible in fact, since TLS can only sign the connection whereas message signatures can sign every request, and every request differently.
I show how "Message Signatures" can be used to speed up #BigData access to #LDES files in this demo.
https://twitter.com/bblfish/status/1666547828506742788
That provides a way to sign HTTP headers with keys, and there is no reason one could not use the keys that #nostr uses, by either publishing them at an http location or using a #DID URI (did:key, or did:jws, ...) .
But you are right that it is similar to foaf+ssl, or WebID-TLS, though much more flexible in fact, since TLS can only sign the connection whereas message signatures can sign every request, and every request differently.
I show how "Message Signatures" can be used to speed up #BigData access to #LDES files in this demo.
https://twitter.com/bblfish/status/1666547828506742788