3 ms·
I'm not sure you understand what a Congressional campaign is like. Outside a few really rich districts, you'll have the candidate, a campaign manager, a media p
by idlewords 9y ago
I'm not sure you understand what a Congressional campaign is like. Outside a few really rich districts, you'll have the candidate, a campaign manager, a media person, someone in charge of fundraising, and people to manage volunteers. Using social media is routine, and everything that doesn't involve money is connected to people's regular accounts.
If you're lucky, the campaign staff will have an analytics person, and they (or the most technically adept member of the campaign) become de facto tech support for everyone else.
Many of the people the campaign staff need to work with will be volunteers who are already task saturated on campaigning, and have no capacity to learn whatever security processes you have in place.
The overriding priorities of the campaign will be fundraising and outreach. Everything else will be subordinate, and anything that makes those two things harder will be ignored.
I don't know what situation your comments are appropriate for, but they will not work for the people we are trying to protect.
- fencepost 9y agoThanks, I didn't realize how small most campaigns were, and I can see why it wouldn't be something where a third-party could set up to provide the services - way too cyclical.
- idlewords 9y agoThe Democratic party apparatus steps in to some extent, but only after the primaries, and they're not too clueful, either. The guide here is an attempt to see how much we can bring up the level of security on a campaign without IT infrastructure. It's meant to be the "wash hands, boil water" of security advice, not an ultimate security guide. So thanks for understanding the context!