What's the alternative if it's "out of date"?

[doraemondrian]

The first thing this repo says is it's out of date. Is this approach permanently discontinued? Or is there an alternative elsewhere I should look at?

Would love to start playing with Dat!

[millette]

Closest thing I found was mentionned in #5

[millette]

Closest thing I found was mentionned in #5

[joehand]

Hey, sorry for the delayed response! Thanks @millette for the assist.

If you are looking to do stuff in the browser, you can use hyperdrive as #5 says via browserify or another module bundler. See a bit more in our docs (under the hood section).

Is this approach permanently discontinued?

It's not discontinued but we found WebRTC performance pretty lacking so we are focusing elsewhere for now.

We also have dat-node if you aren't doing things in the browser.

[joehand]

Hey, sorry for the delayed response! Thanks @millette for the assist.

If you are looking to do stuff in the browser, you can use hyperdrive as #5 says via browserify or another module bundler. See a bit more in our docs (under the hood section).

Is this approach permanently discontinued?

It's not discontinued but we found WebRTC performance pretty lacking so we are focusing elsewhere for now.

We also have dat-node if you aren't doing things in the browser.

[kaosat-dev]

Hi @joehand I am still a bit confused by the usage of hyperdrive : namely:

• can you use the dat ids directly in hyperdrive(without the dat:// protocol of course) ?
• from my understanding of the docs, that would still suffer the same limitation as dat-js ie only being able to connect to other WebRTC based peers ?

[kaosat-dev]

Hi @joehand I am still a bit confused by the usage of hyperdrive : namely:

• can you use the dat ids directly in hyperdrive(without the dat:// protocol of course) ?
• from my understanding of the docs, that would still suffer the same limitation as dat-js ie only being able to connect to other WebRTC based peers ?

[joehand]

can you use the dat ids directly in hyperdrive(without the dat:// protocol of course) ?

Yes, the ids used in dat are the same as the hyperdrive id (archive.key).

from my understanding of the docs, that would still suffer the same limitation as dat-js ie only being able to connect to other WebRTC based peers ?

Correct, that is one of the big reasons we moved away from it. You can use electron-webrtc to connect to webrtc clients in node.

[joehand]

can you use the dat ids directly in hyperdrive(without the dat:// protocol of course) ?

Yes, the ids used in dat are the same as the hyperdrive id (archive.key).

from my understanding of the docs, that would still suffer the same limitation as dat-js ie only being able to connect to other WebRTC based peers ?

Correct, that is one of the big reasons we moved away from it. You can use electron-webrtc to connect to webrtc clients in node.

[kaosat-dev]

thanks for the quick answers @joehand !
one last question if you do not mind based on

Correct, that is one of the big reasons we moved away from it. You can use electron-webrtc to connect to webrtc clients in node.

This means there is currently no purely client side option to connect to the overall hyperdrive/ dat network at large ?

[kaosat-dev]

thanks for the quick answers @joehand !
one last question if you do not mind based on

Correct, that is one of the big reasons we moved away from it. You can use electron-webrtc to connect to webrtc clients in node.

This means there is currently no purely client side option to connect to the overall hyperdrive/ dat network at large ?

[joehand]

This means there is currently no purely client side option to connect to the overall hyperdrive/ dat network at large ?

Correct (ish). Its a bit confusing.

There is not really a dat network "at large," it depends on how clients connect to each other - and you can only connect to clients that speak the same "language". Most of the tools (command line, desktop, beaker) use the same network protocols (tcp, udp, mdns) for discovery and data transfer so they can all co-exist. But none of those work in the browser =(.

To connect to other types of clients from the browser you need a proxy that can connect webrtc clients to tcp/udp clients. That's been in our TODO for awhile but it's harder to prioritize webrtc/browser for our use cases.

[joehand]

This means there is currently no purely client side option to connect to the overall hyperdrive/ dat network at large ?

Correct (ish). Its a bit confusing.

There is not really a dat network "at large," it depends on how clients connect to each other - and you can only connect to clients that speak the same "language". Most of the tools (command line, desktop, beaker) use the same network protocols (tcp, udp, mdns) for discovery and data transfer so they can all co-exist. But none of those work in the browser =(.

To connect to other types of clients from the browser you need a proxy that can connect webrtc clients to tcp/udp clients. That's been in our TODO for awhile but it's harder to prioritize webrtc/browser for our use cases.

[carloslfu]

Hello @joehand, is there a list or a roadmap for that? If not, would be useful to have one. I want to contribute with this specific use case. Some thoughts on how to contribute would be appreciated.

[carloslfu]

Hello @joehand, is there a list or a roadmap for that? If not, would be useful to have one. I want to contribute with this specific use case. Some thoughts on how to contribute would be appreciated.