Demo is not working for me about trystero HOT 6 CLOSED

I updated the default trackers list that the demo site uses. Let me know if it's working for you now.

from trystero.

@jeremyckahn Right now it's a manual process, but it would be ideal to automate it.

Two things I've been looking at to improve the robustness of the torrent strategy:

1. Adding support for PeerTube instances' WebTorrent tracker servers. There are over 1000 active instances so this could be a nice source of redundancy. However I've found PeerTube trackers to be very fussy with announcing new info hashes and I haven't figured out why yet.
2. I don't know if any trackers support it but WebTransport supports direct streaming connections over HTTP/3. This could open up a set of trackers beyond the few that support WebSockets.

Always open to PRs if you find anything viable with these or any other options.

from trystero.

Thanks for keeping Trystero updated/active!

from trystero.

Right now it's a manual process, but it would be ideal to automate it.

In case it's helpful, I found https://github.com/ngosang/trackerslist which seems to automatically manage a list of up-to-date trackers (somehow). Here's that project's list of WebSocket-compatible trackers: https://github.com/ngosang/trackerslist/blob/master/trackers_all_ws.txt

We may be able to set up an automation that pulls from that source.

from trystero.

For me the complete tracker list was failing. Try running the demo locally and passing in a custom trackerList property that contains: wss://tracker.webtorrent.dev

from trystero.

@dmotz thank you for updating the tracker list! Out of curiosity, do you have a specific process for finding and updating it? I'm just wondering if keeping the list up to date is something that could be automated.

from trystero.