the one thing that Dat had that ought to be brought back in some fashion is the "special DNS entry to expose a hypercore on a domain name" - that said, it makes sense that Beaker et al aren't porting that to Hyperdrive/hyper://, since there are totally alternatives to DNS that might make more sense in a hyperdrive-centric p2p paradigm, and it's smart to keep that namespace unoccupied until a canonical approach emerges in that space
that said, something like a hdns:// or dnh:// or something like that would make sense as a stopgap (the one problem with hdns being that it conflicts with the name of a namecoin star registry at the moment)
Another idea: hdat://, for "Hyperdrive At" - also provides a nominally simple way to migrate named Dat links to Hyperdrive ones (just put an h in front of it!)
the one thing that Dat had that ought to be brought back in some fashion is the "special DNS entry to expose a hypercore on a domain name" - that said, it makes sense that Beaker et al aren't porting that to Hyperdrive/
hyper://
, since there are totally alternatives to DNS that might make more sense in a hyperdrive-centric p2p paradigm, and it's smart to keep that namespace unoccupied until a canonical approach emerges in that spacethat said, something like a
hdns://
ordnh://
or something like that would make sense as a stopgap (the one problem withhdns
being that it conflicts with the name of a namecoin star registry at the moment)Originally posted by @stuartpb in https://github.com/stuartpb/beaker/issues/4#issuecomment-1028444339