Relays are Communitues, by default. Surfacing (and using!) them in that way is how you get to their #normielization. To the people around me (of which 90% doesn't use or enjoy Twitter btw) I show this: https://cdn.satellite.earth/eb05a00d6357928c045c898dee476b4ce6ced17e2fa5a0b9bffb212ebb3b6613.png Then I tell them: "Every chat/group/community you see here **is** a Relay (server)" They all get that part straight away and thus know what relays to choose for their outbox 👉 the communities they want to publish in They also grasp pretty quickly that they can publish more than just chat messages in there: posts, articles, events, audio, repos, ... And honestly they get pretty exited about this part specifically. In my designs, every such publication, when opened, displays to what communities it was targeted (and accepted of course): https://cdn.satellite.earth/da6911b627e2d19096bc57d3259b06dfa54f1401a6688c4beac3db5cc5d6c62d.png This helps with community discovery and with helping them understand that they can target their stuff to more than one public community at once. Then, for the inbox-part it comes down to shilling the benefits of having a personal relay: - a backup of all your stuff - fast access and computation for you specifically - having your own inbox that you can set a price or other conditions for - publishing private things exclusively to a whitelisted set of npubs https://cdn.satellite.earth/7bcfe1478007d70033b5e22667be930cb91608923ddf3fa9f5f9270e6c8899b9.png - privacy in general - etc... One last thing that can help is not displaying relays as freaking geeky looking websites 😅. Relays need npubs, and the profile name that comes with it, if you ask me.

0
1
3

0
0
3

0
1
3

0
0
3

Showing page 1 of 1 pages