feature.
By default, this corrects the URL to https, so if your lainsafe
instance is running in port 80 (Tor, or something) (altough is very
possible you copypasted the onion address so it contains the http://
thing). That's a TODO. I'll fix it one of these days.

lainsafe instances. but okay

Merge pull request 'Url formatting is handled by the server' (#1) from czar/lainsafe:feature into master

Reviewed-on: https://git.kalli.st/qorg11/lainsafe/pulls/1

Before this commit lainsafe would generate a random string
which can create coallition between two files and shit would
happen, after this commit, lainsafe generates its filenames by
getting the UNIX time in miliseconds (like 4chan)

official server is lainsafe.duckdns.org which does not use CF

guess

Also added documentation about --tor and --get-respone to the manpage

You have to have tor running in 127.0.0.1:9050, if you have it on
another port please change line 81

I haven't tested this a lot, it seems to work with
https://lainsafe.duckdns.org but does not work with
https://lainsafe.delegao.moe (thanks cloudflare!)

TODO: check if was possible to connect to the proxy

links. Closes #9

link to a file (~/.cache/lainsafecli by default). Which allow the user
to keep track of the file they have uploaded.