Nostr will have the best UX in the future, others will just have an authentication hell. GM🌞

nostr:nevent1qqsperxeufyzy3lf0wg90jv2swrky95kqn3hqe9vad0l57q9qtvzq0qpz9mhxue69uhkummnw3ezuamfdejj7q3qdergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsxpqqqqqqzn0h0f5

Reply to this note

Please Login to reply.

Discussion

This was just goose + MCP though right? Or were you using nostr in the video as well?

Goose + dvmcp discovery

How do filter out the noise MCPs?

*do you

You already know the answer, wot, social graph, review, payments. Do you have other ideas?

#communikeys

Can you tell more? How it will work? 🤔

Ask us here :catDance: :

https://chachi.chat/c/660d8c78651f70487ec9b8ddc283e29cf2561693dda3ba246d3fd3c08dbb7083

1) You set up a community with the relay(s), blossom(s), mint(s), etc... you want

2) You pick what content types you want to handle. For example: You add MCP announcements, repos, code snippets, wikis of Nostr specs

3) You can specialize your community around a specific goal and only accept MCP announcements that align with that (you can use automation with fees and filters, per content type)

4) You invite bot npub(s) into the community OR you at least have an addressable starting point to send them to for vibecoding the things you want.

PS: you can target your MCP announcements to multiple communities. This is the game changer that few get.

Soon, I will have a Nipsters and Zaplab community with exactly what I just described and can just point bots there and let them assist me in building Nostr apps with the exact specs that are relevant, my design package, useful code snippets, ... all there.