Nostr Web Client

DMs are the worst solution imo.

What else though I wonder? if the goal is to piggyback off of existing client notifications then the communi-key would have to trigger a notification via an existing pathway (replying to a post, mentioning in a standalone post).

>That message can even be as simple as a reply on the targeted publication event (just thought of that).

But if the failed-validation post never gets published then there's no post to reply to no? I suppose a communi-key support account could simply @mention you with a boilerplate "You tried to make a post that failed..." message, and you'd get notified that way.

Reply to this note

Please Login to reply.

Discussion

Niel Liesmons 9mo ago

1) There's no need to piggyback off of anything, since this is a new thing that apps would integrate. Might as well go for the most elegant solution we can think of then.

2) Good point on the event not being there. As said, I just though of it. I you think of a great way, let me know. And again, it can be completely outside of the box of what exist.

Garbage nsec 9mo ago

How about this. Everyone who joins the community is assigned a personal bot, call it a concierge spot.

Niel Liesmons 9mo ago

DMs leave that option open, yes. (while visually it's just the Communikey contacting you)

And don't enforce it.

¡Me gusta!

Garbage nsec 9mo ago

When the person joins the community, the bot will spin up an account and greet them, hey welcome to the community!. When an event is rejected, the bot will explain to them what happened, (again this is just a mention, but the person can also follow the bot account for regular updates). The bot isn’t posting anything not directed at that specific individual. And when the person leaves the community, the bot will say goodbye and then take itself out of existence.

Garbage nsec 9mo ago

All via kind1 posts, no DMs

Niel Liesmons 9mo ago

Then I prefer the privacy and polyvalence of DMs

Garbage nsec 9mo ago

You could have each person decide if they want the bot to @ mention them in a kind 1 or just DM or both.

Niel Liesmons 9mo ago

Nope. I see no benefit in kind 1s, only downsides. It's public and bad UX. Messages make more sense.

Garbage nsec 9mo ago

It would encourage kind1 clients to get their DMS in order, that’s one thing

Niel Liesmons 9mo ago

I'm not counting on Twitter clones.

Chat = the universal UX you build out from

🌍 🔫

Niel Liesmons 9mo ago

Copying Twitter UX is an order of magnitude easier than copying Telegram UX.

Garbage nsec 9mo ago

*Concierge bot

Niel Liesmons 9mo ago

You're making me reconsider DMs actually, but not in the sense that you'd first imagine it.

Niel Liesmons 9mo ago

We need a general communication line between "You" and the "Communikey" for several things:

- The Communikey saying "We didn't accept this publication because of XXXX"

- The Communikey saying "We would like you to publish (target) your great article (about a topic we cover) here"

- You buying Products from the Communikey

So it might as well be DMs (spec wise) but it doesn't mean I have to display it as a completely different chat.

Niel Liesmons 9mo ago

Already have several options in mind for how ti fit it in the UI of the Community itself.

I like this idea. Thanks nostr:npub1hyxredcavc6ruqgsf4wf4hmakpwnvefmzaspl7dja6a2sxlx0q3sxwtqnx

Garbage nsec 9mo ago

Ah yes, just read this. This is what I first had in mind. And DMs are okay for this.

Garbage nsec 9mo ago

Trying to imagine some of the future passive aggressive DMs from the communi-key bot:

"Hi there, it looks like you just tried to post to the community from CLIENT. While there was nothing wrong with your post, unfortunately CLIENT is having some issues showing community content as desired, and so we've temporarily stopped accepting community posts from CLIENT. Our community can be fully enjoyed, including posting of all accepted types, in the following apps: OTHER CLIENT, OTHER CLIENT, OTHER CLIENT..."