The folks that discovered the AT&T flaw downloaded information on something like 40,000 people and forwarded it to a journalist. Calling the institution itself after a spot check is pretty tame and seems well intentioned on its face compared to the AT&T situation.

It doesn't. The parent said our space program sucked. I was pointing out that for a program that sucks it does some pretty awesome stuff.

Um, yeah, that's what they do in MRIs. Only have to energize it and keep it cool. They get really ticked if they have to turn it off - very time consuming and expensive to turn it back on again.

It is seldom the veracity of facts that the debate is over; it is their significance. But that happens to be where this falls idea falls short, because misinterpretation of facts is where the most potent misinformation comes from.

Case in point, "vaccine injury" -- which is a real thing, albeit very rare. Anti-vaccine activists point to the growing volume of awards made by the US "Vaccine Court" (more accurately called "The Office of Special Masters of the U.S. Court of Federal Claims") as proof that vaccine injuries are on the rise.

It is a verifiable fact that the volume of awards has grown since the early years of the program. That is absolutely and unquestionably true. However, that this is proof vaccine injuries is gross misinterpretation, because the "Vaccine Court" program is no fault. You don't actually have to show the defendant *caused* an "injury", you only have to (a) show the child got sick after being vaccinated and (b) find a doctor to sign off on a medical theory by which the child's illness *might* have been caused by the vaccination.

Since you don't have to actually prove injury in "Vaccine Court", the rise in cases and awards doesn't know vaccine injuries are on the rise. All that is necessary is that more people think that their child's illness was caused by vaccinations, and the low burden of proof will automatically ensure more awards.

And so there you have it. A perfectly factual claim can be cited in a way that leads people to preposterous conclusions.

I looked up maser as you suggested, and one of the uses of a maser is: Masers are being used by a few countries as directed-energy weapons. So what do you think "maser" means? Oh wait, I get it, you are the one suffering from the Dunning-Kruger effect. Clever.

I have systems which have a GUI and yet have no Qt/GTK stuff whatsoever. The less code I can have on the system at all, the less chance that some of it will go wrong. But sometimes you really need a gui config tool of some kind for sanity's sake.

Of course, more and more of those are GTK or Qt apps now so I guess it's not really that important.

Yeah, cause Mars Exploration Rover, GRAIL, Dawn, New Frontiers, Solar Dynamics Observatory, the Spitzer and Kepler telescopes, all those things are boring science. Only nerds find things like discovering Earthlike exoplanets or determining the origin of the Moon thrilling. They should get their own news site so the rest of us don't have listen to stuff that only matters to them.

And how do we know that the real benefit doesn't come from hitting yourself with birch branches?

This is what I said, but we should be clear there is zero resistive heating *until* the superconductivity breaks down. There is a critical current above which a superconducting wire ceases to superconduct (for complicated reasons).

Again not necessarily. For example the web page and the download server might not be the same, in which case it is not true that being able to modify the download necessarily means you can also modify the webpage checksum.

Another example is when people download and stage a large file on their local network, which is very common practice. If the server on their local network, in a sense the file is modified "in transit", but the malware needn't be anything special or exotic. I'd go so far as to say if you stage anything on your own servers you ought to check its hash religiously before using it.

Yet another example of "not necessarily" is monitoring. It wouldn't be hard to automatically monitor the download page for unauthorized modifications. Of course you should monitor the downloads themselves for modifications, but that takes more time. You can monitor the hashes on the download page continuously from another computer, automatically shutting the page down if anything changes. That wouldn't prevent your download page from unauthorized modifications but it would contain the consequences and it's very easy to do.

This is what I mean by it's the stuff that goes *around* a security measure that makes it work. A hash doesn't do anything unless people check the hash. That includes people who are hosting the file. I often think of this as a kind of diminishing returns exercise; since people often have spent *no* effort on preparing to respond to being hacked, often the best marginal expenditure is in that direction.

It's well established that a person may become an "involuntary public figure" -- someone who does not intentionally thrust himself into the public sphere, but whose actions (or inactions) a reasonable person would expect to draw public scrutiny.

So the question is whether becoming a "revenge-porn" impressario is something a reasonable person would expect to draw public scrutiny. You be the judge.

I guess the devs didn't either, that's why they made numerous improvements to the file manager.

True, but last time I read up on this their superconductivity broke down when they carried high currents. They're superconductive enough to be useful, for example making very powerful magnets for NMR machines, but not capable of carrying unlimited current.

The story is definitely an Apple story, in part. They are profiting handsomely from participating in this behavior. It's disingenuous to suggest that it isn't about Apple simply because it isn't all about Apple. At best, you're as hypocritical as what you're complaining about.

Copyright is not necessarily the only law which applies here. It is possible, for example, to have copyright on works you have no right to distribute. If I write a libelous story about you, I *own* that story, but I can't publish it because it is libelous -- unless I alter the story so you aren't obviously recognizable.

IANAL, but I suspect that what matters here is the subject's "expectation of privacy". Even if you got her permission to take her photo with the understanding it's for your *personal* use, she probably has a reasonable expectation that you won't post it on a public website. In that case after a breakup you would retain copyright and the right to use the image for your personal use (although really how pathetic is that?), but you don't suddenly gain the right to share it with the world if that's not the terms under which she agreed to let you take her picture.