Comments by "Arthur Mosel" (@arthurmosel808) on "Forbes Breaking News" channel.

  1. 1
  2. 1
  3. 1
  4. 1
  5. 1
  6. 1
  7. 1
  8.  @larry6601  Ranked choice and open primaries are abominations. The open primary means that the top two or three vote getters run against each for the office. Which means in California, no Republicans or Conservative stands a chance at state wide office. You run enough candidates in the primary dilute the vote and there usually the choice is between the two most left candidates. As electronic voting, the weak point is how politically lopsided that we find both programmers and firms are. Your basic assumption is that there will be enough review to insure an algorithm that adds, subtracts or alters votes can't be inserted into the software without being discovered. My position is that it can be done. Not strictly analogous, but we have seen the social media copies place there thumbs on the scales of an election by either suppressing news or hyping it for their preferred candidate. Run this scenario in your head. Company X is run by a firm believer in socialism (or venal enough to be bribed or weak enough to submit to threats). He/she hires socialist believers for whatever reason to write or update election software; and they modify it to alter the vote count in someway. This altered software is than provided to voting districts or states who support the cause. An alternative is sending people from the company to update software immediately before an election. In districts supporting their side no one will be allowed to challenge the election and the company will refuse to allow the software to be checked. This defeats all of your safeguards because from the company to the user all are in on the scheme. In other words, a computer can only do what its software tells it to do. Hacking the program while running may be impossible, but corrupting the software is very doable if a group desires it.
    1
  9.  @larry6601  I am no professional programmer, but on several occassions I have worked closely with them in developing programs/record systems that I needed. 8n at least one case, I caught the assumption that the programmer made that turned an existing data base into garbage when forgot that those entering the data did not all finish an entry the same (some added a space). The affect was cumulative, throwing each next entry off by an additional amount, the NRC wasn't happy with the results and it rolled down hill. I have done some simple programming myself after I bought my first computer back in 1982. So I do brave great respect for those with the patience to work at it. My work involved command and control, planning for, responding to, and recovering from various emergencies and disasters (man-made or natural). As a result I have a strong belief that a certain percentage (usually small thank God) are totally unethical, will cut corners or try to cheat. So, I am routinely assume the worst and hope for the best. If you've planned on the worst, anything less is easy. Also effecting my beliefs is the fact that I have spent a great deal of my military time around special ops and electronic security units. Some thing that makes it easy to accept that there are people out there ours and theirs who are willing and able to do not so wonderful things. Not bad when it happens to an enemy, not so much when your side is on the receiving end. Something to remember is that the system used in Arizona (and some other states in 2020) fought releasing information on their system because it was proprietary, not an open system. It was in Arizona where someone from the company made a software upgrade after the machines were certified according to some sources. We'll never know for sure because the court cases never got to discovery. So, to me, these were two red flags that should have been checked and resolved. If you have nothing to hide, why hide.
    1
  10. 1
  11. 1
  12. 1
  13. 1
  14. 1
  15. 1
  16. 1
  17. 1
  18. 1
  19. 1
  20. 1
  21. 1
  22. 1
  23. 1
  24. 1
  25. 1
  26. 1
  27. 1
  28. 1
  29. 1
  30. 1
  31. 1
  32. 1
  33. 1
  34. 1
  35. 1
  36. 1
  37. 1
  38. 1
  39. 1
  40. 1