This is particular bad for multifamily apartment EV charging, where for good reasons the electrical panels and thus the GFCI reset buttons are in a locked room, accessible only to building management.

The NFPA Code Making Panel 12 moved forward with a set of rules that's very hostile to apartment charging, at least as it's done in the USA.

It's pretty much "apt get upgrade". The local amendments are small.

Random letter sellers on Amazon sell the cheapest EVSE, with no record of a safety test.

Yet, the NEC decides to go after a non-issue like this. The huge thing that could be done for EVSE safety is to require Amazon check the listing status of electrical equipment. Then leave well enough alone on the incremental frog drip GFCI expansion.

Message to the NEC: the elephant in the room are installers who don't read your document selling stuff from companies that don't read your document.
The EVSE GFCI rule was a mistake and should be reversed.

You have a vivid imagination.
That said the insurance industry could, but has not, shared AFCI claims related data. They could know if AFCIs are having a claims reduction benefit.

True that:
The original CSPC cost-benefit analysis of the matter, which is still online, showed a marginal (small) cost benefit. But a fairly large profit benefit.

You'd think it was such a big problem something might show up at the NEISS:

https://www.cpsc.gov/Research--Statistics/NEISS-Injury-Data

But, no.

The real hazard are cheap EV outlets, and the fact that companies with names consisting of random letters
sell chargers on Amazon for cheap, and nobody cares. Meanwhile those who actually follow the NEC, UL, SAE and test at a NTRL get hosed by the rules. Go Figure.

The SAE long ago designed personal protection into the EVSE standard.... and it WORKED.
It works GREAT.
The NFPA is muddling in areas they don't understand well, and missed the point.

The extra GFCI devices are expensive, unreliable, have a limited lifetime, and generate panel board heat and use energy. But most importantly are not needed in this application at all. There is NO NEED for a GFCI on a hard wired EVSE.

The article's title uses hyperbole. The issue is real.

If Apple and Google can't properly sandbox apps.... that's the real story. It should be impossible for this or any app to do that much...

And when it comes to how to supplement iodine in remote areas, it turns out to be pretty easy:

    A new approach to combatting iodine deficiency in developing countries: the controlled release of iodine in water by a silicone elastomer.
    A Fisch, E Pichard, T Prazuck, R Sebbag, G Torres, G Gernez, M Gentilini
    Am J Public Health. 1993 April; 83(4): 540–545. PMCID: PMC1694489 http://www.ncbi.nlm.nih.gov/pmc/articles/PMC1694489/

As long as the local shamans don't feel it takes away their business....

And we're going on 5 days here... they owe an explanation. Internap in this case is our provider, hosted within 365 MAIN Oakland:

"> a. Request for Reasons for Outage Guarantee Internap will use
> commercially reasonable efforts to ensure that Customer will be sent a
> formal written Reason for Outage (RFO) on events isolated to Internap’s
> Service Point as quickly as possible, and in any event less than five (5)
> business days from the date of Customer’s request. RFO’s extend beyond
> Internap’s standard notifications given for all events and can contain
> additional details regarding an event. This service point specific
> guarantee excludes backbone problems and any other services provided by
> Internap’s vendors, partners, or affiliates. Failure to meet this objective
> may make Customer eligible for a service credit to be applied to Customer’s
> next monthly invoice for Services."

Sounds like you would benefit from a site level "current events" feed, that always has the most recent events. Then a per-event feed that, after the event, changes to "thank you for coming, see more at "current events". And that feed expires 3 months after the event.

If people are collecting your old feeds, but not getting value from them, is that actually valuable traffic? Are you interested in getting the word out, or counting fictional traffic?

You can also rename the feed to archive old information. Renaming the feed breaks the links to lazy readers. Anyone who really wants to research your old event data will search for it starting at your home page.

The core of my letter, sent today, is:

"IE is not available for Linux, and I have no interest in purchasing a different computer -- your action will disenfranchise me. There is no technical justification for such an exclusionary move by a public agency -- the open and democratic process of developing web standards has resulted in tremendous diversity and choice in Internet software. The proposed Copyright Office ruling undermines the very integrity of the web, and makes a mockery of the international standards effort that built the web."