I'm sorry, when did we go from "logged in your browser history" to "public"? Your argument is bullshit. You're saying that just because a particular thing has some (known) security caveats it's fine to gratuitously introduce more undiscoverable ones to bite people in the ass.
-
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.
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".
-
-
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.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
On the Mac, "get info" windows in the Finder display the source URLs of downloaded files, along with the program used to create the file, and all sorts of other arguably confidential information.
-
This isn't a Mac. I don't know what the standards are like on a Mac. I don't use them and I don't care. I'm talking about this feature *on Linux*.
- Show replies
New conversation -
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.