4 ms·
"You can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mo
by epaga 13y ago
"You can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem."
https://news.ycombinator.com/item?id=9224 https://news.ycombinator.com/item?id=9224 :)
- tOkeshu 13y agoIt's a really geeky approach. The 949 problem concerns a lot of persons who does not even know what a server is.
- shailesh 13y agohttps://news.ycombinator.com/item?id=8863 https://news.ycombinator.com/item?id=8863 :)
- laumars 13y agoFTP is just a horrible and massively outdated protocol which we really shouldn't be advocating for the modern internet[1]. Particularly when everything you've suggested can be much more cleanly done using existing tools on Linux / UNIX / OS X: scp, rsync, git, sshfs (some of which are often pre-installed on the *nix image) [1] http://mywiki.wooledge.org/FtpMustDie http://mywiki.wooledge.org/FtpMustDie
- nomeata 13y agoNote that all these require transferring the file to the server first, before a link can be shared with anyone, and especially cleaning up later. With my tool, the link is instantly available, and as soon as I stop the program, nothing is left anywhere, especially not on the server.