Niel Liesmons

:task: Task teasing #chateau #communikeys #testapp

:90percent: there for publishing and displaying Tasks in #communikeys

Users need to have ZERO relays if they just want to enjoy publishing in #communikeys.

They need ONE (inbox) relay if they also want:

• Mail
• A personal back up
• Restricted sharing of specific publications

That's it.

bringing epic relay feeds in Nosotros. With Articles etc...

should watch out.

Also, play this stuff out and what you end up with, will be something very close #communikeys.

Communities with:

• main + backup relays (and media servers)
• an identifier with agency (key)
• the content types they wok with, listed
• write and read access controls for each content type

joining in on the test-message fun in #communikeys :community:

https://npub1zz6g0z3r2xaqwf4k4u5f6cqsstc0qx9hjxkd5flxaazq3wnx03xqppq4fv.nsite.lol/examples/#group/communikeys

any reason why I can't find my Zapchat and Zaplab #communikeys anywhere? Nor this tool, nor

itself can find them 😔

Wen Nostr data on #pkarr servers? Are there proof of concepts?

Need it for many friends. #communikeys

The #outbox model turns into the #dickoutbox model real fast.

It puts the responsibility over content moderation and targeting in the hands of the actors that are least incentivized to do it well.

Better solutions:

1. #communikeys If you let people target each publication to Communities, you can pull the (moderated!) replies, reactions, zaps, ... from there. You have a global (yet decentralized) state to work with. And you don't even need Followers and all these other dark patterns that are needlessly copied from #BigTech.

2. An #inbox relay that is just that, a mailbox where a user receives things that are targeted at him. And not at all of his network 🤦. A mailbox where you set whatever limits you want for people to reach. And not one where you have to pay for people to spam you for free 🤦.

Money fixes coincidence of wants.

#communikeys fixes coincidence of interests/goals.

:badge: Badges are metadata that you award to a profile.

In #communikeys we plan to use it that way.

Admin, Team, Top supporter, ... 👉 Badges , not roles in some JSON tag.

These badges can be used as a publishing condition. For example: only "Team" can publish Live streams.

You can even ask a one-time fee for such a badge.

Conditional WRITE > Conditional READ #communikeys

When I build a Chat app with:

• Private groups (MLS)
• Public Communities (#communikeys) ... that both use kind 9 chat messages.

How do you really expect me to mix in Nip-17 and call it "DMs" or "Chat Rooms"?

When the kind 14 messages used in that Nip:

• are less secure, private and direct than the MLS I already have
• don't make the conversation have a global state
• can optionally be signed for dispute regulation
• have a subject tag, like email
• can be forked and forwarded, like email
• are perfect for one-off communication in Marketplaces,etc... like email

No thanks.

It's Nostr Mail. Because that's what it's good for.

Not Nostr Direct Messages. My users don't need those false promises and confusion.

My profile doesn't fit into a neat little category for you to put me into.

Instead, my profile publishes about whatever category it wants, in the communities that match my goal. #communikeys

The list of blunt anti-spam "solutions" keeps growing, all of them targeted at the individual user.

Setting screens full of:

• How many profiles can be tagged in one post before you consider it spam (hellthread)?
• What relays do you want to get your data from?
• Do you want to hide pictures from profiles you don't follow?
• Below what WoT score do you want to not see anything of profiles?
• etc etc...

:90percent: of users don't care or know what you are talking about with this.

Community admins on the other hand, do care. Their main value prop is providing a curated experience.

And with #communikeys, they have a waaaay bigger toolbox.

All incentives align and "all" the user has to do is browse those Communities.

:Zapchat: Zapchat = Community browser

FYI: Most of my Nostr activity is, and will be, happening in #communikeys now.

nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg

Yes, these are all Communities. Even that Spanish chad.

Once you have #communikeys to directly target your publications at, "Repost for visibilty!" will sound even more silly.

Communities should have personality.

That's why we're giving them npubs :winkwithtongue: #communikeys

Npubs that can recommend the apps that work well for them and the content types they use.

More and more convinced of putting the supported content types (kinds) + their conditions for publication, in the #communikey event. Instead of relying on the main relay's doc.

If we do it in a way that maps directly onto the relay doc, it has more benefits than downsides:

:Check: Relays can watch that event and admin don't have to log in to relay.tools (or similar) to go and change stuff. :Check: We need a line of communication with the relays anyway, so we might as well use this. :Check: Allows #communikeys to be run on any relay in a way that admin can specify publication conditions :Check: Makes it easier for admin to turn on an exclusive mode (i.e. not allowing publications to be also targeted at other communities), without one relay having to be the authority. :Check: Easier and faster for apps to find (and be clear) on the info. :Check: It means you can just specify your conditions once, and have you blossom servers (and other non-relay infra) respect it all too.

WDYT

#communikeys is a superior answer to every single one of these questions.

Is it me or are the

NIP-29 chats all down because of one relay?

Need #communikeys asap.

I don't want my Communities tied to a specific domain name.

So, either Relays need key pairs. #keylays Or Communities need key pairs so they can switch their main relay. #communikeys

I can't sell Communities that you cannot fully own.

If #communikeys are a bad idea, tell me now 😉