fred/wallet
1
0
Fork 0
forked from cheng/wallet
Code Pull Requests Activity

social networking algorithm designed

Browse Source
This commit is contained in:
reaction.la 2022-06-16 08:37:48 +10:00
parent 2a3bd9e023
commit 5517b7814a
No known key found for this signature in database
GPG Key ID: 99914792148C8388
2 changed files with 31 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/set_up_build_environments.md
View File

@ -176,6 +176,12 @@ Setting up an actual server is similar to setting up the virtual machine
modelling it, except you have to worry about the server getting overloaded modelling it, except you have to worry about the server getting overloaded
and locking up. and locking up.
On an actual server, you probably want to totally disable passwords by corrupting the shadow file once you have `ssh` working.
```bash
usermod -L root
```
If a server is configured with an [ample swap file] an overloaded server will If a server is configured with an [ample swap file] an overloaded server will
lock up and have to be ungracefully powered down, which can corrupt the data lock up and have to be ungracefully powered down, which can corrupt the data
on the server. If the swap file is inadequate, the OOM killer will shut on the server. If the swap file is inadequate, the OOM killer will shut

25
docs/social_networking.md
View File

@ -264,6 +264,31 @@ So, you can navigate to whole world’s public conversation through
approved links and reply-to links – but not every spammer, scammer, and approved links and reply-to links – but not every spammer, scammer, and
shill in the world can fill your feed with garbage. shill in the world can fill your feed with garbage.
## Algorithm and data structure.
For this to work, the underlying structure needs to be something based on
the same principles as Git and git repositories, except that Git relies on
SSL and the Certificate Authority system to locate a repository, which
dangerous centralization would fail under the inevitable attack. It needs to
have instead for its repository name system a Kamelia distributed has
table within which local repositories find the network addresses of remote
repositories on the basis of the public key of a Zooko identity of a person
who pushed a tag or a branch to that repository, a branch being a thread,
and the branch head in this case being the most recent response to a thread
by a person you are following.
The messages of the people you are following are likely to be in a
relatively small number of repositories, even if the total number of
repositories out there is enormous and the number of hashes in each
repository is enormous, so this algorithm and data structure will scale, and
the responses to that thread that they have approved, by people you are not
following, will be commits in that repository, that, by pushing their latest
response to that thread to a public repository, they committed to that
repository.
Each repository contains all the material the poster has approved, resulting
in considerable duplication, but not enormous duplication.
The underlying protocol and mechanism is that when you are following The underlying protocol and mechanism is that when you are following
Bob, you get a Bob feed from a machine controlled by Bob, or controlled Bob, you get a Bob feed from a machine controlled by Bob, or controlled
by someone that Bob has chosen to act on his behalf, and that when Bob by someone that Bob has chosen to act on his behalf, and that when Bob