webtorrent
bittorrent-dht
Our great sponsors
webtorrent | bittorrent-dht | |
---|---|---|
80 | 3 | |
28,981 | 1,198 | |
0.7% | 0.5% | |
9.2 | 5.8 | |
2 days ago | 15 days ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
webtorrent
- Bitmagnet Allows People to Run Their Own Decentralized Torrent Indexer Locally
-
I Moved My Blog from IPFS to a Server
It's because of the kind of content that is shared. BitTorrent serves a lot of content you are not allowed to redistribute, so having an open gateway immediately puts you at risk of aiding the distribution of content. But it does work, someone even made something native to browsers so browsers themselves can share content: https://webtorrent.io/. There are even fuse "gateways" to make it native to your computer and pretend the files exist locally: https://github.com/search?q=bittorrent+fuse&type=repositorie...
IPFS doesn't seem to be used for that kind of content much, it seems to be targeted more towards web-native content (html pages, images, that kind of stuff). It's probably safer for Cloudflare to run this.
- WebTorrent – JavaScript torrent Streaming In browser
-
How can i make a torrent streamer similar to webtorrent and stremio?
title. I have some experience with c++ but not much with torrent libraries. (webtorrent, stremio)
-
Now that Netflix is cracking down on account sharing, can we please get physical releases?
You can stream torrents
- Ihr dürftet nur noch einen Streaming-Dienst (Musik, Filme, etc.) abonnieren. Welcher wäre es?
-
Suggestions to host 10TB data with a monthly and100TB bandwidth
If it fits your model, WebTorrent[0] can offload a lot of bandwidth to peers.
[0] https://github.com/webtorrent/webtorrent
- 25 Linux mirror servers hosted on 15W thin clients serve 90TB of updates per day
-
Time to watch my favourite ads featuring videos!
Then https://github.com/webtorrent/webtorrent could be used to actually download the videos in browser, the idea being here though, that you would at least seed out as much as you got. Enabling other's to access videos without requiring creators have the infrastructure to push a video to 1000s or more clients at once.
-
Use Case for WebTorrent / http seed / browser to browser etc. ?
I assume you've seen https://webtorrent.io/ ?
bittorrent-dht
- Theseus DHT Protocol
-
Static torrent website with peer-to-peer queries over BitTorrent on 2M records
I'm not talking about the consensus protocol of the blockchain itself, but of the p2p algorithms underlying it, e.g. using Kademlia for service discovery and message routing. I'm asking why a distributed system would choose something like Consul (which uses Raft, and requires a coordinator node) instead of running a decentralized protocol like Kademlia (which has no coordinator nodes) within their distributed single-tenant environment.
I did a bit more research last night, and discovered that Bitfinex actually does something like this internally (anyone know if this is up to date?) [0] — they built a service discovery mesh by storing arbitrary data on a DHT implementing BEP44 (using webtorrent/bittorrent-dht [1]).
This seems pretty cool to me, and IMO any modern distributed system should consider running decentralized protocols to benefit from their robustness properties. Deploying a node to a decentralized protocol requires no coordination or orchestration, aside from it simply joining the network. Scaling a service is as simple as joining a node to the network and announcing its availability of an implementation of that service.
At first glance, this looks like a competitive advantage, because it decouples the operational and maintenance costs of the network from the size of the network.
So I'm wondering if there is a consistent tradeoff in exchange for this robustness — are decentralized applications more complex to implement but simpler to operate? Is latency of decentralized protocols (e.g. average number of hops to lookup item in a DHT) untenably higher than that of distributed protocols (e.g. one hop once to get instructions from coordinator, then one hop to lookup item in distributed KV)? Does a central coordinator eliminate some kind of principle agent problem, resulting in e.g. a more balanced usage of the hashing keyspace?
Decentralization emerged because distributed solutions fail in untrusted environments — but this doesn't mean that decentralized solutions fail in trusted environments. So why not consider more decentralized protocols to scale internal systems?
[0] https://github.com/bitfinexcom/grenache
[1] https://github.com/webtorrent/bittorrent-dht
-
Decentralized in-browser torrent site
Yes the database is fixed. I would like to make it updateable using web2web or mutable torrents (BEP44) which the WebTorrent DHT supports.
What are some alternatives?
peerflix - Streaming torrent client for node.js
ipfs-pubsub-room - IPFS Pubsub room
ipfs - IPFS implementation in JavaScript
bittorrent-tracker - 🌊 Simple, robust, BitTorrent tracker (client & server) implementation
instant.io - 🚀 Streaming file transfer over WebTorrent (torrents on the web)
torrent-paradise - Decentralized DHT search site for IPFS
webtorrent-mpv-hook - Adds a hook that allows mpv to stream torrents
webtorrent - ⚡️ Streaming torrent client for the web [Moved to: https://github.com/webtorrent/webtorrent]
webtorrent-desktop - ❤️ Streaming torrent app for Mac, Windows, and Linux
peer-vnc - Secure Access VNC from anywhere based on noVNC
rats-search - BitTorrent P2P multi-platform search engine for Desktop and Web servers with integrated torrent client.