Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 9
Generated: 00:36:50
Good news! After a helpful discussion with the W3C Credentials Community Group, we’ve aligned on a verification method that works cleanly with did:nostr and the Verifiable Credentials stack: w3c-ccg/community#254 (comment) I’ve already patched the did:nostr draft to reflect this. What this unlocks 1. Production-ready reference implementations 2. Compatibility with the wider W3C Credentials ecosystem 3. A straightforward path to issuing industry-standard credentials (badges, awards, driver’s licences, etc.) over Nostr 4. The ability to sign and exchange JSON payloads between Nostr services (relays optional) It’s a nice step up in standards alignment and Nostr functionality. Many thanks to everyone who weighed in, feedback very welcome! image
2025-08-09 21:07:29 from 1 relay(s) 9 replies ↓
Login to reply

Replies (9)

nostr:nprofile1qqsqddupn4l3cl65wggcyehd009g0pwuatsfudh28f90vewx68vrylqprfmhxue69uhhyetvv9ujuem9w3skccne9e3k7mf0wccszenhwden5te0ve5kcar9wghxummnw3ezuamfdejj7mnsw43rzufkd43hywr5d3erxmp5va6hxvmnveh8wd3hxue8xdm6v9jnv6r3de3k6ae4wa4rydm9df6kgdthvduxvdm3xph8sdmyx5lkyun0v9jxxctnws7hgun4v5q3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7nznd8h 👀
2025-08-09 21:13:59 from 1 relay(s) ↑ Parent Reply
I'm not sure I'm a fan of using hex pubkeys instead of encoded "npub" pubkeys as user IDs. The reason is that the DID contains "nostr:" and "nostr:npub…" is a valid Nostr URI. Wouldn't it be neat if the DID URI were "did:[valid Nostr URI]"?
2025-08-09 22:47:55 from 1 relay(s) ↑ Parent Reply
Greetings! I'm guiding 10 people on how to invest in stocks, turning an investment of $160 into $6,200 in just 2 hours. If you’re curious, feel free to DM me with 'want to know how'. Don’t let this opportunity slip away; message me for more info! TEXT SMS: +1 (703) 879-8125 WhatsApp: +1 (873) 300-3966 Check the WhatsApp link below 👇👇👇👇 https://wa.me/message/M2YPIT5J6LL3A1
2025-08-10 00:15:51 from 1 relay(s) ↑ Parent Reply