Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)

TechnicallyWeb3 left a comment (whatwg/url#883)

> For example:
> 
> ci-- for Chain ID
> us-- for user signature
> ua-- for user addresses
> And so on...
> This means, you can be sure that people can't use these as their domains, but you can use them for other things to carry information.

I like this solution. But how about we do this instead:

host: the host
id: chain ID
sig: user signature
user: user address

We can't use `-` since it's url safe and people may register host--tw3.eth as a domain for malicious reasons so let's use `:`

So now URLs will look like 
`wttp://user:user.ethsig:0x1234host:tw3.ethid:11155111`

Except we don't really need `user:` since it's at the beginning we can just imply it. And here's an idea. We can even replace `host:`, `id:` and `sig:` with a single symbol to shorten them. Let's try something like this:

host: = `@`
id: = `:`
sig: = `;`

So our URL now looks like this:

`wttp://user.eth;0x1234@tw3.eth:11155111`

I think we could agree on this name based URL delimiter since it separates the different parts uniquely. Does it make sense to shorten them to a single non-url safe character as I suggested? 

If we take your idea to it's conclusion we get something that looks awfully like what we started with. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/883#issuecomment-3368445326
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/883/3368445326@github.com>