<wpwrak>
"filegive easily sends files point-to-point, with authentication and ciphering, with no software requirements on the receiving side. No third party server is involved in the transfer." duh ?
<wpwrak>
let
<wpwrak>
's see .. no software require on the receiver, not even 3rd party. so how does that work ? quantum teleportation on the magnetic particles of the hard disk ?
<mog>
heh
<wpwrak>
and "ciphering" ... let's say what "dict" has to offer ... ah yes, From Bouvier's Law Dictionary, Revised 6th Ed (1856) [bouvier]: "3. When it is suspected that, a cipher becomes known to the cabinet where the minister is residing, recourse is had to a preconcerted sign in order to annul, entirely or in part, what has been written in cipher, or rather to indicate that the contents are to be understood in an inverted or contrary sense.
<wpwrak>
A cipher of reserve is also employed in extraordinary cases." yes, that sounds plausible.
<kyak>
when mentioning the software required on reciever, should one explicitely mention an operating system?
<kyak>
i guess not. .because it is implied
<kyak>
the same, everyone has internet browser
<wpwrak>
alright, i hope tsx-11 is okay :)
<kyak>
thus it is not mentioned
<kyak>
oh.. yo ushould also mentioned that "a computer" is required
<kyak>
or should you?
<wpwrak>
internet browser ... i'll pick chimera then
<wpwrak>
so that thing is browser-based ? that's what the description should say then
<wpwrak>
and perhaps also what features it expects in the browser ? just html ? does it need cookies ? javascript ?
<wpwrak>
if already the description is that sloppy, what can you expect of the protocol ?
<kyak>
you are just being picky
<wpwrak>
communication protocols are nontrivial. even less so if their authors think they are ;-)
<wpwrak>
naw, that's just a useless description
<kyak>
stop being geek for a second. It's as easy as 'wget url'
<kyak>
no "communication protocols", "cookies", wtf
<wpwrak>
so how does it work ?
<wpwrak>
does it set up a local web server ?
<kyak>
filegive runs an http server, serving the chosen file
<wpwrak>
aha !
<wpwrak>
can it traverse NAT ?
<kyak>
it does handle upnp
<kyak>
so your router must support that
<kyak>
it can also use ssh tunnel for that
<wpwrak>
ah, now come the details :)
<kyak>
--)
coyo has joined #qi-hardware
coyo has joined #qi-hardware
<viric>
kyak: bad url. ?uuid=v0.6
<viric>
wpwrak: what's that rant about? ;)
<viric>
you like the 'no software requirements', right? haha
<wpwrak>
btw, you may want to add one or two timeouts instead of a session counter. e.g., time until the last transfer has to start, allowing any number of transfers until that time.
<wpwrak>
and maybe a deadline extension each time an existing transfer does something. that way, you can also cover reconnects.
<viric>
session counter?
<wpwrak>
the -n X limit
<viric>
well, that mainly gives multiple URLs
<viric>
and it checks that for each URL, someone downloaded until the end.
<viric>
If all URLs are downloaded until the end, it shuts down
<viric>
The alternative is -N, which never shuts down
<wpwrak>
ah, so it already handles reconnects ?
<viric>
yes sure
<viric>
it checks if the download reached the end
<wpwrak>
kewl
<viric>
(if you use a tricky downloading client that submits multiple requests of byte ranges, and the last one reaches the end, it will shut down too, regardless of the first :)
<wpwrak>
yeah, the client could out-optimize itself :) but then, multiple parallel sessions are generally frowned upon
<kyak>
viric: now i get the third different md5sum when using uuid=v0.6
<kyak>
also, the file name is like filegive-0.6.tar.gz?uuid=v0.6