365 karma · joined October 2, 2011
(formerly) andrey@heapanalytics.com andrey@desmos.com andrey@humblebundle.com anfedorov@google.com andrey@invitemedia.com andrey@gamechanger.io andrey@conductor.com
At least in SF in the past 5 years, Comcast seems to have upgraded 100Mbps connections to 1Gbps connections. Not sure whether that translates to a bigger shared pipe for the city as a whole, but it certainly looks like a good amount of improvement in $:bits, at least in comparison with $:sqFt.
We're bringing memberships, certificates, licenses, and credentials into the connected era via a platform built on Scala, GraphQL, and React.
More info: https://angel.co/sigma-certified/jobs/130819-software-engine...
contact eng-apply@sig.ma or andrey@sig.ma with questions
The ToS and Privacy Policy of an analytics company discloses what the that company may do with their client's users' data, not what the client can do with their own users' data.
There's another Privacy Policy between the client and the user where the client discloses what they may and may not do with user data and the user decides whether to become / remain a user.
There are also laws which dictate the data handling further on behalf of large groups of users, e.g. GDRP for EU citizens and, on this side of the pond, interesting Supreme Court cases being decided about what kind of data users could have property rights to: https://en.wikipedia.org/wiki/Carpenter_v._United_States
Thanks for the link! This kind of project is really exciting, so I'm sorry if the nitpicking detracts any from your awesome aspirations :-)
> Today we are proud to announce the Blockstack browser, which allows developers everywhere to access a whole new internet.
reminded me of then-Senator Ted Stevens' take on net neutrality
> Ten movies streaming across that, that Internet, and what happens to your own personal Internet? I just the other day got... an Internet was sent by my staff at 10 o'clock in the morning on Friday. I got it yesterday [Tuesday]. Why? Because it got tangled up with all these things going on the Internet commercially.
In other words, what a load of hot air! Looking forward to their $50M seed round.
And they still can't fix it in 7 days? Well, then they have to shape up or be replaced by a competitor who can. It's harsh, but customers benefit.
When there are known exploits attacks against users, giving a short time to get out quick patches to trusted software vendors makes a lot of sense, but I don't see a good reason for giving more than 24-48 hours before public disclosure.
This is not a "wait until the next release cadence" kind of issue, but more like a "scramble all jets and work through the weekend" kind. If I were a Windows user, I don't think there's anything else I'd want MS to work on over fixing an actively exploited remote priv escalation vuln.
Google's security team worked through their Christmas vacations when they had an attack awhile back. To give other companies 7 days to patch their software is really quite generous.
It's good to encrypt things, but I wouldn't be too surprised if it were possible for folks to issue bad certs via them, as well.
Remote: Yes
Willing to relocate: Yes
Technologies: GAE, AWS, Python, JavaScript, Rust, Swift, Go, etc.
Résumé/CV: https://anfedorov.com/resum%C3%A9.pdf
Email: me@anfedorov.com
I'm an end-to-end developer with a variety of skills, interests, and passions. Interested in contracting as well as considering full time opportunities.
The ending is the clearest part:
Although the Archivist has independent legal authority to determine the status of federal records under the Presidential and Federal Records Act Amendments of 2014, he remains an executive branch official and he is not politically autonomous. In the face of FOIA litigation, which takes precedence as a practical matter, it actually is “routine” (or at least unsurprising) for the Archivist to defer to the Justice Department and to abstain from unilateral action.
If the ongoing FOIA litigation ultimately led to a determination that the Senate report is a “record” for purposes of FOIA, then it would be easy for the Archivist to concur. If not, then it would be more difficult, but not altogether impossible, for the Archivist to conclude that the report is nevertheless a federal record. “The determination of record status under the FRA and the Freedom of Information Act (FOIA), while not identical, is similar,” the Archivist wrote.
In any event, while an immediate resolution of this dispute is foreclosed by the Archivist’s refusal to intervene, the larger question of the status of the Senate report as a federal record remains open.
Legal technicalities aside, it would be astonishing if the full Senate Committee report were not preserved for posterity one way or another, and eventually published. Even if it is not the last word on post-9/11 detention and interrogation, and even if not every word of it turns out to be true and correct, the Committee report has already become central to public discourse on the subject. If it became possible to erase it from the historical record in some kind of Stalinesque act of suppression, then we would all have bigger problems to worry about.