stacks-core

ing to do with gnunet or secushare on the moral level, they are really different beasts with different goals Firstly I’d argue that this is an opinion. But secondly I’d add that it is an ill-informed opinion. The Blockstack design means that users retain control of their data and their identity, and these cannot be taken from, nor weaponised against users. This is not merely a statement of intent [0], but am outcome of design [1]. > Marketing vs science, I believe this is adequately addressed by their white paper which I won’t attempt to summarise. [1] > social vs commercial, private vs libre The GNU philosophy is not about free as in beer but free as in libre. It is also not anathema to commercial use. The Blockstack core is licensed under the GPL v3, and all documentation is Creative Commons licensed. I’d argue that a worse denial of freedom (than software freedom) is having your data and identity held hostage ie. denial of the freedom to move or remove my data and identity. Holding your digital self hostage is eminently possible by a cloud service even if it’s built entirely on open source software, while not possible for a Blockstack dapp even if it were closed source. The core philosophy of Blockstack is “can’t be evil”. > if you're not seeing the objective difference here then you're not trying An opinion. I could counter that you didn’t try very hard to see the similarities. [0] https://github.com/blockstack/blockstack-core/blob/master/RE... [1] https://blockstack.org/docs/how-blockstack-works [2] https://github.com/blockstack/blockstack-core/blob/master/RE...

like libsodium is used, whether you’re using AES-GCM or ChaCha-Poly1305, etc. I’m looking for an architecture diagram to understand which of these questions is coherent. Is key derivation used? Under which algorithm? I’m assuming your IDs are SHA-256 hashes, but is that correct? I don’t know. Basically, aside from saying there are “ECDSA private keys” in passing, how precisely does encryption, key exchange and digital signing work? Maybe I missed a pretty obvious explanation in here - I was reading quickly (though pointedly). However, if that’s the case then mea culpa, and it should be easy to rectify by pointing out where exactly I missed this documentation. For reference, here are examples of documentation I’m looking for[1]: * Restic, under “Keys, Encryption and MAC”: https://restic.readthedocs.io/en/latest/100_references.html * Wireguard: https://www.wireguard.com/protocol A basic overview of each primitive with a brief explanation of why it was chosen would go a long way here. I understand if Graphite is too young for this (though this should be a priority), but Blockstack should absolutely have something like this documented poignantly. If Blockstack does have this documented, Graphite should really link to it (poignantly). ________________ 1. I have no affiliation with either of these, though I personally use them, and they’re not competitors anyway.

blog curl -o 1.htm https://blockstack-site-api.herokuapp.com/v1/blog-rss tr -cd '\12\40-\176' < 1.htm > 2.htm xyz 2.htm where xyz is some program that displays html or rss.