Commit 85033c122b1f84bdfdc8ec4c569b365ffc5ac91c
back links
Dominic Tarr committed on 3/28/2015, 12:18:51 AMParent: 04e33813859529da7681345158af5bbe7b4ffe70
Files changed
| FAQ.md | changed |
| FAQ.md | ||
|---|---|---|
| @@ -43,8 +43,13 @@ | ||
| 43 | 43 | |
| 44 | 44 | A feed link is the same as a user identity (the hash of a public key) and refers to a feed. |
| 45 | 45 | A message link is the hash of a particular message. An external link is the hash of file (also known as an attachment) |
| 46 | 46 | |
| 47 | +### backlinks | |
| 48 | + | |
| 49 | +Since you replicate all your friends data locally, if someone replies or links to your message | |
| 50 | +then you will have that data, and to it's easy to show related messages. Messages can refer to each other, and you can see what messages link back to a given message. Post a photo and then someone can create a thread about it -> instant comment feature. Post a module, and then the comment system becomes an issue system, etc, etc | |
| 51 | + | |
| 47 | 52 | ## why is there a size limit on messages? |
| 48 | 53 | |
| 49 | 54 | Messages are limited it 1kb in size so that the time required to replicate is predictable. |
| 50 | 55 | Also, since peers will replicate all messages for peers they follow, it's important that peers do not create an unreasonable amount of work for each other. |
| @@ -54,11 +59,23 @@ | ||
| 54 | 59 | ## Attachments |
| 55 | 60 | |
| 56 | 61 | Attachments are immutable blobs of binary data, similar to email attachments. When clients see a message that refers to a given attachment, it will request it if the peer does not already have that attachment. Attachments are limited to 10mb. Replication of larger files could be implemented by integrating bittorrent (or even better, [webtorrent](https://github.com/feross/webtorrent) |
| 57 | 62 | |
| 58 | -## can we have user names? | |
| 63 | +## how do new users join the system | |
| 59 | 64 | |
| 60 | -Yes, although it's not possible to have globally unique user names, because that would require a central registry of names, and then the system would not be decentralized. | |
| 65 | +To join the network, a user needs to know a server in the system, to have their data replicated, | |
| 66 | +they need someone to follow them. The simplest way to join the network is to use an invite code. | |
| 67 | +The invite code contains the address of a pub server, and a secret that lets the server know it's | |
| 68 | +okay to replicate them. If you run your own pub server you can create invite codes and give them to your friends. | |
| 69 | + | |
| 70 | +## pub servers | |
| 71 | + | |
| 72 | +wifi routers (Network Address Translation "NAT") and the shortage of ip addresses make p2p difficult. The simplest way around this problem was to create "pub servers". A pub server is exactly like a normal client, except you run it on a server with a static ip address. "pub" as in a bar where your friends meet to exchange gossip. Anyone can run a pub server. | |
| 73 | + | |
| 74 | +## how do I reserve my user name? | |
| 75 | + | |
| 76 | +SecureScuttlebutt does not have traditional user names, because that would require a central registry of names, and then the system would not be decentralized. | |
| 77 | + | |
| 61 | 78 | Instead ssb uses a [pet name](http://www.skyhunter.com/marcs/petnames/IntroPetNames.html) system. Pet names are different to how user names normally work on the internet, but similar to how nick names actually work in real life -- your friends choose your name, instead of you choosing your own name. You may request others call you something (choose your own name), but friends ultimately decide. If your friends all agree to call you _Bob_, that _is your name_. |
| 62 | 79 | |
| 63 | 80 | If an attacker tries to pretend to be you, it's up to your friends to notice and flag them. |
| 64 | 81 | |
Built with git-ssb-web