12 ms·
WebTorrent
- NegativeLatency 4y agoThis 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.
- metadat 4y agoFortunately there are other ways to seed independent of WebTorrent clients. You are right, it'll be mainly used for HnRs. In some cases this is okay or even desirable.
- UI_at_80x24 4y ago> ...it'll be mainly used for HnRs... Evil work-around: show "file-progress" as % of 2:1 seeding? File isn't 'downloaded' until you have uploaded 2x!
- TremendousJudge 4y agoThat won't work, you can only mandate at most 1x; otherwise you have more supply than demand and users will never be able to "finish" their downloads
- vxNsr 4y agoAlso from my own experience downloading Linux ISO’s it can often take weeks to share back to a 1:1 ratio. Especially for less popular distros.
- Hamuko 4y agoI once thought about using webtorrents on a video on-demand site that I was hosting. The idea would've been that I'd have the video available on the server both through HTTP and BitTorrent, and when a lot of people start watching the same VOD at the same time, they'd help seed it to each other and reduce the burden on the server. Never actually made it since the server that I had was actually good enough to serve people at least decently.
- Raed667 4y agoCheckout PeerTube https://joinpeertube.org/ https://joinpeertube.org/
- deleted 4y ago[deleted]
- palata 4y agoThose with a good internet connection will download faster than they play the movie. Say for a 2h movie, it gets downloaded in 15min and shared for the remaining 1h45min...
- lxgr 4y agoBesides being an amazing technical achievement, I find this very interesting legally, as it further blurs the line between passively viewing content hosted somewhere and redistributing/actively sharing content. Have there already been cases of websites making their visitors unwitting peers, similar to e.g. JavaScript cryptocurrency mining?
- mk_stjames 4y agoMy first thought was like "Oh, this is like CryptoJacking a browser window but for file storage instead". Of course, it is technically amazing, and pretty neat that this is possible at all, and could have some very interesting edge-use-cases.
- klabb3 4y agoWell spotted. In other words, WebRTC lets a site owner have their visitors distribute content directly to others without their knowledge or consent, basically making it impossible to argue that the distributor has intent to do so in the general case. That said, it was already highly questionable for legal application, since a torrent client can run on any machine connected to a home wifi, including guests and compromised machines. It may have been enough for a "hey, you're breaking our tos, please check your devices" from the ISP, but should never have been more than that (like threatening letters from rights-holders).
- _def 4y agoI totally agree, that's how it should be. In reality right now there are countries in which you get cease and desist letters and a ~800 Euro fine for even a short amount of seeding. This is a cool technology but also allows more automation in this shady industry and laws will take years and years to follow up.
- 6510 4y agoclicking a link wouldn't count, I mean, what link? oh, now you are seeding too?
- 4y ago
- zackees 4y agoIf implemented this use the webseed feature so you can get serverless seeding. You can add the seed dynamically on the client when there are no peers as indicated by the tracker.
- mhitza 4y agoI couldn't find out at a glance, but is the webrtc connection between peers encrypted or plain sniff-able?
- Sean-Der 4y agoWebRTC is encrypted and authenticated. No concerns about that! Another nice thing about WebRTC is that it uses DTLS. You can’t block web torrents because that would also block conferencing software and corporate VPNs (Cisco)
- ementally 4y agoReally great concept. I found this also interesting https://hypercore-protocol.org/ https://hypercore-protocol.org/
- deleted 4y ago[deleted]
- goosesanta 4y agoIsn't this supposedly what bitchute has been using for years?
- simlevesque 4y agoTLDR: it can't connect to normal trackers without a bridge
- martimarkov 4y agoOr if the desktop clients add WebRTC support. Sod of them have done it others are in the process of adding the support
- toomim 4y agoYes, and as feross says in a comment on this page: "WebTorrent is fully supported in nearly all the most popular torrent clients, including uTorrent."
- jordigh 4y agoOh, huh, I first knew about this from Peertube, and I assumed they were the ones who had created it. It seemed like a really clever solution to the problem of "how do I host my own YouTube without needing a massive infrastructure to deliver video?" Really cool to learn that Webtorrent is a generic API that others can use. There seems to be a lot of good ways it can be used to decentralise the web again.
- giantrobot 4y agoWhen exactly do you think the web was "decentralized"? The web the majority has ever interacted with has always lived on someone else's server. Self-hosting has always been rare. It's weird seeing people talk about some mythical history where the web was somehow decentralized.
- dragonwriter 4y agoDecentralized doesn’t mean that every website is distributed to user-local edge servers, it means that there isn't a single point of failure of the web (that is, the web is decentralized, individual sites are still, separately, centralized.) The emergence of central dominant vendors for key services reduces that (AWS, MS, Google, and CloudFlare are each capable of disabling a lot of the web with a failure; and there are backbone providers that can have similar effects) somewhat, of course.
- giantrobot 4y agoThis idea ignores that 1) there's always been points of failure for the web and 2) there's reasons the dominant players became dominant. The web in real terms requires infrastructure for content to be available. Without that infrastructure you've just got dead links. But this has always been the case. There's no golden period to go back to. The dominant players in the infrastructure business can end service for individual customers but they don't run everything. You can spin up a server and point your DNS records at it and be online if CloudFlare drops your site. They exist because it's cheaper to buy infrastructure in bulk and sublet it but that doesn't stop anyone from making their own server on their own infrastructure. Edit: fat fingered button
- sva_ 4y agoI was wondering how it works, since I'm pretty sure WebRTC has some overhead. Turns out that > In order to support WebRTC's connection model, we made a few changes to the tracker protocol. Therefore, a browser-based WebTorrent client or "web peer" can only connect to other clients that support WebTorrent/WebRTC.
- robertheadley 4y agohttps://github.com/webtorrent/webtorrent/issues/369 https://github.com/webtorrent/webtorrent/issues/369
- nightpool 4y agoI've always been very, very nervous about the privacy implications of this technology. Creating a persistent, public record of every IP that has ever accessed a particular video is a HUGE step backwards compared to current video/file distribution systems, and I don't think end-users correctly appreciate the trade-offs yet of making that sort of information public and joinable across domains / different activity (i.e. "give me a list of all users who view LGBT content and also watch online instructional videos for my Christian school").
- runarberg 4y agoI think the good ol’ saying applies here as well that security through obscurity is not secure. Here like in other aspects it is best to secure users in such a way that if a christian school does a search like that and punishes students based on what they do in their free time (or worse their gender perception or sexual orientation) then there should be an easy course of action through the legal system for the student to get justice (and for the school admins to be punished).
- Etherlord87 4y agoYou shouldn’t rely on security by obscurity, but you also shouldn’t resign from it. In the end of the day, if you have a password hidden somewhere, it’s also security by obscurity.
- runarberg 4y agoHardly. A password is usually hidden written in a notebook (or a local hard-drive) which would have to be physically stolen in order to obtain, or in a password manager which is (hopefully) encrypted. I think a better analogy is in how different countries handle national identification numbers. Some countries have a publicly accessible list encouraging people to share it when commercing, these countries usually have other means of preventing identity theft. Other countries issue identity numbers in a private manner, discouraging and prohibiting distribution. These countries use obscurity to prevent identity theft among other measure. However anecdotally it seems like identity theft is rampant in the latter countries which includes obscurity in the id-theft prevention, but not in the former.
- baobabKoodaa 4y agoP2P connections over the web are usually not possible due to typical consumer router configurations and bad decisions in the design of WebRTC protocol. The vast majority of these P2P web projects, including WebTorrent, is actually using proxy servers to fake the illusion of P2P connectivity (to be specific, they are using TURN servers to proxy traffic). Here's a stackoverflow question I asked about this and burned a 100 bounty on it with no answers: https://stackoverflow.com/questions/70624649/webrtc-fails-to-connect-p2p-even-though-peers-can-send-udp-packets-to-each-other https://stackoverflow.com/questions/70624649/webrtc-fails-to...
- Sean-Der 4y agoThis isn't true. In 2017 appear.in published some numbers. They saw ~15% were not able to do P2P. https://medium.com/@fippo/what-kind-of-turn-server-is-being-used-d67dbfc2ff5d https://medium.com/@fippo/what-kind-of-turn-server-is-being-... Reading your stackoverflow link my guess is that you aren't using STUN. A P2P connection can't be established without a NAT hole punch. Also if possible I would avoid the terms `Full-cone NAT` and `Symmetric NAT` they don't do a good job of describing what is actually happening. NAT Mapping/NAT Filtering is the best way to describe it. I wrote a little bit about it here [0]. To see what type of NAT you have try stun-nat-behaviour[1] [0] https://webrtcforthecurious.com/docs/03-connecting/#nat-mapping https://webrtcforthecurious.com/docs/03-connecting/#nat-mapp... [1] https://github.com/pion/stun/tree/master/cmd/stun-nat-behaviour https://github.com/pion/stun/tree/master/cmd/stun-nat-behavi...
- baobabKoodaa 4y ago> In 2017 appear.in published some numbers. They saw ~15% were not able to do P2P. https://medium.com/@fippo/what-kind-of-turn-server-is-being- https://medium.com/@fippo/what-kind-of-turn-server-is-being-... Thank you for this. I guess P2P connectivity is more often possible than I thought! For the record, I have tried to form P2P connections with multiple different devices and multiple different network conditions, and although I have been able to achieve connectivity with Python, I have not been able to achieve connectivity with WebRTC. So I have reason to be suspicious about claims regarding web P2P connectivity. > Reading your stackoverflow link my guess is that you aren't using STUN. A P2P connection can't be established without a NAT hole punch. I described NAT hole punching in my stackoverflow question, where I asked why isn't WebRTC doing this? I was using a STUN server (edit: I mixed up TURN and STUN servers and edited this post to fix that. My stackoverflow question has clear references to how I was trying to achieve connectivity - it has been a while so not everything is in clear memory for me.)
- sbdaman 4y agoWebTorrent is the first torrent client that works in the browser. YEP, THAT'S RIGHT. THE BROWSER. This is beside the point but I really, really hate when services write their home/about/faq pages in this style.
- pyrolistical 4y agoImagine visiting a website and the ads are sent to you via webtorrent and your browser diligently reshares it. Not only do you suffer the ads, you unwittingly contribute your resources (power and bandwidth) to propagating them
- comprev 4y agoThat is a great example of how all technological developments have an equal and opposite negative side.
- anaganisk 4y agoReminds of PeerCDN acquired by Yahoo and built by same author, it used to work beautifully. https://web.archive.org/web/20150810065820/https://peercdn.com/ https://web.archive.org/web/20150810065820/https://peercdn.c...
- dv_dt 4y agoSeems like ad blockers have a new field to look at. I was just thinking about what how people would feel about this when they’re on limited or metered bandwidth.
- pyrolistical 4y agoSounds like an amazing browser feature to meter bandwidth. Not only does it increase accessibility of the internet for low bandwidth users (they will use more if they know they won’t blow out their budget) but it will help shame the bloated websites with more user visibility into the issue
- __MatrixMan__ 4y agoSeems like it needs a way for users to decide what they share so that we can just share the content and let the ads 404. Hell maybe we can even pay each other--both for the hosting and for the data work necessary to keep the malware (e.g. ads) out.
- dang 4y agoRelated (others?): WebTorrent Desktop 0.23 - https://news.ycombinator.com/item?id=23877912 https://news.ycombinator.com/item?id=23877912 - July 2020 (36 comments) Show HN: WebTorrent Desktop 0.22.0 - https://news.ycombinator.com/item?id=23856223 https://news.ycombinator.com/item?id=23856223 - July 2020 (2 comments) Libtorrent adds support for the WebTorrent protocol - https://news.ycombinator.com/item?id=23818659 https://news.ycombinator.com/item?id=23818659 - July 2020 (87 comments) Libtorrent adds support for the WebTorrent protocol - https://news.ycombinator.com/item?id=23775267 https://news.ycombinator.com/item?id=23775267 - July 2020 (1 comment) Learn WebTorrent and WebRTC - https://news.ycombinator.com/item?id=23365708 https://news.ycombinator.com/item?id=23365708 - May 2020 (6 comments) Dweb: Building a Resilient Web with WebTorrent - https://news.ycombinator.com/item?id=17858555 https://news.ycombinator.com/item?id=17858555 - Aug 2018 (22 comments) Nile.js – A Peer-to-Peer Live Video Streaming Library built on WebTorrent - https://news.ycombinator.com/item?id=14443968 https://news.ycombinator.com/item?id=14443968 - May 2017 (20 comments) Show HN: WebTorrent CDN with graceful degradation - https://news.ycombinator.com/item?id=14303618 https://news.ycombinator.com/item?id=14303618 - May 2017 (6 comments) Instant.io – Streaming file transfer over WebTorrent - https://news.ycombinator.com/item?id=12526717 https://news.ycombinator.com/item?id=12526717 - Sept 2016 (67 comments) Product clones using WebTorrent - https://news.ycombinator.com/item?id=12510479 https://news.ycombinator.com/item?id=12510479 - Sept 2016 (7 comments) WebTorrent Desktop – Open source streaming torrent client - https://news.ycombinator.com/item?id=11442116 https://news.ycombinator.com/item?id=11442116 - April 2016 (80 comments) WebTorrent – BitTorrent over WebRTC - https://news.ycombinator.com/item?id=10921773 https://news.ycombinator.com/item?id=10921773 - Jan 2016 (94 comments) Webtorrent – BitTorrent over WebRTC - https://news.ycombinator.com/item?id=10607747 https://news.ycombinator.com/item?id=10607747 - Nov 2015 (108 comments) Instant.io – Streaming file transfer over WebTorrent - https://news.ycombinator.com/item?id=9569315 https://news.ycombinator.com/item?id=9569315 - May 2015 (40 comments) Node and Browser BitTorrent Client (JavaScript+WebRTC) - https://news.ycombinator.com/item?id=9336472 https://news.ycombinator.com/item?id=9336472 - April 2015 (2 comments) Instant.io: End to end browser based web torrent - https://news.ycombinator.com/item?id=8317714 https://news.ycombinator.com/item?id=8317714 - Sept 2014 (2 comments) WebTorrent now works in the browser, end-to-end - https://news.ycombinator.com/item?id=8317441 https://news.ycombinator.com/item?id=8317441 - Sept 2014 (83 comments)
- m00dy 4y agoI'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://webrtc-internals to debug rtc connections. First time in my life, I coined the term connection leakage. A bug in the WebRTC handshake leads to too many connections (300+) for even 1kb torrents. I hope it gets solved very soon. I also attach my node profiling output. Looking for some advise if you have any.. [C++]: ticks total nonlib name 5511 16.9% 43.2% epoll_pwait 692 2.1% 5.4% __pthread_cond_timedwait 682 2.1% 5.3% __lll_lock_wait 413 1.3% 3.2% __GI___pthread_mutex_lock 338 1.0% 2.6% __GI___pthread_mutex_unlock 128 0.4% 1.0% __write 84 0.3% 0.7% __pthread_cond_broadcast 83 0.3% 0.6% __lll_unlock_wake 62 0.2% 0.5% __mprotect [Summary]: ticks total nonlib name 153 0.5% 1.2% JavaScript 8206 25.2% 64.3% C++ 116 0.4% 0.9% GC 19811 60.8% Shared libraries 4411 13.5% Unaccounted [C++ entry points]: ticks cpp total name 692 27.3% 2.1% __pthread_cond_timedwait 679 26.8% 2.1% __lll_lock_wait 413 16.3% 1.3% __GI___pthread_mutex_lock 337 13.3% 1.0% __GI___pthread_mutex_unlock 100 3.9% 0.3% __write 84 3.3% 0.3% __pthread_cond_broadcast 82 3.2% 0.3% __lll_unlock_wake 52 2.1% 0.2% __mprotect
- ThaUnknown 4y agohey, I'm one of the few remaining active WebTorrent devs and I've seen this issue myself, to the point where it's simply easier to use NWjs or Electron with node integration and use chromiums wrtc implementation instead of the wrtc package, if you ever manage to find a better replacement for wrtc for node tell me, and I'll make sure it's implemented ;p
- porsager 4y agoPerhaps node-datachannel could be a viable alternative? https://github.com/murat-dogan/node-datachannel https://github.com/murat-dogan/node-datachannel
- dmotz 4y agoWebTorrent 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://github.com/dmotz/trystero https://github.com/dmotz/trystero And here's how it talks to WebTorrent servers to bootstrap peer connections: https://github.com/dmotz/trystero/blob/main/src/torrent.js https://github.com/dmotz/trystero/blob/main/src/torrent.js It also allows encrypting your peers' session descriptions to hide them from the torrent server. All of this is of course experimental and I'm very open to feedback.
- jckahn 4y agoThank you so much for your work on Trystero! It’s one of the most amazing projects I’ve ever found. I’ve used it to great success on multiple projects and I’m a big fan. I don’t understand how Trystero doesn’t have thousands of GitHub stars by now. 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/ https://chitchatter.im/ and I recently wrote about the potential of this library: https://dev.to/jeremyckahn/taking-the-power-back-with-web-meshes-omg https://dev.to/jeremyckahn/taking-the-power-back-with-web-me...
- deleted 4y ago[deleted]
- jadbox 4y agoHow should I look at WebTorrent vs IPFS?
- draugadrotten 4y agoas an opportunity for a clever hack to merge the two
- ream88 4y agoWhat is the particular reason WebTorrent is trending today? Anything new? I mean, its my main torrent software since a few years now
- airstrike 4y agoLikely the Ten Thousand rule in effect https://xkcd.com/1053/ https://xkcd.com/1053/
- feross 4y agoDisclosure: I'm the author of WebTorrent. It's so fulfilling to see WebTorrent still popping up on Hacker News after all these years. I started the project in 2013 and devoted most of my 20s to working on it, ultimately becoming a full-time open source maintainer. I started WebTorrent with the goal of extending the BitTorrent protocol to become more web-friendly, allowing any browser to become a peer in the torrent network. Within less than a year of starting the project, I got WebTorrent fully working (see https://news.ycombinator.com/item?id=8317441 https://news.ycombinator.com/item?id=8317441). And it worked _well_, beating many native torrent apps in terms of raw download speed and the ability to stream videos within seconds of adding a torrent. WebTorrent never got as much attention as the cryptocurrency projects selling tokens throughout the mid-2010s, even though WebTorrent _actually worked_, and it had more users than almost all of them :) I was never tempted to add a cryptotoken to WebTorrent, despite many well-meaning friends telling me to do it and cash in. Nonetheless, WebTorrent served as an accessible on-ramp to the world of decentralized tech, along with other projects like Dat (https://dat-ecosystem.org/ https://dat-ecosystem.org/) and Secure Scuttlebutt (https://scuttlebutt.nz/ https://scuttlebutt.nz/), playing a role in getting people excited about decentralization. But WebTorrent is more than a protocol extension to BitTorrent. We also built a popular desktop torrent client, WebTorrent Desktop (https://webtorrent.io/desktop/ https://webtorrent.io/desktop/), which supports powerful features like instant video streaming. We also built a `webtorrent` JavaScript package (https://socket.dev/npm/package/webtorrent https://socket.dev/npm/package/webtorrent) which implements the full BitTorrent/WebTorrent protocol in JavaScript. This implementation uses TCP, UDP, and/or WebRTC for peer-to-peer transport in any environment – whether Node.js (TCP/UDP), Electron (TCP/UDP/WebRTC), or the web browser (WebRTC). In the browser, the `webtorrent` package uses WebRTC which doesn’t require a browser plugin, extension, or any kind of installation to work. If you’re building a website and want to fetch files from a torrent, you can use `webtorrent` to do that directly client-side, in a decentralized manner. The WebTorrent Workshop (https://webtorrent.github.io/workshop/ https://webtorrent.github.io/workshop/) is helpful for getting started and teaches you how to download and stream a torrent into an HTML page in just 10 lines of code. Now that WebTorrent is fully supported in nearly all the most popular torrent clients, including uTorrent, dare I say that we succeeded? Not only that, but we helped the JavaScript ecosystem a ton by writing hundreds of npm packages including buffer (https://github.com/feross/buffer https://github.com/feross/buffer), simple-peer (https://github.com/feross/simple-peer https://github.com/feross/simple-peer), and StandardJS (https://standardjs.com/ https://standardjs.com/). It's been a long and winding journey, but I'm glad to have played a role in making WebTorrent happen. Huge shoutouts to all the open source contributors to WebTorrent over the years, but especially Diego R Baquero and Alex Morais who were critical to WebTorrent's success. If you're curious what I'm up to now... I'm building Socket (https://socket.dev https://socket.dev) with an awesome team of open source folks. And there's actually a WebTorrent connection, too! Before Socket, we built an end-to-end encrypted file transfer app, Wormhole (https://wormhole.app https://wormhole.app), using WebTorrent under-the-hood (Show HN thread: https://news.ycombinator.com/item?id=26666142 https://news.ycombinator.com/item?id=26666142). Like Firefox Send before it, security was a primary goal of Wormhole (see security details here: https://wormhole.app/security https://wormhole.app/security). But one area where we felt we could improve the security of Wormhole was in how we audited our open source dependencies. Like most teams building apps with JavaScript, we had a large `node_modules` folder filled with lots of constantly-updating third-party code. The risk of a software supply chain attack was huge, especially with 30% of Wormhole visitors coming from China. As most teams do, we enforced code review for our first-party code; but as most teams do, we pulled in third-party dependencies and dependency updates from npm without even glancing at the code. It's too much work to read every line of code of all dependencies. But the status quo would leave our users open to supply chain attack and we wanted to do better for our users. We looked around for a solution to detect signs of attack and to analyze the risk of various open source packages, but none existed. So we built Socket to help developers ship faster and spend less time on security busywork by helping them safely find, audit, and manage OSS. By analyzing the full picture – from maintainers and how they behave, to open-source codebases and how they evolve – we help developers and security teams to identify risk from malware, hidden code, typo-squatting, misleading packages, and more.
- squarefoot 4y agoWhile I absolutely love BitTorrent and make heavy use of it, I still am not sure if embedding it in a browser is a good thing. I have no doubts about the usefulness, but wouldn't a low priority daemon, or even a client on a minimal external system such as the smallest *Pi-like board, be more functional? It would also speed up peer discovery. As an example, I have my client as a service on my XigmaNAS NAS, so that it stays on even after all PCs in the house are turned off at night, and frankly I can't imagine going back to a traditional client or a browser, therefore a PC to stay turned on to work. ...Unless I completely misunderstood the purpose of this software.
- andirk 4y agoI think you're right in that there are more beefier implementations outside of the browser, but the point of creating an app that is in the browser is almost entirely for minimal barrier of entry.
- juandjara 4y agoFor 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
- xd1936 4y agoProgress is coming along on that! https://github.com/webtorrent/webtorrent/issues/369 https://github.com/webtorrent/webtorrent/issues/369
- ThaUnknown 4y agothe main hold-up on this is actually libtorrent not releasing WT support in a full release yet, from my talks with qBit devs, there's a lot of people waiting for them to simply include it in a release as it seems stable, and there are quite a few people using it on rasterbar, see https://tracker.btorrent.xyz/stats https://tracker.btorrent.xyz/stats
- billconan 4y agoI want to build a social network, and use a p2p protocol for sharing large files. I know that peertube claimed to use bittorrent, but then it seemed to drop it? What's the catch? And is ipfs better or worse?
- billconan 4y agochecked peertube's doc, they don't seem to drop bittorrent. in addition to it, they also use webrtc.
- matt3210 4y agoThis would let you Torrent a file download (like Ubuntu of course) in your phones browser, using no data cap instead of using a data capped tether to a computer
- vaylian 4y ago> WebTorrent is the first torrent client that works in the browser. YEP, THAT'S RIGHT. THE BROWSER. Not quite. Opera had built-in support for Bittorrent for quite some time: https://www.reddit.com/r/todayilearned/comments/ec79j/til_you_can_download_torrents_within_opera/ https://www.reddit.com/r/todayilearned/comments/ec79j/til_yo...
- nchi3 4y agoIt's quite obvious that it means "running in the browser engine" rather than "has the technology implemented in a native language". But sure, you're technically correct.
- pastacacioepepe 4y agoNot sure about the Opera Bittorrent support, but WebTorrent is years old, don't be fooled by the fact it's been posted here today. I remember first trying it at least 5 years ago.
- bdhcuidbebe 4y agoMeh. We had firefox plugins before that. https://www.xenoveritas.org/node/113 https://www.xenoveritas.org/node/113
- peterweyand 4y agoThe Brave browser already does this and has for some time.
- feross 4y agoBrave does it using the WebTorrent library :)
- SergeAx 4y agoThank to that, I've just learned about open movies and am very excited. I wonder how far open movies can get us in the indie scene, can it make impact similar to open software. I watched Tears of Steel and thought to myself: "My, some parts of this are so cheesy!" and then immedeately thought "But if you don't like it - you may fork the project and make it better!".
- airstrike 4y agoI've always imagined this is how the internet will work in space
- xd1936 4y agoWebTorrent seems like the most obvious solution for distributing Linux ISOs. Instead of coordinating networks of volunteer http mirrors, the download webpage of various distributions could simply use WebTorrent and operate one webseed... Then every user becomes a seeder. They are usually going through the trouble of making torrent files anyway. I made a proof-of-concept of this idea during the pandemic for fun[1]. It doesn't work very well without WebRTC peers though. 1. https://linux.exchange/ https://linux.exchange/
- Avamander 4y agoI often use the torrent download option because it's faster than the HTTP download. Hopefully WT will offer that experience seamlessly at some point. Though, not that many torrent clients support WT yet, so it'll take a bit for the swarm to become multiprotocol. Same with v2 torrents really.
- deleted 4y ago[deleted]
- izzytcp 4y agoIt hasn't receive any meaningful update in years now. For those wondering if you'll be fined if piracy is forbidden in your country by using WebTorrent the answer is yes, at least in Germany. They have some good trackers, speaking from experience. :)
- wutbrodo 4y ago> WebTorrent Desktop This is kind of amusing
- v3ss0n 4y agoPeertubr already does the YouTube over webrtc like torrent part