141–149 of 149 posts
I'm building a decentralized ai marketplace and guess what? This piece of software is the backbone of our off-chain file transfer protocol. It just works; however, its seeder (BitTorrent-tracker) depends on node-webrtc, and it is not an official node package for web-rtc. It has some weird issues. For example, when you seed the torrent through BitTorrent-tracker, and on the client side (chrome browser), I used chrome:…
Can I buy some of your stock?
Earlier quoted context omitted.
I am on a 200GB capped residential LTE internet connection. Upload is included in that data cap. If this was surreptitiously deployed that would cost me money and generally be not cool.
Seems like the browser should warn of a webRTC connection coming from the site.
Earlier quoted context omitted.
Seems like the browser should warn of a webRTC connection coming from the site.
Sounds like a job for an adblocker
Controlling invasive technologies like camera use or file browsing cannot be realistically achieved by an adblocker.
Earlier quoted context omitted.
That attitude is totally fine if you don't care about having people visit your site more than once.
Most people will view the content they like.
Earlier quoted context omitted.
I wonder if Tailscale have any numbers on how often clients failover to STUN?
But it doesn't matter since STUN is just used for setting up the connection; it doesn't relay traffic. WebRTC always needs a coordination server to exchange tokens, so STUN doesn't make it less P2P.
WebTorrent is obviously well suited for p2p file distribution, but using a minimal subset of the protocol also provides a nice hack for easily bootstrapping peer connections between web app users. Piggybacking on public mediums already designed to do peer exchange can let you rapidly prototype a WebRTC project without the hassle of running your own server anywhere. I built a library that explores this idea: https://g…
I wish more people would pay attention to Trystero because it enables so many interesting use cases. It’s the foundation of https://chitchatter.im/ and I recently wrote about the potential of this library: https://dev.to/jeremyckahn/taking-the-power-back-with-web-me...
For most commonly downloaded torrents, webrtc support is not enough yet, that i know of. While torrent clients like transmission, qbittorrent and rtorrent do not support webrtc it would be difficult to guarantee the spread of this tech that would otherwise be great
Progress is coming along on that! https://github.com/webtorrent/webtorrent/issues/369
I'm building a decentralized ai marketplace and guess what? This piece of software is the backbone of our off-chain file transfer protocol. It just works; however, its seeder (BitTorrent-tracker) depends on node-webrtc, and it is not an official node package for web-rtc. It has some weird issues. For example, when you seed the torrent through BitTorrent-tracker, and on the client side (chrome browser), I used chrome:…
This is pretty cool, but wouldn't it make it harder to get seeds in the first place? Just imagining someone getting their file and closing the torrent tab, I guess you could try and address this with some UI callouts, but as a frequent torrenter, since it runs on a dedicated machine/application I tend to seed heavily.