Show thread history
Niel Liesmons
2w ago
Video is easier for me 😉.
1️⃣ What any App that adopts Communikeys needs (at the very minimum) is a "Share" screen that lets users target their stuff.
2️⃣ The clients don't need to check if it "follows Community Guidelines", that's a job for the community's set up. The clienst can however, see the pricing (and other conditions for each content type) in the #communikey creation event and use that in their UIs pretty easily.
3️⃣ The last step missing is the way for the community to send "a message" back, if needed/wanted
1️⃣ What any App that adopts Communikeys needs (at the very minimum) is a "Share" screen that lets users target their stuff.
2️⃣ The clients don't need to check if it "follows Community Guidelines", that's a job for the community's set up. The clienst can however, see the pricing (and other conditions for each content type) in the #communikey creation event and use that in their UIs pretty easily.
3️⃣ The last step missing is the way for the community to send "a message" back, if needed/wanted
See translation
1
1
0
0
0
Replies
Joe working on B2B
@Joe
2w ago
Thanks for the video, design looks sleek.
So coming back to the example of the text-post-only community; I thought there might be front-end validation in some simpler cases like that, but if all handled by the communi-key then how would that work? The post gets sent and then it's the communi-key's main relay that has the logic to parse the post (does it conform to spec)? And if the main relay rejects the post because it does not conform to spec then that rejection is the basis for the validation-fail notification client side?
Just trying to figure out where the actual computation happens vis a vis screening the event content against the presumably machine-readable spec.
So coming back to the example of the text-post-only community; I thought there might be front-end validation in some simpler cases like that, but if all handled by the communi-key then how would that work? The post gets sent and then it's the communi-key's main relay that has the logic to parse the post (does it conform to spec)? And if the main relay rejects the post because it does not conform to spec then that rejection is the basis for the validation-fail notification client side?
Just trying to figure out where the actual computation happens vis a vis screening the event content against the presumably machine-readable spec.
See translation
0
0
0
0
0
Niel Liesmons
@nielliesmons
2w ago
Computation on the hosting side = services that I can sell.
Doing it client side, breeds inconsistent experiences. And if there's one thing I can't sell, well, ... :winkwithtongue:
Doing it client side, breeds inconsistent experiences. And if there's one thing I can't sell, well, ... :winkwithtongue:
See translation
0
0
0
0
0
Niel Liesmons
@nielliesmons
2w ago
Yup, doing that computation on the relay (+ maybe blossom server) front seems to be the best win-win imo.
Main relay does computation, rejects your targeted publication event (and doesn't store the actual event neither) and sends a message back to you "Sorry, this is not TXT".
That message can even be as simple as a reply on the targeted publication event (just thought of that).
Main relay does computation, rejects your targeted publication event (and doesn't store the actual event neither) and sends a message back to you "Sorry, this is not TXT".
That message can even be as simple as a reply on the targeted publication event (just thought of that).
See translation
0
0
0
0
0
Joe working on B2B
@Joe
2w ago
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.
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.
See translation
0
0
0
0
0
Niel Liesmons
@nielliesmons
2w ago
DMs are the worst solution imo.
See translation
0
0
0
0
0
Joe working on B2B
@Joe
2w ago
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.
>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.
See translation
0
0
0
0
0
17 more reply(ies)
Niel Liesmons
@nielliesmons
2w ago
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.
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.
See translation
0
0
0
0
0