blob: 4a71d6885c1b4db3ccb7e7b0207894108e053a4e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
|
Arching Kaos Infochain
Another idea is to make a chain for credentials in order to interconnect the APIs of the different nodes of Arching Kaos instances.
To do that, I was thinking about a combination of the IDs of the Node is carrying.
(Mind the gap)
{
"ipfs",
"cjdns_publickey"
"ssb"
}
API get this packet.
SSB
Then we want to peer with them. We follow the SSB id from our running SSB instance (the one on arching-kaos project). That is done.
We can also have the ability to exchange confidential messages through SSB to our followers/following lists.
CJDNS
Convert the publicKey to ip6. Then we can work on the rest. We can compare with CJDNS peering list but possibly, public IP and the peering could be solved using the previous article/"NEWS"/thoughs file...
IPFS
Utilize it to contain arching-kaos-{publish-the-previously-mentioned packet, new-public-credentials-announce, new-mixtape-messages, ( if we stop using IRC ) or even which ever thing the API does plus ++}.
Note:
IRC is mentioned here. If we attach a bot to the instance of Arching Kaos, the bot can refer to things of the SSB.
|
