Aw, cool :D I'm really interested to see where this goes. I just fired it back up to have another look, and I thought of a couple more ideas: - If it's not t

Aw, cool :D I'm really interested to see where this goes. I just fired it back up to have another look, and I thought of a couple more ideas: - If it's not too hard, maintain a live-updated index of how many peers are available for each file on the file listing page (and extend the API so it returns this data too). That way I won't be sitting waiting forever because I can't tell the difference between a backend outage and peer unavailability for a given file, which is currently the case. - While writing the above idea I thought of this: maybe, at least to begin with, it might be useful to use a "store'n'forward" type model with the system, where you say "I'm interested in <this> and <this> file", then once the files download, the site uses desktop notifications to update you. (I imagine your API works push-style, so API clients would probably behave similarly to this by design as well.) - Categories of some kind might be a good idea at some point. If you do implement these, I think everyone would appreciate if it worked like IRC's /list command - a giant "here's the whole thing" dump, somewhere. Nobody really knows the full list of subreddits, and on Medium.com there's no public list of categories at all. - Sometime wayyyy down the track... it would be epically awesome if you could allow people to have the option to put OTR under their posts. There are JavaScript implementations, FWIW, but I'm not sure whether it's possible to form a cryptographically secure AND anonymous link using OTR... if it is, a lot of people would love it. - At the moment when you click a file it opens in a new tab. That means a new WebSocket connection for each file. It would both be nicer UX and lighter on the server if you open files in the same window, methinks. - I unfortunately haven't seen what happens when you open a file, but if it doesn't exist yet, having a "6 other peers agree on file content" message in the corner of the post view would be a cool idea. [Staring at "connecting...."] Yeah, you definitely need to update the file list so it shows peer counts for files. :P Maybe you could add some "last-resort" code to the backend that hands you the file if there are no other peers, along with a "warning: this file is not being delivered using a peer" type message (in red :D)?