As the OP, I want to say that while some of you seem to get it, I don't quite get what's wrong with those of you making fun of the post... this is absolutely a story of interest to people interested in science. It was for me, by way of example and if you're not, why are you here? But perhaps you don't understand that this is a rare solar-system event that even amateurs can actually watch as the transition happens. Amateur and pro astronomers will definitely be making time-lapse videos of it happening and I for one am interested in seeing that. If this is of no interest to you, why don't you just pass the post by as most sane people would. Most of us don't read many of the posts on /. even though they absolutely deserve to be on the main feed... because we're not interested in the subject. We don't bitch about them being there though. Sheesh.

Well, it's simple really: it costs Google time and thus money to fulfill these requests and, more importantly, undermines their ability to SELL THAT DATA instead of giving it to LEOs. QED.

Well, the whole point of this technique is precisely that it is fundamentally, provably and demonstrably NOT able to be "faked out". You're missing the entire point of it I'm afraid. We've long suspected that this was possible but no one had actually "discovered" the mathematical technique to do this... until now.

Check out EEVBlog on youtube for Dave's scathing debunking of this crap ( https://www.youtube.com/watch?... ) . Under the absolute best possible conditions - which the real-world case probably can't get within an order of magnitude of - you're looking at 500W input for 5W charging. And 5W charging would be pretty slow anyway but there's just no way they can actually reach that in any event.

Look: all you millennials making fun of us old farts for making a big deal out of the Y2K "bug" (not a bug but a crisis actually) you weren't there working in the trenches, you don't know shit about it, and so you should listen to us old farts instead of trying to take the piss out of us for what you think was scaremongering. This was a HUGE problem - especially when we're talking about embedded systems. I spent five years on-and-off testing and remeditating systems in anticipation of the date roll-over. There were countless systems that would have fundamentally failed if not fixed. And while I can't speak to the issues faced in many other specialties, some examples I personally worked on included : a) a number of widely-deployed medical dosimetric pump models that would have just silently stopped working on Jan. 1, b) some large-ship engine maintenance controllers that would not have issued maintenance alerts because their internal date calculations erroneously indicated no maintenance was due for decades and some that could no longer calculate fuel level (due to consumption-over-time calc issues), c) most legacy accounting software suites couldn't properly calculate payable and receivable aging, d) banking systems that would suddenly calculate a hundred years of interest on a balance, and e) payroll systems that would have deducted a year's worth of benefits and tax in the first payroll of the year 2K. There were numerous other similar issues – many of which were difficult to even FIND because the machines were tucked away in a closet in some factory or nuclear power plant basement that no one had even looked at in years because, well fuck, they always just worked. You need to understand that in many cases we were dealing with arcane, very poorly-documented and understood systems.

