Telecos will say yes to the "fix caller ID" agenda, but then do nothing at all. Legitimate call centers use the same change-of-caller-ID features that illegitimate ones use. That legitimate stream of money means that there is also lobbying for no-change. Businesses need this feature if they are to leverage call center services from other countries.

Can we get rid of them? Or maybe apply some some trig math based on angle to midday sun?

If you were burning coal to liquefy air you'd care a lot. If solar/wind and a surplus, you'd not care as much even though that construction and acreage also costs money. Diversity of energy storage implementations would be good I guess.

Acetaminophen on wikipedia redirects to Paracetamol because most of the world knows Acetaminophen as Paracetamol. See: https://en.wikipedia.org/wiki/... Is that the source of the confusion/controvesy?

That from a reddit comment from the dev team. In my own research (as a user of Flutter for 1.5 years now), most external to google dev teams using Flutter don't rely on FlutterDriver anyway - too hard to setup, too slow and too fiddly to do basic things. It reminds me of Selenium-RC from 15 years ago (which is my fault). Thank goodness WebDriver came along and did the reverse-takeover of the project.

Too bad. SPAM & spoofed senders needs to be addressed. As it happens an all-carrier initiative to use a messaging system to confirm non-spoofed originator/sender is entirely possible - https://twitter.com/paul_hamma...

SPAM is why we're fixing it.

ARexx has "interpret" which was amazing. That stuff is still better than AppleScript today.

I'd prefer to see something that was email, but evolved some. Like Wave was. Here's something I did to make IMAP a little more dynamic - https://github.com/paul-hamman...

How ironic that a technical copy/paste error makes it into a /. article about facial recognition being used in a risky way by maw enforcement: ... "The stakes are too high in criminal investigations to rely on unreliable â" or wrong â" inputs," Georgetown researcher Clare Garvie wrote.... If you're browser is hiding the error it is in front of each of the quote marks for "or wrong".

Multiple nodes are competing to update the ledger? How many of them? how many different companies/orgs are involved in the running of those (that would indicate competition)? Many different codebases are involved for the service, or just one depoyed in parallel to all those nodes? I've not been able to reach the execs at Voatz to get answers and I've tried.

Where is the data for the PACE trial? https://me-pedia.org/wiki/PACE.... Can unrelated researchers rake over same data to verify the conclusions within it? No.

That said, harassment is bad. In order to play fair, activists should restrict their activities to release the "release the data behind the findings for the PACE trial that's now found its way into policy, or withdraw/retract the published papers and the policy". I don't myself have CFS/ME but I have been following it. Over 25 years now, I've known three people personally with CFS/ME and totally see how debilitating it is to have, and frustrating to have to explain/justify in front of friends/relatives as well as some/many health care professionals. Just as MS has now advanced to treatable with a stem-cell reboot, and Parkinson's & Altzhiemer's are showing signs of pathogens being the cause, that's the direction of research that's being delayed by PACE directed findings (allegedly).

A twitter account to follow - https://twitter.com/keithgerag... - a medical professional with CFS/ME who's doing his best to sift through everything for the rest of us.

https://github.com/paul-hamman... - a visualization of ad partners adding ad partners to a page (ad infinitum)

Similar enough to https://patents.google.com/pat... and only because I'd previous built one (and dismantled it) from Meccano in 1991 and tried to patent it (rejected) after thinking the world needs more wind power :-(

Prior to 2005, Intel bought a chunk of DEC to get VLIW technology (for their Itanic CPUs) as well as StrongArm. The latter turned out to be wasteful to manufacture, which is one reason it could not remain.

Atom came from a semi-competing group was working on an X86 SoC thing. Apparently they were overly optimistic about making low power SoC processors because they sold the StrongArm/XScale stuff _early_ to create room in a number of ways for what they thought to be this super compelling X86-compatible line.

This was convincing enough for Steve Jobs to commit to X86 and drop PowerPC as then Intel CEO, Paul Otellini, had shown the roadmap of the forthcoming CPUs to Steve Jobs. Not just Core-Solo and Core-Duo ("Intel Core" micro-architecture stop-gaps), but Atom which would deliver power savings to rival ARM.

The intention was to flip to Atom when it was ready. I'm speculating that would have meant Atom for phones too. As the power profile of the Atom chips being released was years behind the predicted timelines, Apple pivoted to ARM for the iPhone's launch as their fat-binary tech made that easier than it would for others (still speculation).