[computer]

So my interpretation of how this works is that there's a server at api.iflix.io[1] which acts as (caching?) torrent client, and the browser just streams from that server. Seems like it probably won't last very long due to copyright issues, and/or will have very high bandwidth costs?

You can use it to download arbitrary torrent files by modifying the URL. For example, a changed link[2] downloads an Ubuntu ISO.

So there's no peer-to-peer work done by client-side javascript. (The server is written in NodeJS.)

[1] http://api.iflix.io/play/_SOME_MAGNET_HERE_/0

[2] http://api.iflix.io/play/b6b8ce579988a85b2a3ec8cd870ccb785d7...

[eglover]

ZZLBox/Furk have been doing something similar for a long time for real bandwidth costs on their side. If the DMCA had the authority they wished they had, Pirate Bay wouldn't exist.

I would like to hear the answer to your other question though. It looks like a marriage between the iflix server and your own connection with most bandwidth being put on your side.

[0x4139]

Well, the thing is that this will work as a storage space with streaming capabilities what you put there is your problem, in short terms some kind of loophole in some countries can be found, the bandwidth is not a problem, solutions can be found there.

[0x4139]

ihim :), it would be cool if you would watch a movie, not download an ubuntu iso :)