Add Try subscribe/broadcast flow doc #19
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
||
| With XMTP, messages from a contact you haven't messaged before are kept out of your main inbox until you explicitly approve the contact. Only then can the messages display in your main inbox. This helps you keep your main inbox free from spammy and scammy messages. | ||
|
|
||
| <img src="https://raw.githubusercontent.com/xmtp/docs-xmtp-org/main/docs/pages/img/main-vs-spam.gif" alt="Gif showing the difference between contacts and conversations in a user's main inbox vs scammy/spammy conversations in a user's secondary requests and spam inboxes" width="50%"/> |
There was a problem hiding this comment.
jha looking for better inbox to capture in gif
| 2. Connect the wallet you want to subscribe to the broadcast. To demonstrate the consent feature of the Subscribe button, be sure to connect a wallet address that has not already exchanged messages with the broadcast address. | ||
| 3. Select the broadcast you defined. | ||
| 4. Click **Subscribe**. | ||
| 5. Go to XXXXXXxmtp web app on devXXXXXX and connect the subscribed wallet address. The example welcome broadcast message displays in the main inbox. |
There was a problem hiding this comment.
Need a web app running on the dev network that also supports consent proofs. Asking Fabri and Saul about this on Mon.
| 3. In the broadcast dropdown menu, select the broadcast you defined. | ||
| 4. In the broadcast text field, enter example broadcast text. | ||
| 5. Click **Broadcast** to send the example broadcast text to the subscribed address. | ||
| 6. Go to XXXXXXxmtp web app on devXXXXXX and connect the subscribed wallet address. The example broadcast message displays in the main inbox. |
There was a problem hiding this comment.
Need a web app running on the dev network that also supports consent proofs. Asking Fabri and Saul about this on Mon.
|
|
||
| You can also use the example subscribe-broadcast page to send an example broadcast message. | ||
|
|
||
| 1. In the **broadcast-example-api** repo, update `addresses.json` to include only the address you just subscribed to the broadcast. |
There was a problem hiding this comment.
In a real-life flow, how does the connected address that clicked the Subscribe button get saved so that this manual step isn't required?
And more specifically, how can a creator get their subscriber list without having to rely on the third-party service they may be using to actually do their subscribe/broadcast? I think this needs to be possible when we say that creators can take their audiences with them.
|
|
||
| ```html | ||
| curl -X GET "http://localhost:6989/broadcast?broadcastId=0624abaf-0312-4653-8236-1ff6bda21328" | ||
| ``` |
There was a problem hiding this comment.
How do https://www.npmjs.com/package/@xmtp/broadcast-sdk and https://github.com/alexrisch/broadcaster-app come into the picture? Is there an opportunity to surface them in this README?
jhaaaa
force-pushed
the
send-test-broadcasts
branch
from
2964426
to
c5b5d67
Compare
First pass written with help from ChatGPT. 😅
Preview: https://docs-xmtp-org-git-send-test-broadcasts-ephemerahq.vercel.app/consent/subscribe-broadcast