Damus
Niel Liesmons profile picture
Niel Liesmons
@Niel Liesmons

Designer that codes.
Also #WordStudy #Dadstr #Farmstr

Relays (9)
  • wss://eden.nostr.land/ – read & write
  • wss://niel.nostr1.com/ – read & write
  • wss://nos.lol/ – read & write
  • wss://nostr.wine/ – read & write
  • wss://relay.damus.io/ – read & write
  • wss://relay.primal.net)/ – read & write
  • wss://relay.primal.net/ – read & write
  • wss://theforest.nostr1.com/ – read & write
  • wss://zaplab.nostr1.com/ – read & write

Recent Notes

hodlbod · 11h
Partitioning spaces by content types is artificial, that's not how social groups actually work. That's an imposition of the limitations of the app/protocol on communication. This is why integrations a...
Niel Liesmons profile picture
Huh? I don't know if it's me or if you're contradicting yourself here?

So let's be practical:
How can the Zapstore community announce that it has Apps?

Without apps having to randomly query the relay for event kinds, that might not even be targeted to the actual community, that is.
1
hodlbod · 10h
I don't know if I understand your question, but if the community has chat, someone might want to drop an App listing in chat as well as have it available everywhere. I would say in most cases it would make sense to quote the app listing event in a kind 9 chat message to explicitly bring it into cont...
Vitor Pamplona · 11h
Lol, yes... I have not had a good experience relying on relays being up.
Niel Liesmons · 11h
Then step away from having the relay BE the community and just let communities use a main relay as infrastructure, just as they also use a blossom server etc...
hodlbod · 11h
Partitioning spaces by content types is artificial, that's not how social groups actually work. That's an imposition of the limitations of the app/protocol on communication. This is why integrations are so popular; they bridge one siloed content type to another content type. Nostr can fix this nativ...
hodlbod · 12h
The way I'm handling this in flotilla is by "embedding" non-chat stuff into the chat interface. But of course, not all kinds can/should be rendered. Which is the same problem across the rest of nostr,...
Niel Liesmons profile picture
There is way to be non-messy guys.

Have one event that specifies the content sections of the community.

Rooms can be such content sections.
Forum posts another, Apps another, Polls another, Repos another...

Whatever the community wants to cater to. Let them announce that.

The daily drivers do NOT have to support every root kind. They only have to be really good in the comments/reactions/zaps around the root kinds (+ good in chat too).
1
Niel Liesmons · 11h
Then, let community specify which list of profiles can write in what content section. And have one UX flow to join any of these white-lists. Transparent, not opaque stuff relay-side.
verbiricha · 1d
NIP-29 taking off :poggers: nostr:nevent1qgst9nwtxlfj2vc5tsqvfapatc0pm6muv77wafl0v06jdjjv4wy3vvcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz...
Niel Liesmons profile picture
Heads up, I'm gonna hopefully come up with a way to have Nip29-style Chat Rooms as something you can make part of a wider content-type Community (that also is an App catalog, can have actual Forum, etc...).

Really do think there might be a way. And I see the benefits of some Nip29 relay-specific things, for rooms only tho
1
verbiricha · 1d
u da man