That's not a valid HTTPs URL though, is it? Since there's no specific location to hit. Maybe I'm missing something.
back
1 comments
Then i did not understand the article, I thought morel.us-east.host.bsky.network was the specific location after resolving the DID.
No, I mean that ` https://did:plc:fpruhuo22xkm5o7ttr2ktxdo@/sh.tangled.feed.star/3m23ddgjpgn22
` (that's your proposal?) isn't a valid URI for https:// scheme. The need for the new scheme comes from being unable to express an identity-rooted URI in other schemes.
Yes, you need to make the part after @ optional, that already exists for other protocols like email. That's why it's still simpler than creating a new scheme from scratch. As far as I understood it it's still JSON over HTTP(S), so then why not use the scheme for that.