Sorry, but ultimately it comes down to this: curl is following the RFCs, and you are not.
-
-
Replying to @mathew
Sometimes the RFCs are bullshit. If people followed the RFCs to the letter anyone could DoS any server, because they require vulnerable implementations of things like TCP. This is one of those times.
1 reply 0 retweets 0 likes -
There is a huge gap between "I'm deliberately putting a password in URIs so I can paste them in a command line in the privacy of my home" to "hey browser please attach my password invisibly to every file I download so I can unknowingly hand it to someone in a USB stick"
2 replies 0 retweets 0 likes -
"The RFCs say I can get away with this" doesn't mean that doing something isn't stupid. The RFCs do not aim to forbid all stupid behavior.
1 reply 0 retweets 0 likes -
Replying to @marcan42
Except in this case, the RFCs say you shouldn't do the stupid thing, but you're insisting on the right to do the stupid thing because it's convenient, and then have software take special steps to protect you.
1 reply 0 retweets 0 likes -
Replying to @mathew
I'm insisting in software *not* taking dumb steps like silently shoving URIs into xattrs for no reason. This has been a thing for *years* and I only just found out. This is broken. It's not just about userdata passwords. Nobody expects download URIs to tag along files!
1 reply 0 retweets 0 likes -
Replying to @marcan42
It's not for no reason. It's very useful to know where a file came from and record the URL along with the file download. Safari does it, DEVONthink Pro does it, Evernote does it, etc. Which is exactly why the RFCs say not to put secret info in URLs.
1 reply 0 retweets 0 likes -
Replying to @mathew
Please enumerate those useful reasons. Especially reasons to attach the URI *to the file*, not just metadata in a browser database somewhere.
2 replies 0 retweets 0 likes -
Replying to @marcan42
This reminds me of people who get really angry when they find out about EXIF information. Look, I understand, you didn't know about it — but now you do, so the smart thing is to adjust your behavior accordingly.
1 reply 0 retweets 0 likes -
Replying to @mathew
At least EXIF data is inside the file, and applications display it, and it's just metadata, and pretty much every non-evil camera app has toggles for sensitive stuff like location information. Literally *nothing* advertises "hey your file has an xattr with a URI in it".
2 replies 0 retweets 0 likes
I've "adjusted my behavior" by turning this off in .wgetrc and I may introduce local patches on my package build server to eradicate all traces of this feature across all of my machines. This wouldn't be the first such "kill a stupid dangerous feature" patch I carry locally.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.