They open sourced the tool to do it- https://kythe.io - but I think it would be a pain to make it work for anything like GitHub that supports arbitrary languages and build systems with untrusted code
626 karma · joined October 11, 2012
They open sourced the tool to do it- https://kythe.io - but I think it would be a pain to make it work for anything like GitHub that supports arbitrary languages and build systems with untrusted code
Since it tracks everyone in the area, there's major privacy concerns about how they're used, and police have been caught repeatedly lying about their use. To the point that if the defense in a case discovered police had used a Stingray to identify their client and challenged it, the police would drop the case rather than letting anything about the Stingray enter the public record. https://arstechnica.com/tech-policy/2015/04/fbi-would-rather...
1. The author died more than 70 years ago or it was owned by a corporation and it's been 95 years since publication
2. It was written prior to 1989 and did not include a copyright notice.
3. It was written by the government
4. The author explicitly released it into the public domain
1 and 2 probably don't cover much code on the Internet. So unless it's a government repository and/or explicitly marked with a public domain notice, you can probably assume it's copyrighted.
If, as you were implying, U3 was hiding extra unemployment right now but U6 was more accurate, then it wouldn't be so closely tracking U3.
Using even the broadest measure of unemployment[1], numbers are back down where they were before Covid. The labor force participation rate is still down though[2] which means that about 2% of US adults aren't looking to go back to work at all- many of them are likely now retired, students, or stay-at-home parents.
[1] https://fred.stlouisfed.org/series/U6RATE [2] https://fred.stlouisfed.org/series/CIVPART
But besides that, the federal government already has an SSO provider that supports smart cards, U2F, and TOTP. I suspect many agencies will choose to adopt that rather than trying to roll their own SMS auth.
https://www.technologyreview.com/2019/01/21/137783/algorithm...
Of course there are places where global state is unavoidable (even if it's just "the filesystem"), but by confining your global state to a small corner of your codebase and having the rest of the code interact with this component instead of touching all the global variables directly, you can reduce the number of potential problem spots.