820 karma · joined December 1, 2015
While I never post a comment on an article before reading it, I almost always read the comments before reading the article to avoid click baits. An brief one-line summary that serves the same role as an abstract would eliminate the need to read the comments first.
It might even help eliminate clickbaity titles in technical articles altogether.
What about "technical" users?
International domain names will never be used if browser and website support remains as horrible as it currently is.
Conductive meshes work as well provided that the holes are small enough.
At this rate, it'll become another html spec.
That said, I understand that the author added these in an attempt to make the article more enjoyable. I also appreciate the fact that some readers will indeed find these additions enjoyable. To each his own.
I bet the lack of IP is what will give china and other countries the edge in the long run.
It's also one of the features I sorely miss when using Rust. Luckily, Rust's stdlib is starting to tend towards being more practical with recent additions like system time.
No government would buy unreliable weapons.
I tend to call software that tries to trick users into doing things they explicitly do not want to do malware, but that's just me.
I remain unconvinced.
How so?
The author is voicing criticism that a lot of people (including myself) have with regards to the current state of software distribution security.
Furthermore, his survey of the top distributions is interesting for people who take their security seriously.
Seeing that there is no way for me to verify the authenticity of the signing keys (short of visiting canonical in person), every bit of security helps.
If you're serious: Why not make use of existing infrastructure (current courts, laws, etc) rather than reimplementing all that again on top of ethereum? Also, what prevents this new layer from becoming as corrupt and bureaucratic as the one we currently have in place?
While it doesn't address all issues, it does go a long way towards mitigating them. I must also take this opportunity to commend you guys on how transport security is handled; the fact that traffic remains secured end-to-end using a host certificate rather than terminating security at the proxy puts sandstorm well ahead of anything else in this space.
Secure, easy, and open source. I'm sold as both a developer and an end-user.
This level of polish might just be what it takes to get the masses to host their own digital services. I'm strongly considering setting a sandstorm server up for my family.
One question promptly and prominently pops to mind: Given the focus on non-technical users, How does sandstorm mitigate issues that are caused by NAT and NAT traversal?
I don't care much for the game, but details of why the servers weren't (aren't?) able to handle the traffic interests me immensely.
ON a more serious note, I always use http://example.com. Being reserved and maintained by the IANA for documentation and testing, it's the most stable site I can think of.
This surprised me for a different reason: I was under the impression that effective security bit size does not scale linearly with bit lengths in RSA, and that key size would need to be 16,000-bits long for a comfortable safety margin (a size not practical and not supported by RSA).
Are there any practical reasons why one shouldn't use epileptic-curve based crypto?
The reason I, and I suspect many others, avoid these types of services is the risk of this information being inherited or possessed by an entity that would use this information in ways to which I do would not consent nor approve. This information would not only affect me personally, but also my children.
Germans are more privacy-aware than most for a good reason. I dread a future where an evil government gets a hold of this data and the technology to effectively use it.
To elaborate on the parent's example: a particularly bad bug in a library depended on by a set of programs might not cause much of problem if you build and deploy this software yourself.
However, it would be a more significant endeavor on both the distribution's part (recompile, repackage, sign-off, and release every program in the set), and on the user's part who has to download the large binaries each time a dependency is updated rather than a small library. This problem is further exacerbated by the npm-like dependency graphs rust programs tend to end up with. Take servo as an extreme example of what these graphs might look like: https://web.archive.org/web/20160703132700/https://dirkjan.o...
Furthermore, I don't see how dynamic linking prevents the compiler from optimizing the resulting binaries. C libraries have been dynamically linked for decades without issue.
That said, the parent post was merely demonstrating that "morally right" or "best human rights" record is completely subjective.
In a democratic system, your notion of "right" and "wrong" is nonsensical and incorrect if it does not align with the majority, regardless of how "evil" or horrifying this may seem.
You either have democracy or you don't.