Ah okay, cool, or I guess the communi-key npub could just DM you the notification (or an npub approved by the communi-key to send support DMs could).
On the screening side, I'm not quite sure how much screening logic a strfry relay can be set up to do before it starts to smoke. Or how a strfry relay can be integrated with an external service to handle heavier loads, via those policy plugins and stuff. I'm sure it's all doable though.
There's already many relays that have their own policies built in.
There's one for 240 chars only, one for GM posts, one for posts with an đź‘€ reply on it by a certain npub.
So if that's all all possible and already active. I don't see the limit here. But I'm a noob on the relay side.
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.
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.
How about this. Everyone who joins the community is assigned a personal bot, call it a concierge spot.
DMs leave that option open, yes. (while visually it's just the Communikey contacting you)
And don't enforce it.
¡Me gusta!
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.
All via kind1 posts, no DMs
Then I prefer the privacy and polyvalence of DMs
You could have each person decide if they want the bot to @ mention them in a kind 1 or just DM or both.
Nope. I see no benefit in kind 1s, only downsides. It's public and bad UX. Messages make more sense.
*Concierge bot
You're making me reconsider DMs actually, but not in the sense that you'd first imagine it.
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.
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
Ah yes, just read this. This is what I first had in mind. And DMs are okay for this.
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..."
