News for hackers. Stuff that matters.
Re:Why curl defaults to stdout by dec0dedab0de on Monday November 17, 2014 @08:09AM (#8617978)
On my laptop, to view something while offline. On a server, to install something that is not in a package manager.
Re:Why curl defaults to stdout by noselasd on Monday November 17, 2014 @08:51AM (#8618172)
On that note, sites that don't easily offer copyable links for download annoys me to no end.

Most of the time downloading anything, I need it on another machine, and normally the easiest way is copy/pasting an URL from my local web browser to a remote terminal, and fetch it using wget. In which case an auto redirect to a mirror selector that again auto downloads the item, all handled by javascript, is pretty frustrating.

Re:Why curl defaults to stdout by fragmede on Monday November 17, 2014 @04:36PM (#8620784)
Re:Why curl defaults to stdout by Igglyboo on Monday November 17, 2014 @09:42AM (#8618353)
I noticed this with mega.co.nz and I hate it, they do all the downloading with javascript then start an actual browser download (which is just copying from localstorage to your download directory) which finishes in an instant but I have to remain on the page now.
Re:Why curl defaults to stdout by cooper12 on Tuesday November 18, 2014 @10:01AM (#8624088)
I don't think it would be possible to use curl for mega because it has to locally decrypt the stream first. I do remember using a (now deprecated) python library that wrapped the mega api [0] a while ago, so that might interest you if you want to do everything from the command line.

[0] https://github.com/richardasaurus/mega.py

Re:Why curl defaults to stdout by TylerE on Monday November 17, 2014 @10:23AM (#8618558)
With Mega it's rather unavoidable as the javascript is running the decryption.