Who Added an Algorithm to New York State’s Voter Registration Roll, and Why?

[livingston]

Who Added an Algorithm to New York State’s Voter Registration Roll, and Why?​

Dr. Andrew Paquette, who serves as research director of the all-volunteer citizens’ group New York Citizens Audit (NYCA), has proven that New York state’s voter registration roll now contains an algorithm designed to facilitate election fraud.

One must understand how voter registration data works to appreciate just how serious this is. All registration data is predicated on algorithms, which are basically equations added into the registration in chronological sequence to transform a voter identification number (“Voter ID No.”) into a code.
In an honest system, the voter who registers first gets Voter ID No. 1, the second voter to register gets Voter ID No. 2, etc. In other words, there’s a direct correlation between the date order of registration and the ID No., with the ID Nos. increasing by increments of one.
However, Dr. Paquette has discovered a different algorithm. This one changes the Voter ID No. assignment so that the ID Nos. no longer increase by increments of one that are tied to the order in which voters register. Instead, the ID Nos. appear scrambled, with no linear sequential order.
“The algorithm that is still added to the New York state voter registration database is a complex mathematically driven cryptographic scheme that involves National Security Agency-level of complexity,” claims Dr. Paquette.

Who Added an Algorithm to New York State’s Voter Registration Roll, and Why? | The Gateway Pundit | by Guest Contributor

Guest post by Jerome Corsi – originally published at American Thinker – republished with permission.

www.thegatewaypundit.com

 

[FP1201]

Who Added an Algorithm to New York State’s Voter Registration Roll, and Why?​

Dr. Andrew Paquette, who serves as research director of the all-volunteer citizens’ group New York Citizens Audit (NYCA), has proven that New York state’s voter registration roll now contains an algorithm designed to facilitate election fraud.

One must understand how voter registration data works to appreciate just how serious this is. All registration data is predicated on algorithms, which are basically equations added into the registration in chronological sequence to transform a voter identification number (“Voter ID No.”) into a code.
In an honest system, the voter who registers first gets Voter ID No. 1, the second voter to register gets Voter ID No. 2, etc. In other words, there’s a direct correlation between the date order of registration and the ID No., with the ID Nos. increasing by increments of one.
However, Dr. Paquette has discovered a different algorithm. This one changes the Voter ID No. assignment so that the ID Nos. no longer increase by increments of one that are tied to the order in which voters register. Instead, the ID Nos. appear scrambled, with no linear sequential order.
“The algorithm that is still added to the New York state voter registration database is a complex mathematically driven cryptographic scheme that involves National Security Agency-level of complexity,” claims Dr. Paquette.

Who Added an Algorithm to New York State’s Voter Registration Roll, and Why? | The Gateway Pundit | by Guest Contributor

Guest post by Jerome Corsi – originally published at American Thinker – republished with permission.

www.thegatewaypundit.com

Anticipated statement from the DNC/Legislature: " we have been made aware of concerns, and will conduct an in-house investigate after the November Elections...we are fully confident in the system."

 

[TEOTWAWKI inc.]

It can't be that complicated. It's just pairing their voter ID # to their newcomer ID #.

 

[That_FNG]

Who? Democrats duh. Next question.

 

[Grimscale]

Theoretically it shouldn't matter what voter id # they get.
As long as they are vetted at the time of registration to verify they are 1) ALIVE, 2) a U.S. Citizen, and 3) Live where they say they live.

I propose that there should be extensive universal background checks made at the time of voter registration and everyone must obtain a License To Vote which must be presented at the time of voting.
To obtain said License the applicant must be able to supply usernames/passwords of any social media accounts they have, provide five character references that are not direct relatives and are from the same County the person lives in, and demonstrate in a "test vote" scenario that they are capable of coloring within the lines of the tiny little dot provided on a sample ballot. Applicant must also pay a $500 application fee and blow the presiding judge.

 

[SonOfSun]

