git ssb

2+

cel / scuttlebot.io



Tree: 86cfe7c6ec39c87ba43e41c3ed13c7902bf07fd8

Files: 86cfe7c6ec39c87ba43e41c3ed13c7902bf07fd8 / tmpl / guides / concepts / social.html.js

1884 bytesRaw
1var page = require('../../page.part')
2module.exports = () => page({
3 section: 'docs',
4 tab: 'guides-concepts',
5 path: '/social/social-network.html',
6 content: `
7 <h2>Social network</h2>
8 <p>
9 Scuttlebot forms a global cryptographic social network with its peers.
10 Each user is identified by a public key, and publishes a log of signed messages, which other users "follow."
11 </p>
12 <p>
13 Scuttlebot searches the P2P mesh for new messages and files from followed users and from FoaFs.
14 The messages and files are stored locally, indefinitely, for applications to read.
15 </p>
16
17 <h3>Identity</h3>
18 <p>
19 Users are identified by confirmations in the social graph.
20 This is known as a Web-of-Trust.
21 There is no global registry of usernames.
22 Instead, users name themselves, and share petnames for each other.
23 </p>
24 <p>
25 Discovery occurs by examining the social graph, or by out-of-band sharing.
26 Applications can analyze the follow-graph, and look for "flag" messages, to determine who is trust-worthy in the network.
27 </p>
28
29 <h3>Pub Servers</h3>
30 <p>
31 "Pubs" are bot-users that have public IPs.
32 They follow users and rehost the messages to other peers, ensuring good uptime and no firewall blockage.
33 </p>
34 <p>
35 Pubs have no special privileges, and are not trusted by users.
36 However, because Scuttlebot has no DHT or NAT-traversal utilities, users must "join" a Pub to distribute their messages on the WAN.
37 </p>
38 <p>
39 Scuttlebot can change Pubs, or join more than one, and sync directly over Wifi.
40 Identity is not tied to the Pubs.
41 </p>
42 <p class="next"><a href="/docs/social/follow-users.html">Follow users</a></p>
43 <ul class="see-also">
44 <li><a href="/whitepapers/secure-scuttlebutt.html">Secure Scuttlebutt</a></li>
45 </ul>
46 `
47})

Built with git-ssb-web