Throw up a cursive CAPTCHA.

I meant to write that the discrepancies between monthly, early reporting, and later, quarterly reporting, have been a feature for years. Maybe decades. Much of this is structural, survey reporting v statistical reporting, but it's there. An astute observer would generally discount monthly reports knowing thewy are regularly revised in the negative.

I suspect those who have a serious, fiduciary interest in using these reports do indeed rely on the later, quarterly, 'revised' reports, and spend a fair amount of time explaining to their clients the problems with monthly flash reports. It's the problems of restating several months' worth that is of more interest to me. This is an issue of trust.

Yes, fair enough.

"early estimates have been consistently too *optimistic* for many months."

Maybe for many years, in total.

You trust 'them' to operate ML systems better and more objectively than any other system?

Software isn't true, ethical, honest, or trustworthy. Those qualities are what programmers and their employees exhibit. Or don't.

I get concerned when the revisions exceed certain margins. Especially when they restate by 25-50%.

Actually, does anyone who needs accurate data believe the initial reporting for any month? Doubt it.

We've been hearing that forever. Let me know when it actually becomes mainstream.

Add to that AI has yet to prove itself. This just sounds like a line they're giving for investors.

I was 100% C=64 before I transitioned to Apple ][ before I went IBM-PC DOS, briefly Windows/OS2 Warp, then MacOS, then 100% linux, and added Android later.

(sprinkle in some brief CP/M, BeOS, and NetBSD sidequests)

I'll deal with the shift to the next phone platform OK, I think.

I should probably dust off my Pine64 and try the latest builds again. It's been a few years since they were unusable as a daily driver.

Folks, this might be a huge opportunity if you correctly pick the successor and are the first developers.

As it is written, it doesn't eliminate the problem. It only attempts to minimize it. That makes it useless at the intended "privacy preserving"

"USENET died when ISPs noticed few users actually used it" - it also died a bit when deja-news was bought by google, turning it into google groups. ISPs were now thinking (incorrectly, of course) that they were paying for some Google branded service...that was coincidentally getting less use directly because Google was offering a web page interface to the same data.

So it was a gradual fade-out at the ISPs initially as people started trying web-bb's (never totally caught on, and survivers like SJGames' illuminati board have really low participation for the readership, really). The fadeout accelerated when Google replaced the usage of the service AND the impression it was an open, distributed system into Google one that Google alone should be paying for.

I think the real issue is warm parts of China selling to cold parts of India without including the features that aren't needed near the factory. We know lots about battery chemistry, but rural farmers have had more immediately relevant things to know about up to now and don't have a good source of information on this new thing the government is pushing, so they skip things that sound like luxuries and end up with something inappropriate for their purpose.

Should be easy to get rid of those costly CEOs then.

I have a gaming laptop with two USB-A and USB-C ports, and it's a constant struggle to connect all my devices simultaneously without needing a hub. I use the two USB-A ports for my mouse and wireless headset dongles, while a phone charging cable and portable monitor take up the USB-Cs. This setup stresses me out because there's no extra space to connect anything else without losing functionality.

That's entirely why they inventing docking stations.

This is retarded.

1. It isn't for profit healthcare that is the problem, it's THIRD PARTY PAY.
2. I don't use third party pay, ever, for healthcare. I've been insured nonstop for over 30 years, and NEVER ONCE has my insurer paid my doctor.
3. Even when I've had emergencies, I still called around, negotiated a fair cash up front rate, paid cash up front, and billed it to my insurer. My cash up front rate was sometimes below any co-pay negotiated with my insurer, lol.

I just recently had some elective surgery that would have cost me about $2000 on my annual deductible, but I was able to cash pay a negotiated rate of $400 including a follow-up "free". I submitted the $400 to my insurer and they reimbursed me.

Third party insurance exists because YOU VOTERS demanded the HMO Act of the 1970s, which tied health care to employment, and then employers outsourced it to third parties.

Health care is remarkably cheap in the US (cash pay, negotiated) and I don't have to wait months to see a doctor when I call and say I am cash pay. They bump me up fast.

I love these retro stories from 2012.

What a blast from the past!

This is a retro story from 2012, right?

In 2000-2002 I managed security and infrastructure for a high school in Maine. This was a school with many very talented and diligent students. And some were learning to program in Turbo Pascal.

Someone either decided to, or did not notice the risks of, included the network libraries, something that was optional. I asked the publisher, and they confirmed, most school systems did not ask for that.

Sure enough, some students succeeded in writing a new GINA, intercepting attempted logins, and boom - they got a teacher's signon credentials to the NetWare server etc. And wasted no time rewriting some rows in the school grading and scheduling app. Much hilarity ensued.

It took while, but I was able to write a script to readily identify a non-student login, coloring the screen background bright red (it was NetWare, after all), and exposing the perp. The second part of this was a pair of cable scissors for the lab monitor or teacher in attendance. And the script dumped keystrokes to the equivalent of /dev/null for 10, later 15 seconds, trapping the perp at the screen. Some students power cycled, but most were a little stumped.

Instructions to the staff were simple. If a red screen appeared, take the scissors over. If a teacher or staff was not near that station, find the blue cable at the back and cut it. Took me about 30 seconds to re-terminate ethernet cables back than, and I had ago kit to do so, happily if we caught a perp. Most I passed in the hall, and they knew who I was, giving me some mean looks.

Solved in a few days. We left in the goodies, and I was tasked with giving a class on NetWare basics, oh fun. Which led to a much more devious intrusion, and a student being threatened with expulsion from they computer lab for the remainder... Their parents were outraged, this student needed those courses to get into the Ivy League school he was accepted at, early, (Legacy), and this was intolerable. My complaint was capturing data form backups to restore data that had been changed. And a brief discussion, which I led, pointing out that if such unethical if not illegal activity did not disqualify their son from entering that fine institution, well, my esteem for that institution was diminished somewhat. They curbed their child, and we got through the year. with no further detected breaches.

This isn't new, and this sort of behavior predates personal computers. But it is fun. They got to learn somehow.