1
I've become increasingly concerned about voting interference and was surprised to hear there's no national repository for reporting difficulty in voting.
There's 866-OUR-VOTE, but that's voice only. FairFight.org has a Google spreadsheet. So far I haven't really found a website dedicated to collecting reports of disenfranchisement.
I bought CantVote.org and would like to develop a simple PWA for submitting reports of voting-related shadiness or outright interference.
This would obviously be ripe for abuse, but my main goal is to log the reports and worry about filtering out fake data later.
People would be reasonably suspicious, so the code would be open-source. My current plan is to dump submissions into an S3 bucket or DynamoDB and find low-cost ways to share anonymized data afterward. Come join https://github.com/CantVote if the tech side of this project interests you.
But before getting started, does anyone know of any:
1. Similar efforts? 2. Obvious dealbreakers? 3. Good people to contact?
Thank you, fellow patriots.
I expect that we'll keep the components in a separate npm package, and in the case of any major changes to the component library, just manually synchronize the deployment of both sites.
To minimize the marketing dept's dependency on engineering, I'm thinking of using a headless WP installation to manage the content and pull it into React components dynamically. Ideally using SSR, or less-ideally loading the content using XHR.
Has anyone dealt with this type of setup before? Are there any obvious pitfalls, or best practices for keeping teams independent while keeping multiple sites in sync?