The DAT protocol will be drop totally?

[lumenpink]

Will the new Hyperdrive protocol supersede it?

[pfrazee]

Correct, we're transitioning from dat:// to hyper://. A lot of the core tech is the same (same developers, etc) but it's a breaking set of changes improvements.

Beaker has a dat -> hyper converter which you can use to update your library.

[Foldover]

I wanted to try the conversion tool, but it merely seem to create an empty index.json file. I suppose that is not the expected behaviour?

[pfrazee]

@Foldover the converter currently only loads dats that were in your library. It doesn't access the network, so any dat hosted via the cli dat command for instance won't load. Does that answer your situation?

[Foldover]

Thanks for replying so fast! The dat was in my library, created via Beaker's browser tools, no CLI involved :). The legacy dat was created in Beaker 0.8 I believe.

[pfrazee]

Hmm sounds like a bug. There does seem to be some interest in better tooling here so I may invest a little more time in better dat:// readonly support and conversion tools. (No promises yet but we're looking into it.)