Interesting. But I think #NIP98 has just been made obsolete by the #IETF publication of HTTP Message Signatures .
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.
Protocol Action: 'HTTP Message Signatures' to Proposed Standard (draft-ietf-httpbis-message-signatures-19.txt) from The IESG on 2023-08-16 (ietf-http-wg@w3.org from July to September 2023)
X (formerly Twitter)
The 🐠 BblFish (@bblfish) on X
Today I presented the @ietf's upcoming HTTPSig protocol (@http_wg) at the @w3c Solid Community Group meeting.
I illustrated it by running my #scala...