In an honest system, the voter who registers first gets Voter ID No. 1, the second voter to register gets Voter ID No. 2, etc. In other words, there’s a direct correlation between the date order of registration and the ID No., with the ID Nos. increasing by increments of one.

Umm, no. As someone who professionally works with a lot of data that's not always the way to do things. Sounds like this Dr doesn't know shit about this topic - if he did it wouldn't alarm him. There are plenty of reasons not to use a sequential numbering system in a database. An efficient database schema may not need an incremental counter field when coded data may just be more efficient.

Want a real life example you've probably dealt with? Here:



A VIN is an example of a coded record. Why have data fields and associated size and slowness for all of the data when you can combine it into one relevant item? Are VIN numbers "fraud"? The mere existence of non sequential numbers doesn't in any way, shape, or form mean it's fraudulent.

@libertysnake

 

[FP1201]

Theoretically it shouldn't matter what voter id # they get.
As long as they are vetted at the time of registration to verify they are 1) ALIVE, 2) a U.S. Citizen, and 3) Live where they say they live.

I propose that there should be extensive universal background checks made at the time of voter registration and everyone must obtain a License To Vote which must be presented at the time of voting.
To obtain said License the applicant must be able to supply usernames/passwords of any social media accounts they have, provide five character references that are not direct relatives and are from the same County the person lives in, and demonstrate in a "test vote" scenario that they are capable of coloring within the lines of the tiny little dot provided on a sample ballot. Applicant must also pay a $500 application fee and blow the presiding judge.

democrats would say this is fine for Republican/Conservative Voters, but raciest for them.

 

[libertysnake]

Umm, no. As someone who professionally works with a lot of data that's not always the way to do things. Sounds like this Dr doesn't know shit about this topic - if he did it wouldn't alarm him. There are plenty of reasons not to use a sequential numbering system in a database. An efficient database schema may not need an incremental counter field when coded data may just be more efficient.

Want a real life example you've probably dealt with? Here:

View attachment 238255

A VIN is an example of a coded record. Why have data fields and associated size and slowness for all of the data when you can combine it into one relevant item? Are VIN numbers "fraud"? The mere existence of non sequential numbers doesn't in any way, shape, or form mean it's fraudulent.

@libertysnake

It'd be more of a security risk to number it sequentially, actually. Think just practically. If voters start with 1+, then it's easy to predict which voter number is most likely easy to use for fraud alone. Just pick a small number. Person is likely dead if you wanted to commit fraud, vs if you simply generated a voter hash based on location + date + maybe their social last four digits.

Less predictable keys are less exploitable.

It's easier to detect fraud too. If you know how the voter IDs are hashed, then you reverse check using the sensitive location or something used to form the voter ID hash and detect if someone illegal is using it across the country in a location that makes no sense. Or figure out the voter would be 150 years old and it's obviously stolen using an algorithm. If you know how the hash is formed, you hide what the gov knows about the voter to someone who stole the hashed voter ID.

Anyway, just thinking out loud why.

 

[SonOfSun]

It'd be more of a security risk to number it sequentially, actually. Think just practically. If voters start with 1+, then it's easy to predict which voter number is most likely easy to use for fraud alone. Just pick a small number. Person is likely dead if you wanted to commit fraud, vs if you simply generated a voter hash based on location + date + maybe their social last four digits.

Less predictable keys are less exploitable.

It's easier to detect fraud too. If you know how the voter IDs are hashed, then you reverse check using the sensitive location or something used to form the voter ID hash and detect if someone illegal is using it across the country in a location that makes no sense. Or figure out the voter would be 150 years old and it's obviously stolen using an algorithm. If you know how the hash is formed, you hide what the gov knows about the voter to someone who stole the hashed voter ID.

Anyway, just thinking out loud why.

I was more or less thinking the same thing for security. If I was to design it the deobfuscated voter ID would have a VIN like prefix with voter properties coded like date of registration, county of registration, etc. Those properties could be used for security checks, etc.

Bottom line, IMO, if the text of the article is accurate, this "Dr" doesn't know much about database design and his analysis is bogus at best.