From 7f592621758f9dc1b8e7d0dacf9faa0b52555e23 Mon Sep 17 00:00:00 2001 From: "reaction.la" Date: Thu, 29 Aug 2024 06:51:59 +0000 Subject: [PATCH] still fixing README -- two README's now --- README.md | 9 +++++++-- docs/rootDocs/README.md | 20 ++++++++++++++++++++ docs/setup/contributor_code_of_conduct.md | 19 ++++++++++--------- docs/setup/set_up_build_environments.md | 23 +++++++++++++++++++++++ 4 files changed, 60 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index d81f3ca..1660940 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,13 @@ it will not be private for much longer). You cannot have truly end to end encryption, except you control your own keys directly. -To make an actually useful social net requires a lot of engineers doing a lot of work, which requires funding, which requires a a profit model. The current business plan being to [eat SWIFT's lunch](./docs/manifesto/SWIFT.html), by creating an environment in which one can create and operate the necessary Daos. +To make an actually useful social net requires a lot of engineers doing a lot of work, +which requires funding, which requires a a profit model. +The current business plan being to [eat SWIFT's lunch](./docs/manifesto/SWIFT.html), +by creating an environment in which one can create and operate the necessary Daos. + +We need uncensorable speech to save civilisation, but uncensorable speech does not pay the bills. +Uncensorable money does pay the bills. The rest of the documentation is in Pandoc markdown, rather than Gitea or Github markdown, so you will have to build it before any of these links work. @@ -103,7 +109,6 @@ update in pushes, pulls, checkouts, and switches. [cryptographic software is under attack]:./docs/setup/contributor_code_of_conduct.html#code-will-be-cryptographically-signed "Contributor Code of Conduct" -{target="_blank"} It will, however, also implement signed commits, and insist you have set up a key pair as explained in the contributor code of conduct because [cryptographic software is under attack] from NSA diff --git a/docs/rootDocs/README.md b/docs/rootDocs/README.md index c860dcc..ee0963f 100644 --- a/docs/rootDocs/README.md +++ b/docs/rootDocs/README.md @@ -3,6 +3,26 @@ title: >- README --- +## About + +Wallet is open source software intended to become the manager of hierarchical + deterministic keys for a social network that a superset of the Bitmessage social net, + for securely pseudonymous uncensorable public communication, + and securely private communication. (Telegraph looks like +it will not be private for much longer). + +You cannot have truly end to end encryption, except you control your own keys directly. + +To make an actually useful social net requires a lot of engineers doing a lot of work, +which requires funding, which requires a a profit model. +The current business plan being to [eat SWIFT's lunch](./docs/manifesto/SWIFT.html), +by creating an environment in which one can create and operate the necessary Daos. + +We need uncensorable speech to save civilisation, but uncensorable speech does not pay the bills. +Uncensorable money does pay the bills. + +The rest of the documentation is in Pandoc markdown, rather than Gitea or Github markdown, so you will have to build it before any of these links work. + [pre alpha documentation (mostly a wish list)](docs/index.htm) [copyright © and license](./license.txt) diff --git a/docs/setup/contributor_code_of_conduct.md b/docs/setup/contributor_code_of_conduct.md index d710bc3..d43aa7c 100644 --- a/docs/setup/contributor_code_of_conduct.md +++ b/docs/setup/contributor_code_of_conduct.md @@ -16,7 +16,7 @@ that frequently strange and overcomplicated design decisions are made, decisions), decisions whose only apparent utility is to provide paths for hostile organizations to exploit subtle, complex, and unobvious security holes. -McAffee reported that this is a result of plants - the state plants engineers +McAffee reported that this is a result of plants -- the state plants engineers in nominally private organizations to create backdoors. Shortly after he reported this he was arrested and murdered by the US government. (To be precise he was arrested at the instigation of the US government, and then @@ -131,10 +131,11 @@ identified cryptographically, rather than through the domain name system. then at the root of your repository ```bash -ssh-keygen -t ed25519 - C gandalf -f .git/gandalf #to create your key pair -git config user.signingkey .git/gandalf.pub #tell git to use this key pair -git config user.name gandalf #will be ignored -git config user.email gandalf@ #fake email will be ignored +nm=gandalf +ssh-keygen -t ed25519 -C $nm -f .git/$nm #to create your key pair +git config user.signingkey .git/$nm.pub #tell git to use this key pair +git config user.name $nm #will be ignored +git config user.email $nm@ #fake email will be ignored git config include.path ../.gitconfig #sets various defaults, ssh signing among them ``` @@ -143,7 +144,7 @@ git config include.path ../.gitconfig #sets various defaults, ssh signing among to the .gitsigners file to publish your public key to anyone who wants to make sure that commits are from the nym that they claim to be -- at least claim to be when their commits are - displayed by the git aliases of `.gitconfig` + displayed by the git lg alias provided by `.gitconfig` The nym in `.gitsigners` is the one that matters, though `user.email` and `user.name` should be the same or sufficiently related to @@ -266,13 +267,13 @@ practice people only used Zooko identity, and Web of Trust was a cloud of confusing complexity and user hostile interface on top of Zooko identity. What gpg identity is primarily used for in practice is to make sure you are getting the latest release from the same repository managed by the same person as -you got the previous release - which is Zooko identity, not Web of Trust +you got the previous release -- which is Zooko identity, not Web of Trust identity, and has no real relationship to email. Zooko identity is about constancy of identity, Web of Trust is about rightful use of email addresses. Web of trust was a true names mechanism, and today no one speaks the truth under their true name. -Web of trust was designed for a high trust society - but in a high trust -society you don't need it, and in a low trust society, the name servers were +Web of trust was designed for a high trust society -- but in a high trust +society you don't need it, and in our low trust society, the name servers were too vulnerable to enemy action, and died, leaving the Web of Trust user interface in every installed copy of gpg a useless obstacle. diff --git a/docs/setup/set_up_build_environments.md b/docs/setup/set_up_build_environments.md index ade10ef..a007534 100644 --- a/docs/setup/set_up_build_environments.md +++ b/docs/setup/set_up_build_environments.md @@ -3085,6 +3085,29 @@ This is by far the simplest and most direct way of allowing the world to get at [Git Book for Git daemon](https://git-scm.com/book/en/v2/Git-on-the-Server-Git-Daemon) +When you have submodules, an issue arises with people accessing the submodules through different protocols. +The fix is to make `.gitmodules` protocol agnostic by using relative urls. As for example + +```.gitmodules +[submodule "libsodium"] + path = libsodium + url = ../libsodium.git + branch = rho-fork +[submodule "mpir"] + path = mpir + url = ../mpir.git + branch = rho-fork +[submodule "wxWidgets"] + path = wxWidgets + url = ../wxWidgets.git + branch = rho-fork +``` + +This will enable recursive cloning and all that to work regardless of the root protocol. + +After amending the `.gitmodules` file you need to execute the command `git submodule sync`, +and now that you are using relative urls, when the base url changes, `git submodule sync --recursive` + ### Gitweb Does much the same thing as git-daemon, makes your repository public with a