Hi, it seems as if the website, and most web implementations are now offline and not working because of a content delivery error. Also, a similar issue has been posted on instant.io's github

The overly technical UI that https://instant.io currently has should move to https://webtorrent.io.

Instant.io should be easy and friendly.

Right now they're hidden which makes it hard to navigate between pages

We have supervisor listening to automatically restart the server, but we should prevent the crashes because they cause the site to be intermittently unavailable.

Error: socket hang up
    at createHangUpError (_http_client.js:203:15)
    at Socket.socketCloseListener (_http_client.js:235:23)
    at emitOne (events.js:82:20)
    at Socket.emit (events.js:169:7)
    at TCP._onclose (net.js:469:12)

• change node color depending on seed/leech state
• show transfer rate between nodes (by changing thickness of line?)
• show additional peer info (client name, version, country) when clicking on peer
• show web seed node in the graph (it's omitted right now)
• show upload speed (MB/s) in the interface (when it's not 0 B/s)

webtorrent.io exhibits the nefarious "mysterious audio syndrome": I was introducing someone to bittorrent clients via webtorrent.io, and the sintel video starting playing while they were scrolled down the page, producing audio that wasn't immediately identifiable. It would be swell if the video player only automatically played if the player element is onscreen.

Thanks for making webtorrent! ❤️ 👋

• Post the docs from webtorrent/README.md
• Publish a BEP (webtorrent/webtorrent#168) for torrent client implementers to use

• http://tracker.webtorrent.io/announce
• udp://tracker.webtorrent.io

https://github.com/feross/webtorrent-tracker

Hello, im trying to install this website demo and im getting this error on Ubuntu 16.04

/home/feross/www/webtorrent.io/bin# ./deploy.sh
Already up-to-date.
npm WARN deprecated [email protected]: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated [email protected]: Deprecated, use jstransformer
extract:xhr → gunzTarPerm ▌ ╢█████████████████████████████████████████░░░░░░░░░░░░░░░░░░╟
./deploy.sh: line 14: 15602 Killed npm install --production --quiet

Im really dont know how to start to install, im starting from this shell script 'deploy.sh'...

my pkg:
dpkg -s nodejs Package: nodejs Version: 5.11.1-1nodesource1~xenial1

thanks !

What version of WebTorrent?
version - 0.98.18
What operating system and Node.js version?
OS X Sierra - Node v7.10.0
What browser and version? (if using WebTorrent in the browser)
Tried both Firefox and Chrome [Version 58.0.3029.110 (64-bit)], both latest versions.

this codepen works
but the video doesn't show, it just downloads the whole file.

error I get:
GET https://webtorrent.io/torrents/Sintel/Sintel.mp4 net::ERR_CONTENT_LENGTH_MISMATCH
``

Let's feature 3-10 of the most impressive apps that use WebTorrent from here: https://github.com/feross/webtorrent/blob/master/docs/faq.md#who-is-using-webtorrent-today on the homepage of webtorrent.io.

so for example it's possible to link "Complete HTML page example" in https://webtorrent.io/intro

like https://github.com/feross/webtorrent/blob/master/docs/get-started.md#complete-html-page-example

I'm not sure how it's extracted from there and rendered in webtorrent.io

ah yeah it's done with jade https://github.com/feross/webtorrent-www/blob/d5e123b00da784aeba1aa0bee53d4ccaab0daf26/server/views/intro.jade#L3 so we probably need some kind of jade setting

Some simple responsive CSS would go a long way to making the site look decent on mobile.

Test experience on all browsers, including those that lack WebRTC support.

Saw this on iOS chrome, which is not a very helpful message.

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

On https://webtorrent.io, we're showing Sintel, which is well-seeded and has a web seed (i.e. it's also available over http). On medium-speed public wifi here in New Zealand (where I'm visiting), the Time to First Frame is a few seconds. I think there's more we can do to make this faster.

Possible ideas:

• Add the web seed "peers" as soon as possible
• videostream should get better! cc @jhiesey
• Add the video tag to the page as soon as possible to save DOM rendering and reflow time.
• Use a smaller video file, so less data is needed to start playing the video.
• Use a video that doesn't start with 3 seconds of black screen (this is just a perception thing)
• Web seeding should fetch larger chunks than 16KB (block size) (webtorrent/webtorrent#67)

https://gitter.im/feross/webtorrent

Cross-post from webtorrent/webtorrent#844

Are the torrent-graph somewhere available as a repo?

    var TorrentGraph = require('../lib/torrent-graph')

It's really cool, I'd like to reuse it.

Original report of issue was at webtorrent/webtorrent#815

In my case I am on a usage-caped satellite Internet connection. It is rather hard to visit the website to learn about webtorrent because of the data that will be consumed while I try to read the webpage.

The suggestions proposed by @franciscop on the original issue were:

• Download a 2-3MB file. However this is not so cool as you cannot see the video itself, but much better than using the user's data plan.
• Detect the device/screen and choose to download only on desktop. However this is probably error-phrone.
• Add a "stop" button (or a "start" one) so the visitors can toggle the torrent download at will.

Note: I am not a fan of the second one because there are many cases (such as mine) where you do not want the automatic download on a desktop either.

The code from the youtube videos and the slides are encoded to html entitties and therefore not interpreted by the browser.

Examples:

1. https://torrentfreak.com/webtorrent-brings-bittorrent-to-the-web-impresses-netflix-151213/
2. https://torrentfreak.com/webtorrent-desktop-streams-torrents-beautifully-1604xx/
3. https://torrentfreak.com/webtorrent-250k-downloads-strong-with-zero-revenue-160827/

More positive press coming soon, hopefully! 😎

• HTTPS: https://en.wikipedia.org/wiki/HTTP_Secure
• HSTS: https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
• CSP: https://developer.mozilla.org/en-US/docs/Web/Security/CSP/Introducing_Content_Security_Policy

https://github.com/sashahilton00/webtorrent-site

After doing npm install and npm build I can't do npm start . Am I missing something or is this a bug?

http://imgur.com/Vl5B5TS

Right now, whenever someone commits to this repo, the website goes down for a minute while the new code is git pulled, npm installed and the node process is started.

I'm okay with a few seconds of downtime for https://webtorrent.io, but not for the tracker, which is relied upon by other services. When the tracker is down, peers can't find each other.

• Tutorial
• Basic code samples
• Friendly, helpful video

GitHub is silly slow. I bet they're throttling us, since we're using around 600GB of bandwidth per month at the moment. We've received 2 reports of this, and I just experienced a crawling download on a 40Mbps connection. I bet this is affecting our download rates.

Looking into Fastly and MaxCDN at the moment: https://twitter.com/feross/status/780555558713643008

If neither of those can offer us free CDN, then we can try CloudFlare.

See: https://news.ycombinator.com/item?id=10923152

Run 2 instances of node so when the tracker gets overwhelmed with connections and crashes, it won't take down the webtorrent.io homepage too.

• What is WebTorrent? (share the vision)
• How does WebTorrent work? (share the technical details)
• What is WebRTC?
• Why don't I see any peers?
• What can I build on top of WebTorrent?
• Who is using WebTorrent today?

I've installed the webtorrent plugin for Vuze and the announces are telling me that the webtorrent.io tracker is not connecting. IT says,

"Connection failed., UnresolvedAddressException"

Other webTorrent trackers like OpenWEBTorrrent tracker and my version of bittorrent-tracker work perfectly fine. I'm not sure if the server you were running it on crashed from the load or you need to register the IP to the domain again but it's been ~24 hours and still no connection.

Aiming to make two torrents:

• 480p (less than 50MB, for demos on slow networks)
• HD

Video should be CC license, or we should have permission to use it