I mean, it is obvious for a human inspecting the one specific input and output sample, but how do you do this at scale? (Spoiler: cross your fingers and hope, that's how)
Except when they "extract" something that wasn't in the source. And now what, assuming you can even detect the tainted data at all?
How do you fix that, when the process is literally "we throw an illegible blob at it and data comes out"? This is not even GIGO, this is "anything in, synthetic garbage out"
That is, literally, faith-based business management. "We suck, sure - but wait, a miracle will SURELY happen in version 5. Or 6. Or 789. It will happen eventually, have faith and shovel money our way."
As in, "things that happened before my Xth year of life are Normal, nay, Traditional even. Everything afterwards is Ephemeral, and possibly Heresy as well."
HTAs were equal parts great (for their time) and terrible (plus they stuck around until IE died): a bog-standard webpage, but IE-only and with local-user process execution powers. Also, the local persistence was...problematic.
Well that's a bit of a balancing act, isn't it? "Why isn't this feature on the site, it would be more useful to me; also, that feature is annoying and useless to me" - says literally everyone.
Thus, we get a built-in editor (less friction, yay/too rudimentary, boo) and popups (OSM events, yay/Popups are now everywhere, boo). And endless discussions on "this should be more/less prominent."
I don't think there's any official edict, but the approach "I don't like this and I'll make my own version" is at the very least workable (as opposed to, say, Google Maps).
And that's a great example of missing the context right there. "There's this impossibly great offer here. OF COURSE I take it, because there's no way everyone's getting fired after the first year, why would there be strings attached?"
Once you start taxatively naming "these are the Only Blessed Ranges," you'll be bitten by the usual brouhaha "email address ends with .[a-z]{2,3}". We all know how it went, and ".[a-z]{2,4}" didn't cut it, either, not even in 2000.
The Artist Formerly Known As Prince has entered the chat.
(the name was a unique symbol)
Yes, all abstractions leak, there will always be edge cases. Doesn't mean "JUST USE ASCII DUH" (the lowercase extension is for the wimps); a whole spectrum exists between these extremes.