Few suggestions.
- Would like to see the tx speed.
- Long file names look wrong in the UI.
- Would like to see file size in GB/MB/KB instead of just bytes.
What else would you have expected me to do with it? I mostly built it as an experiment. I was playing around with the new P2P features in flash 10. My first idea was video conferencing (http://www.boostcam.com) which actually manages to more than make up for hosting costs in adsense revenue. If only I had thought to have it connect two random people! This was my second idea. I didn't really think there was much else to do with it. I have some ideas for features, but I have and always will be very limited on time.
Web sockets are implemented on top of a HTTP verb, e.g.:
{Regular HTTP handshake} {Socket negotiation} {Data sent over the open connection}
Unless your browser also accepts incoming HTTP connections it won't be able to accept incoming requests. It's not UDP as you know it, so you can't just fiddle with DNS or a router and re-direct packets to another JavaScript P2P client.
Hopefully that'll get fixed one day. Direct P2P from the browser would be incredibly useful, but there are real problems with cross domain DNS abuse. For example it's possible to use IE6 visitors to run a search engine spider without their knowledge or consent because of the (reasonable sounding) same-domain-cross-iFrame-read permissions.
Yes, it's server-assisted p2p. It's a great tech for getting around firewalls and serves as an effective solution to the "I can't send you the file for some reason" that we were running into daily with our various IM clients.
I know nothing about your service because all I see is a little bit of text that might as well be a middle finger to the user.
and an adobe icon.