In the #ACCESSAct hearing, @RepThomasMassie called the shared vulnerabilities in large-scale hacks as stemming from "interoperability." That's factually wrong. They have "shared dependencies" (use the same code/modules). This isn't the same thing as "interoperability."
Then @RepThomasMassie correctly warned that when firms get to define standards to their proprietary advantage, it produces monopoly power. However, #ACCESSAct provides for OPEN standards, developed independently of large firms.
The problem of proprietary advantage through capture of standards is well-understood and the #ACCESSAct takes account of it.
@RepThomasMassie is right to worry that if you have to buy a license to interoperate with "the big guys," it would be unfair. But that's not what #ACCESSAct provides for - rather, these are open standards, unencumbered and freely implementable (as all the best standards are)
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Before covid, "remote proctoring" tools were a niche product, invasive tools that spied on students who needed to take high-stakes tests but couldn't get to campus or a satellite test-taking room. But the lockdown meant that *all* students found themselves in this position.
1/
(If you'd like an unrolled version of this thread to read or share, here's a link to it on pluralistic.net, my surveillance-free, ad-free, tracker-free blog:)
This could have prompted educators to reconsider the use of high-stakes tests. After all, high-stakes testing has well-understood limitations in pedagogy, and organizes education around a highly artificial ritual completely unlike the rest of scholarly *and* industrial life.
3/
I've been paying close attention to @RepThomasMassie during the #ACCESSAct markup and I can't figure out his point. He correctly observes that proprietary standards are anticompetitive, but opposes the gold standard for open standards, namely, an IPR policy requiring licensing
@RepThomasMassie has described himself as a software developer, but it really feels like he is way, way out of his depth on standardization. Has he ever participated in an SDO. Not being able to distinguish between "interop" and "common vuln" is a pretty tyro error.
It's stuff like this that makes people assume that lawmakers are incapable of understanding - and thus regulating - technology. @RepThomasMassie really needs to get up to speed on how standards work.