Would this new feature would reward users any more than the existing karma/gilding mechanism? I am skeptical that the typical Reddit user would have even have a cryptocurrency wallet.
188 karma · joined March 15, 2017
Would this new feature would reward users any more than the existing karma/gilding mechanism? I am skeptical that the typical Reddit user would have even have a cryptocurrency wallet.
I like this solver, which uses a dynamic programming/search approach to find solutions. https://github.com/SomeKittens/calculords-solver
I design my current web apps to work using serverless functions https://serverless.com/ This ensures that if my applications become popular, I will not have to do additional infrastructure work to scale. I use a cloud provider managed database (AWS DynamoDB, RDS for Postgresql) so I don't need to worry about managing that either.
There is a steep learning curve! A quick Google search shows that Rust serverless is in its infancy (https://github.com/softprops/serverless-rust). Also, if you need to have bi-directional communication using WebSockets (or something comparable), the options you have to work with are limited (AWS AppSync is what I am currently struggling with)
That being said, it has been an extremely challenging and rewarding experience, migrating my personal projects.
> All in all, while the client and backend code are vulnerable to some issues, all of the problems can be easily fixed without a lot of effort. In that sense, Cure53 believes these items of the Bitwarden scope to be fully capable of reaching the desired standards of security in a rather short time. To reiterate, the results of this autumn 2018 assessment are positive for the client and code.
Wondering how they will address the current cryptographic scheme though.
https://www.cockroachlabs.com/docs/stable/install-client-dri...
That being said, I am really excited to try this out. 2.0 adding JSON support is what converted me to try this out for a project.
Is anyone else seeing this? It needs a bit more polish before I could use it for encrypted collaborative editing.
I think if your primary repo that's hooked into CI goes down, you're still SOL. Having your own repo just enables you to continue local development among your team.
I don't see any great solution, other than making your app distributed to begin with and doing your build/deploy manually.
As a complete aside, I've fantasized about deploying to all cloud vendors (Azure/GCE/AWS/Heroku/DigitalOcean/misc.) each with their own specific build/deploy and having persistent state shared with something like CockroachDB. Having some load balancer managing state between all instances. Taking advantage of the free/basic tiers provided by all of the vendors.
I've configured my push such that it will deploy to both Github and on my Gogs meaning that I always have an up to date repository in two places.
https://github.com/gogits/gogs (if you're interested in setting up your own)
https://stackoverflow.com/questions/14290113/git-pushing-cod... (push to two remotes)
You don't have to use just BitBucket, or rely entirely on your self hosted git service.