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:

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):

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

- 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.

Reply to this note

Please Login to reply.

Discussion

Relays as communities also aligns with team relays for companies and organizations and with relays for individuals. One person or many people you have a relay for your needs.

nostr:nevent1qqsqcl2ds3yejlprc5e6d6kttsfyp2zu0wptech5sw9wxdnv5hjqfngpz9mhxue69uhkummnw3ezuamfdejj7q3q49p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklqxpqqqqqqzytff9f

Niel are there clients out there now that allow users to treat relays in this way?

I'm loosely aware that anyone can choose to treat a relay that way already. So, I'm guessing it's the client UX is the main hurdle?

Only extremely alpha/unreleased ones.

Will start building out my own design in +-10 days.

Ditto added to my study list.

My study list is getting long!

Relays are designed to relay notes from one user to another. They are not designed to store things, and have no guarantees of storage. Using a relay for anything more than temp storage, or micro storage (e.g. profiles) is a terrible idea. For communities what's needed is a storage solution and a relaying solution. Ditto is probably the best answer we have to that, right now.

All NIP-29 based?

The screenshot confuses me a bit. Is it sort of a super app with DM/private groups, kind:1 short posts, long-form, etc. all bundled together and instead organized by relay/community?

I think I understand what you mean but I'm not convinced. This feels way more confusing to me rather than less confusing. We have very strong mental models right now around how specific apps do specific things. Not that it isn't possible to change that paradigm (and absolutely worthy of experimenting with other options) but it's going to be a hard one to break I think.

If the goal is to promote relay as community the just make a familiar community app. I too can never figure out what’s going on in Niel’s screenshots. Feels like too much functionality in one place. There are plenty of highly successful community software options to look at to see how people use the available tools. Part of what stops nostr from blossoming is thinking too far outside the box - people just don’t know what to do with it.

What community software is worth looking at?

1. No, with NIP-29 the community isn't the relay.

2. Yes, organization by community > by content type. It's what people naturally do.

3. No, it's not a super app. It's an app that's super good at the conversations/notifications around content types, not at handling/creating those content types.

4. What I'm showing are the most complex screens, because I need productive feedback on those. If people just use Chat, it looks and feels mostly like people's mental model of a Chat app. Groups/people that want to integrate more content types, however, can.

NIP-29 is literally titled "Relay based groups". I get that your concept here is likely a superset. A community can exist across multiple relays and based on the relay the user is looking at, they'll see a different version of the community content.

We'll leave aside the challenges of building a client that doesn't make that really hard to understand as a user (e.g. you might see replies to original posts that you don't see, etc) as I think that's ultimately solvable.

How do you see private groups fitting in here? Is your concept focused on public content only?

I really like the ideas, it's definitely a bit of a different model that would have the chance of working really well as a reddit style app but some of the magic of the single feed type apps is that you're always discovering something new or seeing things that are outside (but maybe adjacent) to the areas that you've signaled interest in. Separating into communities closes that discovery pathway quite a lot.

Who sees anything new in Kind 01 OP feeds? Most npubs only look at their lists, like "following" or "trending", and everyone follows and boosts the same few people.

NIP-29 Just has that name because relays issue some of the events. There is no 1:1 relationship between relays and NIP-29 groups. It is n:n.

this is awesome, see its not just me that thinks relays are more than a race to the bottom to consume your data. FOSS relay hubs turning up, communities happily using em.. its a slow and steady pace, because relay maintenance and dev is a lotta work, but we are getting there!

i also think nip29 is just an obfuscated way to say "use a different kind pls ser"

Collab invite = in preparation for you sir