148 karma · joined March 5, 2015
+ full-stack developer (python, postgres, modern js/react, java ee)
+ devops(docker, ci, centos, backup, monitoring)
Over time you will recognize that the same patterns occur in different projects and even languages.
For the beginning I'd suggest to stay away from frameworks that do too much magic. If you are interested in web, start with Flask, not Spring.
I rember reading a blog post about crate facing data loss in some cases:
https://aphyr.com/posts/332-jepsen-crate-0-54-9-version-dive...
Is this still an issue?
Attackers will probably have a lot of computational resources (think of AWS, botnets, GPU computations), while typical users don't (mobile phones).
I haven't had time yet to look into the IPFS details yet, but thanks for the reference.
Some years ago in the university I wrote a paper about that in a seminar to summarize the possible counter meassures, but from what I remember, there were no really practical solutions. I think the most promising one is the use of a centralized certificate authority, which reintroduces some of the problems p2p wanted to solve. Does anyone know if new ideas have come up in the last years?