But the point is that millions of techs spent many millions of hours to FIX THE SHIT . BILLIONS and BILLIONS of dollars were spent world-wide on Y2K remediation over just a few years. I made a shit-ton of money doing that – and bear “workplace politic scars” as a result because of pin-head non-tech managers who just didn't get it. And I worked alongside other firms that had dozens and dozens of coders and engineers whose SOLE JOB for years was Y2K remediation of legacy systems. Generally, we're not talking about systems designed and implemented in the 90's but systems that originated in the 70's and 80's that had basically still ran the world in the 90's! This is code running on a host of even-then obsolete Z80 and 8080-based industrial microcontrollers and also computers made in the 70's and 80's by the likes of DEC, MAI, Tandem, Altos, IBM, Wang, Ohio Scientific, etc. running COBOL, FORTRAN, MAI BASIC, VAX BASIC, DEC BASIC, FoxPRO (er, foxbasic) and tons of other languages (damn, coders these days have no fucking idea how much of world commerce was controlled by the BASIC language in all it's multifarious forms!). And I worked on all those and more. Much of the code we fixed for the Y2K bug was trivial, and some of it was important. Many technical papers I read at the time indicated there were many systems out there that were really critical to fix - though I didn't work on many such, I know people who did and it was scary.

So yeah, the world wouldn't have ended but we would all have lived with a lot of pain for a while if so many talented people hadn't realised there was a problem and worked so fucking hard to fix the shit that we inherited. If you weren't in the trenches then you really have no idea about how bad it could have been if not for all the talented people heeding the alarms that started ringing in the mid 90's.

Many people posting here seem to have some serious difficulty with reading comprehension. The post did not imply the *exploit* was racist (that would be asinine), but rather Apple's response to it and their downplaying of any real-world consequences of a serious iOS exploit. Further, they refused to acknowledge that the exploit was used by China to target a specific ethnic minority even though that's abundantly clear; they say things like "a small number of web-sites" to obfuscate the fact that the small number of web-sites in question pretty-much is the totality of web-sites used by the ethnic minority in question. So all this discussion that here about "racist exploit" is completely and utterly off the topic. And as far as it goes, Apple's response is the only thing at issue here. We expect better from a corporation such as Apple that tries to position itself as a positive moral force in the world via it's PR and marketing. So instead of going off and discussing which platform has inherently better security how about talking about the issue. That is, was Apple's response - i.e. lambasting Google and saying it's overblowing the result - appropriate given the very serious fall out that appears to have resulted. Apple can't be blamed that they there WAS an exploit but they sure as shit can be called out for making it out to be no big deal - which is precisely what they are trying to do. And yes, their response can be construed as racist because it is incredibly insensitive to the plight of the Uyghurs due to the well-documented human rights abuses by China in Xinjiang and elsewhere against them.

Officials also said that this system was a long time in coming and will help to ensure that hackers only have to compromise one database now instead of dozens. "It's just silly that hackers have had to target so many different systems in the past" said one official. "Now, the process is streamlined for everyone." he added.

You sir, are very demonstrably ignorant of this issue. I'm so sick and tired of you right-wing American F**ks who do not understand the FIRST THING about universal health care. First, yes, Canadians travel to the US for healthcare but many Americans also come here because it's WAY, WAY cheaper to pay for world-class hospital care here if you need it and are not covered in the US (which is about 11% of the overall American population according to: https://www.cnbc.com/2017/04/1... ). BTW, in Canada, that number is 0%. Everyone is covered; well, unless you're an American coming up here trying to get healthcare 'cause you'll die in the US - then you'll have to pay for it... about 25% or so of typical US charges for many things. *WE* may travel to the US because it's FASTER to get certain types of procedures in the US - specifically elective and those for non-life threatening conditions - and pay an insane amount of money for it. Obviously, this means RICH Canadians. Having had three major surgeries here in Vancouver over the last four years, which were all performed by extremely qualified surgeons and support teams in a timely manner even though none of them were for life-threatening conditions in the short term. In the US, my insurer (if I was lucky enough to have one) would probably still be dicking me around on wether or not they'd cover it. I can also tell you that if I had been in the US, as an independent software developer, it's very unlikely I'd have any coverage at all except for perhaps under the ACA. So there. While I wish no ill on you just because you're a right-wing 'tard, part of me kinda hopes that you find yourself suddenly without HC and with no ability to pay for it - and needing it or you'll die. Then maybe you'll get it.

I posted above... I'm with you man. My C is pretty rusty but I can do UI / feature design and would very much be interested in doing testing, QA, etc. Eudora with it's MDI, unequalled search capability, MBOX format, filtering, and folder creation/transfer capabilities make it the best (IMHO) email client out there bar none. Tried the rest, stayed with the best.

I have had that happen maybe twice and all it does is crash the app (been using Eudora since the late 90's). Based on my reading, there's no way any BO vulnerability exploit will be able to do anything on your box (at least under Windows) beyond crashing the program. If you know something that I don't please post a link to some technical article that explains how the EXE could be exploited to do more than crash it.

Yup, me too (same version). I've tried several other email clients but nothing compares to Eudora IMHO still - even with it's deficiencies. The MDI interface, the easy (albeit at times klunky) filter creation, excellent multi-parameter search capability, MBOX format (excellent to train my Spamassassin on the mail server), easy folder creation and transferring, etc. etc. Yes, there are security concerns but not if you're careful and set things up correctly. If someone decides to take on the project of modernizing it, please reach out to me - I'M IN to help! (post reply to this post with some way to get in touch).