And these failures are not the kinds of failures you'd get with adequate code control in place.
-
-
I've got 5 more reports to process. Meatball cat is helping me power through.pic.twitter.com/UQPLnsmEYh
-
If you code in a backdoor, and then put /* THIS IS A BACKDOOR */ good news you have a 90% chance of succeedingpic.twitter.com/GBQgpM9PT4
-
-
I'm taking photos of my screen with my phone because it's 1000x faster than dealing with screenshots. Sorry.
-
As a reminder in this thread, these standards are *voluntarily* adhered to and compliance is only required in a handful of states.
-
I'm wrapping this thread up. I've put my summary on Github:https://github.com/Gorcenski/voting-machines …
-
My summaries are very brief, but for simplicity I also copied the public records into the repo. Or download them at http://eac.gov
-
I also added a non-technical summary as to why this is concerning.
-
This thread, btw, thanks to
@Slestac who pointed me to the data source.
-
Waking this one up briefly to add this screenshot from a Glassdoor review of ES&Spic.twitter.com/DuCGEfA17Y
-
And a review froma Lead Software Engineer for the company that did the majority of the cert tests.pic.twitter.com/GTjQQEqNle
- 3 more replies
New conversation -
-
-
I guess code integrity of individual files, + potential to link to a particular dev who can't "disown" a change. no?
- 1 more reply
New conversation -
-
-
yes,
@a16z, why would u do that?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
what if someone breaks in, modifies the source code, compiles their own build, distributes the software, provides 24/7 suppo
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.