Comment Re:And, of course ... (Score 2) 71
You don't need to buy Micros to get your hands on that data!
(Hint: Micros has suffered some really bad breaches in the past, basically hanging their customers out to dry.)
You don't need to buy Micros to get your hands on that data!
(Hint: Micros has suffered some really bad breaches in the past, basically hanging their customers out to dry.)
Your understanding of history is so terribly flawed that I don't even know where to start.
I myself don't have a single USB 3 host device.
I purposefully bought one of the cheap USB 3 Kingston keys after reading the reviews. Been very happy with it: It often operates at close to the theoretical USB 2.0 transfer rates, and there have been instances where my USB 2.0 host is plainly the bottleneck. It was the right drive for the right price on that particular day, perfectly in the corner of the price/performance curve.
Meanwhile, none of this is news: If you buy an ATA/66 hard drive in 1997, you already know that you don't necessarily get 66 megabytes per second from it because the spinning rust can only transfer things so fast. The speed of the physical interface has typically nothing to do with the rate at which data is transferred, and it never has.
The only thing new here is your own flawed perception.
The summary misses a key point. Yes they scan and store the entire book, but they are _NOT_ making the entire book available to everyone. For the most part they are just making it searchable.
Agreed that it's not in the summary, but as you correctly note, it's just a "summary". Anyone who reads the underlying blog post will read this among the facts on which the court based its opinion: "The public was allowed to search by keyword. The search results showed only the page numbers for the search term and the number of times it appeared; none of the text was visible."
So those readers who RTFA will be in the know.
That's a bad security model in that it relies on the assumption that the local network is physically secure, which is never a good assumption to make.
NetBEUI over the Internet impossible? What are you going to tell me next, that I can't watch TV over the Internet either because the IP doesn't know how to deal with ATSC?
A small SBC running OpenVPN in tap mode will work just fine in a "it's not a router, it's an Ethernet bridge!" sort of way. And...done: NetBEUI, over the Internet, with every bit of untraceable clusterfuck that NetBEUI ever had.
And all you might notice is one or two new MAC addresses lurking around.....if the attacker is sloppy AND if you're paying attention. Which you aren't, or you'd realize that the model is unsound to begin with.
Can this be used as precedent to dismiss all the pending RIAA and MPAA lawsuits? What about reversing past suits whose victims are already in the body count?
Don't I wish.
Are you saying I can't transmit Ethernet frames over the Internet?
Paragraphs.
Pretty please.
Prison is not meant to be torture, but it is meant to be punishment.
The trouble with an FPS or an MMO, or routine fun in general, is that people would be more likely to do dumb things just so that they can live in prison: Three squares a day, one's own bunk, laundry service, and regular gaming sessions?
We've already got enough people who LIKE prison and jail.
I've never had a problem with Hot Pockets: Follow directions, learn how it works in a given microwave oven, and...done: Ridiculously-hot cheap, bubbly, unhealthy goodness.
Meanwhile, I don't need to read TFA to learn how the powdered aluminum wrapper turns RF energy into thermal energy. And I don't need TFA to know that any thing has a certain reluctance toward changing temperatures, as nothing is a perfect thermal conductor.
In fact: Dude, I've been cooking with a microwave since I was a little kid: It was the first kitchen appliance I was certified on other than -- maybe -- an electric can opener.
Up next on
*head in hands*
And when you download an installer, it's a ZIP with a single file: One compressed EXE.
So you extract the EXE (which is not meaningfully bigger than the ZIP), and execute it.
Then, the first thing it does is extract a compressed CAB (which is not meaningfully bigger than the EXE).
After that, it installs the CAB, which could have been accomplished by simply double-clicking on the (again, already-compressed) CAB....now that it's finally exposed after all of the needless wrappers.
This behavior would have never been considered acceptable in the day of the floppy disk, and it shouldn't be acceptable now: It's grossly inefficient in terms of CPU utilization, disk utilization, and (most importantly) human utilization. In many ways, we've forgotten much of what we used to know.
I can't fathom the number man-hours that are wasted daily by end-users just to save a few hours of optimizing such installers once, but if I had to take a guess, I'd think that [human lifetimes wasted] / [day] would be a cromulent unit to factor it in.
I email myself all the time.
I keep backups of most of my data, of course, but email is the most easily-searched, most easily-accessed, and most redundant system I have...and it takes zero additional thought on my part for it to behave in this way.
Additional redundancy is also simple: If something is Really Important to me, I can send it to myself at multiple independent email servers with ridiculous ease.
I've been doing it this way since I discovered IMAP something close to 20 years ago.
The fact that someone is using a tool in a way that you didn't intend should not be taken to indicate that such behavior is wrong, and if IMAP were totally unsuited it wouldn't handle multiple concurrent clients of different types, much less folders, much less generally-sane handling of attachments, much less [...].
(Granted, this is for stuff that is not secret to me -- just important to me. I don't have many secrets, and any that I do have certainly aren't anywhere near the Internet or any other network.)
Thus spake the master programmer: "After three days without programming, life becomes meaningless." -- Geoffrey James, "The Tao of Programming"