4,623 karma · joined June 22, 2011
[ my public key: https://keybase.io/danielcompton; my proof: https://keybase.io/danielcompton/sigs/HVrj42Dnw9wOvE9nvNSySMmkoacaCW11OZr0ead1iJQ ]
Those are much easier to sell to, because there is a much smaller amount of buy-in needed from the organisation as a whole. Because the stakes are so much lower than in an enterprise-wide deal, an MVP may be perfectly acceptable to your customers.
> Anyone know of any other language communities with similar foundations?
We got the idea from Ruby Together - https://rubytogether.org.
> the Clojure community, from my understanding, tends to concentrate around the same tools.
I'd say relative to it's size the Clojure community is quite diverse in it's tooling and library ecosystem, compared to say, Ruby. Because of the dispersion of projects and interest, we survey our members quarterly and pick projects based on the survey results.
I searched on https://dotmesh.com for "security" and "encryption", searched Google for "site:dotmesh.com security", and tried going to http://dotmesh.com/security, but got nothing for all three.
1. The first thing I thought when I saw this is "How is this secure?". You're wanting to store the most sensitive information a business has - credentials + production DB. I took a look around the site + Google and couldn't find anything about security. Client side encryption of data seems like it would be good to make people comfortable with storing their data at dothub. I'm not sure if there is any use case for dothub having unencrypted data (at least not yet)?
2. "Application states" is quite a vague term, when I saw that I thought it was referring to capturing the state of a running process. "A git-like CLI for application states" is not a very compelling pitch. As others have noted, for all but the most masochistic of users, "a git-like CLI" is a negative point.
The benefit you're offering is "Snapshot production data to be able to replay in development" and "Snapshot failed CI builds to debug later". I'd recommend putting those up-front and in bold. A more compelling tagline (to me) is "Dotmesh - version control and snapshots for your production data".
It would be great if Stripe could offer incorporation in another company with fewer unknown implications, or hire a lawyer to write an opinion for the implications of using Stripe Atlas in every country in the world.
> Two hackers had stolen data about the company’s riders and drivers — including phone numbers, email addresses and names — from a third-party server, putting the personal data of more than 57 million people at risk. The hackers approached Uber and demanded $100,000 to delete their copy of the data [...].
> Uber acquiesced to the demands. Under the orders of Travis Kalanick, who was then its chief executive, and Joe Sullivan, the chief security officer, the company paid the ransom.
> Then Uber went further. The company tracked down the hackers and pushed them to sign nondisclosure agreements [...]. To further conceal the damage, Uber executives also made it appear as if the payout had been part of a “bug bounty” [...].
The obvious question you're having here is "Won't that be slower?" and the answer is yes it will necessarily be slower due to physics. However on the Google Cloud public Slack (https://gcp-slack.appspot.com), it was mentioned that networking for zone to zone is similar to machine to machine, so this is likely to not be an issue.
If the primary instance fails (either because of machine/rack/zone failure), it will stop sending heartbeats and the failover will try to mount the regional disk and become the primary. Because all writes are synchronously replicated, no data loss occurs, although your service will be unavailable until failover completes.
> Their mention of replication makes it sound like they are behaving similarly to RDS' Aurora instances
I don't think anything this fancy is happening, to my understanding it is just a disk that happens to be synchronously replicated to two zones. Under the covers they may be doing some smart copy-on-write stuff, but that isn't exposed to the user.
From the sound of the blog post they plan to unveil regional disks sometime soon, so we may get more info then.
You can do this with CAA records today, to restrict which CAs can issue certificates for your domain.
Why is this a problem? If you need to make a change to improve scalability, it doesn't seem unreasonable to ask contributors to follow code and performance guidelines.
Apple likely built Face ID to be more accurate than claimed. This is similar to what they did with waterproofing the iPhones, where for one or two years they were built to a higher waterproofing level than they were marketed as.
Imagine Apple's suppliers were building to a 1:2,000,000 accuracy rate, and they were told they could drop the accuracy to 1:1,200,000 accuracy rate. Bloomberg is right that Apple has allowed the suppliers to reduced accuracy, while Apple's statement that there continues to be a one in a million probability of a random person unlocking your phone is also true.
This is an uncharitable reading of the situation though, and I'm mostly inclined to take Apple at their word on this.
This is the core idea behind Peloton, a research database from CMU: http://pelotondb.io. Andy Pavlo has a really interesting, and entertaining talk about it https://www.youtube.com/watch?v=mzMnyYdO8jk.