Register URI with IANA

[flyingzumwalt]

Some sort of URI/URL registered with IANA

Update: see https://github.com/ipfs/in-web-browsers/blob/master/ADDRESSING.md

[daviddias]

I'm currently working on the IPFS integration for the brave browser and I wasn't sure what to go for when it comes for protocol handler. Which should I use to register a handler:

• ipfs:/..
• ipfs://..
• /ipfs/..
• dweb:/
• dweb://
• /dweb/

??

UPDATE: See ipfs/specs#152 (comment)

[flyingzumwalt]

related: ipfs/specs#152 (comment)

cc @lgierth

Go with ipfs:// and ipns://. If you can, also go with dweb: but I doubt that'd work -- from what I understand Brave is based on Electron and its protocol APIs don't support pure URIs yet (is that correct?).

By the way, it's a good time to get URI support into Electron's protocol APIs now. It is because it's also a good time to make a proposal for good progammable protocol handlers in Firefox, and Electron's API might make for a good proposal.

[ebkalderon]

Just a curious lurker here. Has anyone arrived at a conclusion about the browser-compatible address scheme to use? Is anyone still monitoring ipfs/specs#152?

[lidel]

Just for the record, memo about currently suggested URI addressing schemes can be found at:
https://github.com/ipfs/in-web-browsers/blob/master/ADDRESSING.md

[lidel]

@jonnycrunch what would be the first step in registering ipfs://?
Should we register ipns:// together, or is it better to tackle them one by one?