Thats ... pretty messed up.
[0]https://www.eff.org/files/2016/01/12/113_second_amended_comp...
477 karma · joined March 31, 2015
Thats ... pretty messed up.
[0]https://www.eff.org/files/2016/01/12/113_second_amended_comp...
If so, kind of makes you wonder what you really buy by adding the axolotl protocol. Thoughts?
Targeted towards international NGOs operating in rough areas, but works for other business too.
Not free though. Seems security comes at a premium.
One valid use, I think, could be around ensuring you don't pollute your backend with user data to avoid liability.
For example, if you wanted to use a distributed database in your backend and needed guarantees that when you delete data it is deleted everywhere at once, you could use JS crypto to do client-side encryption of the data and only have to delete the key to render the distributed data inert.
I heard about this through an article that was on HN a few weeks back (https://blog.balboa.io/yet-another.html)
Not really a new idea, I don't think, but not one that gets surfaced much when people talk about client-side crypto.
In my opinion, the onus is on the user to be responsible with their time, guarding their attention from competing interests. But we as developers can probably help out as well. One way might be giving people easy ways to opt out of notifications (or opt out by default).
I almost want to invent another category for bootstrapped startups that have access to large amounts of personal liquid assets.
Just think of the difference in strategic moves available to you if you have $1MM vs $10k to throw at a problem.
Having said that, I applaud his efforts to try things differently, and even agree with a lot of what is in there.
So much easier.
Yet so much harder.
But that's China ;)
The study makes a distinction between the 'big three' of Christianity, Islam, and Judaism, but anyone with even a cursory knowledge on the matter knows that there are sects and divisions within those overarching categories that are worlds apart.
I think what this study shows is that religious belief isn't necessary for moral behavior. But that's a question of epistemology, not a question of ontology. Said another way, people can be awesome people, but still lack a 'grounding in being' for their values.
Having said that, after navigating those waters for awhile, I enjoy dealing with a clear legal framework, laws that are more often than not applied uniformly, and a government that doesn't stifle the free exchange of ideas on the internet to such a point that you need a pretty beefy VPN solution just to do a Google search.
Just my opinion though, good to hear you have been successful in your work - good luck and keep on trucking!
In my experience it is becoming harder and harder to form relationships, and one of the factors seems to be our housing choices[1].
[0]http://journals.plos.org/plosmedicine/article?id=10.1371/jou...
[1]http://www.vox.com/2015/10/28/9622920/housing-adult-friendsh...
Employers have a disproportionate amount of influence over the lives of the people under their employ. This should carry with it a sense of duty, or responsibility, to the well-being of their fellow human.
Got to hand it to them, its actually a pretty cool attack vector.
If you build a "perfectly secure" piece of software, but it takes a very high level of skill to use it, your users will use something else that is easier to use, but less secure. And then how has your ideologically perfect piece of software helped improve their security?
If you make tradeoffs for usability, you will raise the bar because people will actually use what you make.
To make matters worse, your DropBox syncing software will automatically cryptolocker your files stored in the cloud.
So true. We moved away from Mongo for very similar reasons, but we moved to Cassandra instead of Postgres only with great trepidation (we were worried about scalability issues).
Only time will tell if this was a good move or if we should have just done as you did. Good luck out there!
The takeaway: "All this points to new top-management imperatives: keep an eye on the speed and direction of automation, for starters, and then determine where, when, and how much to invest in automation."
Honest question: does this model apply when your product can't at any point be, for lack of a better word, half-baked?
Say you're making a security product or working on control code for rocket thrusters.