konklone
Joined 14 years ago
Joined 14 years ago
I lead the security and safety team for Wikipedia, at the Wikimedia Foundation. I’m hiring a product manager to lead our security roadmap and steer the priorities of our security engineering team.
It’s a high-pace, shipping-heavy time for the whole project right now, as we are dedicating ourselves to surviving all the ways AI is messing with us and the internet, and getting to the other side of it. I joined myself about a year ago, and have found it to be a great time and place to swing big and surprise people.
This is a PM role and PM background is certainly helpful, but it’s not strictly required (everyone has the first PM job at some point). A technical background and security expertise are a must for this role, so we’re also open to people in engineering roles, who have demonstrated PM-relevant skills and are interested in making a pivot.
You can apply at https://job-boards.greenhouse.io/wikimedia/jobs/8140060?gh_s... - we don’t auto-filter based on AI or anything like that, I will personally see your resume.
In those 5 years, HTTPS has gone from being the minority of traffic to being ~90% of the connections observed by most Chrome clients (scroll down a few graphs for the Chrome-observed one): https://transparencyreport.google.com/https/overview
Firefox has reported similar numbers. It's now more common for new web features to require HTTPS when they are introduced, to avoid developing HTTP sites as dependencies: https://blog.mozilla.org/security/2018/01/15/secure-contexts...
That doesn't mean that HTTP is banned, but given the magnitude of the change and the size of the web, I think it's fair to say that it's being deprecated.
More practically, anyone who wanted to build a product (or a government process) on intercepting or modifying people's unencrypted web traffic would find their dataset to be an order of magnitude smaller, and orders of magnitude less useful (since so much of the remaining HTTP traffic is in the long tail of small/older sites).
But to answer your other question, as part of the Department of Commerce, a "CFO Act" agency, USPTO would not be exempt.
Also, the DoD CIO has had, since ~2003, this excellent FAQ supporting open source:
http://dodcio.defense.gov/Open-Source-Software-FAQ/
But as people on this thread and elsewhere will tell you, that hasn't resulted in widespread support at DoD for open source.
I currently work for as a technology advisor to the General Services Administration. I help 18F and other technology programs at GSA build open, secure technology inside the US federal government. Before that, I spent 5 years with the Sunlight Foundation working on open data infrastructure and policy.
[ my public key: https://keybase.io/konklone; my proof: https://keybase.io/konklone/sigs/9Iwmw27600DiYlztkLB1x2b2vIGIiPJ6DpXE76ekFkY ]