LogFAQs > #947497371

LurkerFAQs, Active DB, DB1, DB2, DB3, DB4, DB5, DB6, Database 7 ( 07.18.2020-02.18.2021 ), DB8, DB9, DB10, DB11, DB12, Clear
Topic List
Page List: 1
TopicPolitics Containment Topic 346: One Q Over the Coup Coup's Nest
Wanglicious
11/22/20 11:02:49 PM
#348:


masterplum posted...
The goal is to get the result faster. Look at nevada this year for example that went days without updates, or some of the house district races that took weeks.

In assembly lines they hire shifts for example. If money was no issue you easily could have counting 24 hours a day with 3 shifts of workers. I'm not saying we take it that far, but I agree with the premise that if we were willing to pay more we wouldn't have such a long delay

faster in what way? i see two ways you can mean that.
1) "faster" from getting the vote to counting the vote.
2) "faster" from having the results posted.

dunno if there's other options but i'm generally working with that framework.
for both the easiest answer would be extending the time you can vote, having different ways you can vote. like if you want the overall, long term objective to be accurate vote count in 24 hours i can respect that. but there's a lot that has to change to reach that point and with the level we're at now or the level we'll be at in 4 years, it's an impossible ask. the fingerprint database route would be the best one for this.

the two aren't the same either, the former would allow absentee ballots much easier than the latter.

---
"Maybe it's a tentacle, molesting the planet itself. - Aschen Brodel.
... Copied to Clipboard!
Topic List
Page List: 1