DDEP-0002:datdot-uri-scheme

[serapath]

@todo

• add first draft of uri scheme proposal to include an app handler
• deal with datdot addresses
• specify standard for "viewer websites" (= installable datdot apps)

---

inspiration

• https://github.com/hypercore-protocol/hyp/blob/master/proposals/0002-hyper-url.md

e.g.

const protocol = `datdot:`
const dhost = `13f94sj9tjw4h40t294hg24h9` // example
const port = `60318` // example port of localhost websocket daemon
const hostname = `${dhost}[:${port}]`
const version_tag = `v123` // example
const hier_path = `foo/bar/baz` // example
const query = `foo=bar&beep=boop` // example
const fragment = `foobarbaz` // example
const uri = `${protocol}//${dhostname}[+${version_tag}][/${hier_path}][?${query}][#${fragment}]`

[serapath]

The structure/protocol behind a certain DHT topic and/or hypercore(s) (e.g. e.g. hypertrie, hyperdrive, cabal, etc...) is solved by DEP-007 and this issue about "related feeds" proposal, so basically, so you don't even need any custom protocol handler at all when it comes to sharing a links

---

BUT:

Which of the of compatible "apps" to use to open content?

• is it a default app?
• is it a custom app?

This is maybe a "related" but different problem.

---

related (sub) proposal:

context
Because it is hard to get new custom protocol handlers into browser, so you can instruct the browser which app to use to show content, i would recommend a different URL scheme, that allows more flexibility, because it only requires a single generic protocol handler for the entire ecosystem.

It is an alternative that does not depend on IANA Or others to:

• datprotocol/DEPs#66 Consider IANA registration of URI Scheme for dat?
• but would still need at least one handler to support that custom URL format, maybe dweb://
  • arewedistributedyet/arewedistributedyet#28 Shared stewardship of the "dweb" protocol handler

proposed format:

1. <querystring> = <param1=arg1&paramN=argN>
2. <p2p url> = <protocol>://<user>:<pass>@<subprotocol>:<hostname>:<port>/<path>?<querystring>#<fragment>

examples

• dat://cabal:87ed2e3b160f261a032af03921a3bd09227d0a4cde73466c17114816cae43336+5
• web+dat://cabal:example.chat:8080/channel/lobby?name=joe&status=idle#2020.05.09-13:37

alternative

• https://hackmd.io/x4Wb4PifSBOGVO8FMCY-IA

any thouhgts on that and whether that is part of this or a separate spec proposal?

related/other sources of inspiration:

• https://en.wikipedia.org/wiki/Magnet_URI_scheme

[serapath]

a reliable standard way to tell what "content" is behind a "dat address"?

* Like if i had a website where you can paste in a dat address (or swarmkey), you would be able to figure out all "types" of data available
* e.g. a `"dat address"` could make available a `hyperdrive` and also serve as a `cabal channel` (where people talk about the hyperdrive)

Next, people could maintain links to `"viewer websites"`
for each of the detectable data or protocol types and it comes with default viewer websites
* Finally, if people click `[open address]` it will open that new website
  (similar to open the correct desktop program for a file extension) and that website will load the content