git ssb

0+

Dominic / ssb-peer-invites



Commit 21ae23f01fae8bf8697229c0ae69a68842b2e368

fix some missing "user" mentions

mixmix committed on 2/4/2019, 12:51:20 AM
Parent: d7f18bb72566f32143d78451ca1a2eefb974f3ef

Files changed

README.mdchanged
README.mdView
@@ -15,19 +15,19 @@
1515 * hard to tell if growth was word of mouth or not
1616
1717 ## usage
1818
19-With user invites, you can create invites without having a pub.
20-However, your local sbot needs to support user invites.
19 +With peer invites, you can create invites without having a pub.
20 +However, your local sbot needs to support peer invites.
2121 that requires installing the following, if you havn't already:
2222
2323 ```
2424 sbot plugins.install ssb-device-address
2525 sbot plugins.install ssb-identities
2626 sbot plugins.install ssb-peer-invites
2727 ```
2828
29-with user invites, you do not need to have your own pub server,
29 +with peer invites, you do not need to have your own pub server,
3030 as long as you have a friend has one (that supports peer-invites).
3131 To enable peer-invites on your pub, install the same modules
3232 and restart, and also announce a public address using
3333 [ssb-device-address](https://github.com/ssbc/ssb-device-address)
@@ -56,12 +56,12 @@
5656 >sbot peerInvites.acceptInvite {invite_code}
5757 accept_message...
5858 ```
5959
60-## user invites - how it works
60 +## peer invites - how it works
6161
62-host (user creating the invite) generates a _seed_, and publishes an invitation
63-message (`type:'peer-invite'`) for their guest (new user, receiving the invite)
62 +host (peer creating the invite) generates a _seed_, and publishes an invitation
63 +message (`type:'peer-invite'`) for their guest (new peer, receiving the invite)
6464 The message may contain both a private and a reveal section.
6565 (private section is only readably be the guest, but reveal is published
6666 if they guest accepts the invite).
6767
@@ -96,19 +96,19 @@
9696 their friend to not be a jerk) `reveal` can be used to enhance this. It could for
9797 example - be used to assign someone a name before they are invited.
9898
9999 private can be used for the benefit of the guest. it may contain a welcome message
100-or links to threads or channels, or users to follow.
100 +or links to threads or channels, or peers to follow.
101101
102102 on success, cb is called with `{invite: msgId, seed: seed, pubs: [addr,...]}`
103103 this information can be sent to the guest as the invite!
104104
105105 ### peerInvites.openInvite(invite, cb(err, invite_msg, content)
106106
107107 "open" an invite. retrives the invite message created by the host (using `peerInvites.create`)
108108 and decrypt any encrypted values. since the invite may contain a welcome message, etc,
109-user interfaces implementing user interfaces should process peer-invites in two steps.
110-firstly opening the invite, then accepting (on user confirmation)
109 +peer interfaces implementing peer interfaces should process peer-invites in two steps.
110 +firstly opening the invite, then accepting (on peer confirmation)
111111
112112 calling openInvite will not publish a message, but may make a network connection
113113 (if you do not already possess the `invite_msg` which you won't the first time)
114114
@@ -120,9 +120,9 @@
120120 ## example
121121
122122 Alice wishes to invite Bob to her corner of the ssb
123123 network. But she is does not have a pub server.
124-She creates a _user invite_, indicating that she
124 +She creates a _peer invite_, indicating that she
125125 is creating an invite. This is just a message on her feed.
126126
127127 ``` js
128128 var seed = random(32) //32 bytes of randomness

Built with git-ssb-web