Hyperdrive or dat for CLI usage?

[vasantm]

Hello, We (a bioinfomatics lab) recently started exploring dat and using it for sharing datasets.
The team is made of people comfortable at the CLI and other bench scientists who rather use a browser to explore/download data.
My idea was to create dat shares for the informatics folks and point other scientists to beaker browser to explore those same data shares.
With the recent release of Beaker Browser and the announcement that you're moving to hyperdrive. What's the best use practice for achieving what we want?
Should we switch to hyperdrive at the commandline as well

[pfrazee]

We're still deciding as a community what to do with the dat CLI. I somewhat think it'd be wise to keep it on the previous protocol for people to access dat:// data, but that may not be what the community decides.

In the meantime, I'd advise using the hyperdrive-daemon now instead of dat. You can find it at https://github.com/hypercore-protocol/hyperdrive-daemon

[vasantm]

Thanks Paul, for the clarification and prompt response. 👍 I think we might test out hypercore to see how it fits our needs

…

On Wed, May 20, 2020 at 4:45 PM Paul Frazee ***@***.***> wrote: We're still deciding as a community what to do with the dat CLI. I somewhat think it'd be wise to keep it on the previous protocol for people to access dat:// data, but that may not be what the community decides. In the meantime, I'd advise using the hyperdrive-daemon now instead of dat. You can find it at https://github.com/hypercore-protocol/hyperdrive-daemon — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1640 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKDHNNDZORGWCZQUL5M6QLRSQ6M5ANCNFSM4NGDQCAA> .