Just realised Zap.stream will play in the background on android. I have a lot of nostr:nprofile1qqs9tuz9jpn57djg7nxunhyvuvk69g5zqaxdpvpqt9hwqv7395u9rpgpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhswz3hdy radio coming on.
What is your vision?
What problem are you solving for your user?
IMO clients need to niche down until they can answer those questions.
Then deploy funds to make that niche sticky.
Just discovered WhatNot. Watched stream after stream of people breaking and bidding collectibles.
Seems uniquely fitted to a clone on Nostr rails. Livestream plus chat plus marketplace with zaps payments
(tiny AOVs would makes zaps significantly cheaper than ccard).
US$5bn valuation, $3bn GMV in 2024. Juice seems to be worth the squeeze.
Literally browsing Nostr while Cline codes for me rn
Yeah, so, I just wasted 4 hours of my life trying to get https://github.com/jamesmagoo/nostr-writer to compile, but I was just stumbling from one bug-fix to the next, with no end in site. On and on and on....
How far did you get with this?
I have been using Nostr plugin for Obsidian but
1. Image upload is now broken. Articles still publish just without any image, and I have to upload them separately.
2. "d" tag is a random string, but many clients use this as a URL, so ideally I would use keywords or a string derived from the title.
3. Two-way sync between Nostr and the vault would be a killer feature.
"Global" is always such a bad idea
You're right of course that's what relays do.
And as a user, I'm going to select to use certain relays based on some reason. I am forced to be selective, as there is no global state.
And as I'm selecting, on what basis am I selecting?
I'm selecting on the basis of where my people will see and post notes. I need a word for this concept, so let's say "community".
Yes I'm probably wrong, and meanwhile I'm also building stuff that works this way, and it works well.
What about just using a relay with NIP-01 and NIP-42 only? It seems to work
nostr:nprofile1qqs2js6wu9j76qdjs6lvlsnhrmchqhf4xlg9rvu89zyf3nqq6hygt0spz9mhxue69uhkummnw3ezuamfdejj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uygje4n I finally came around. Relays are communities.
H/t to all the great folks for code and inspiration nostr:nprofile1qqsgzfdez8ksa9xmuvqg5zly3nl9e5xqkpvj8nllj9aw06ra4pqq3qcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9uqdl3vp nostr:nprofile1qqsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36cpr3mhxue69uhhyetvv9ujucnfw33k76twwpshy6ewvdhk6tcpzdmhxue69uhhwmm59e6hg7r09ehkuef0qy2hwumn8ghj7un9d3shjtn4w3ux7tn0dejj7ne6u4e nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhkcmmrdd3x77pwve5kzar2v9nzucm0d5hszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0qydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tc4rdlnm nostr:nprofile1qqswa8vhnelpgx9f7arjhtuzmjtqs2sdgfgmw77tzu9xankf87kl7eqpzdmhxue69uhhwmm59e6hg7r09ehkuef0qydhwumn8ghj76rpwejkutnpvd3kjmmv0yh8xmmrd9skctcprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7jk0p5w nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug
nostr:nprofile1qqst3axzay8sm4n8zg2n84acmt7hwwztpdg9r7p89e2f83v007f7zjcprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq7lw5g published this https://github.com/AbdelStark/nostr-mcp
Also I have a quite complete Nostr implementation for n8n AIs, and could potentially port to MCP if there's demand.
Xkcd
E.g.
I define a npub that is an LLM that will respond to users.
The npub publishes it's spec as NIP-89 including anything e.g. context window size.
A user publishes a kind 5910 note, tagging the npub, with content complying with the spec.
The npub replies with 6910 for success response or 7000 for anything else.
Check out what Gzuuus DBTH etc are doing with DVMCP. Each tool defines it's parameters in a NIP-89 declaration, then responds in the DVM style (5910, 6910, 7000), when tagged, based on those params.
Very extensible for any tool to use (an AI, or any API, as a tool). Can define and require any parameters (context window size for an AI, stock symbol for a price query, etc).
Use a good password for sure
I agree specific DVM kinds is kind of quirky. I think the issue is that the observed usage is different from how the spec was conceived.
Spec: specify a kind and see which npub replies
Actual use: tag a specific npub
If someone tags and npub that is set up to give a certain response, then the kind number seems redundant.
But IMO this kind of thing is always the issue with defining a new spec, including if you were to define a new one. IMO better to evolve what is already in use.
DVMs are good. What would a Nostr AI Connect do?
🚀 Excited to share https://dvmcp.fun – a Nostr-powered catalog where humans and AI discover and use DVMCP servers for decentralized computation. Think of it as a decentralized directory where MCP operators can announce their tools and resources using DVMs, allowing people to utilize them. This represents a new way to leverage DVMCP servers, and the creation of custom interfaces.
🤖💻 It's still a work in progress (so expect some rough edges!), but you can already explore and use tools at https://dvmcp.fun Guides on usage and deploying your own DVMCP setup are coming soon, in the meantime if you are interested there are some readmes in the DVMCP repo
→ Code: https://github.com/gzuuus/dvmcp
→ Frontend: https://github.com/gzuuus/dvmcpfun
Feedback welcome :)
#dvm #mcp #ai #llm
Great share Gzuuus. Is this for marketing e.g. if I wanted to promote nostr:nprofile1qqsx7ke38jurn3ukuvjz7ercez6wacgj844cr42ek4qcu7854ql4saqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsctyxnu or nostr:nprofile1qqsf8ncgzhyqp058qnwzvh0p2hvxjelsh87wxpqrqdp4lmc5kxww0jspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs3jn4vj (or other future servers)? How to add servers to this list?
I built this a few weeks ago and kind of forgot to tell people about it. I need to get a blog up.
Relay uses NIP-42 auth for read and write, and client uses "-" tag to tell relays not to redistribute notes.
I do exactly this!
The set up is as follows
1- the client is Jumble.social
2- the relay is SW2
Set up SW2 with read and write auth to the desired pubkey.
Set up Jumble to read from the relay, and when posting, hit the switch to "post only to this relay"
That sounds like a good approach. And, if you've just removed a bunch of broken stuff this may be a good time to start.
What setup are you using where the AI is making its own commits? Sounds bold
I’m gonna burn through a lot of AI credits trying to fix my websocket implementation.
Replit must be happy. People like me are probably their best customers, not professionals who know exactly what they’re doing.
nostr:nevent1qqsgetwwvsy4crt9n99j758uhzhdzlvj2392la99mwyrglqz7jeh9ksppemhxue69uh5qmn0wvhxcmmv82j88s
I recommend having a git strategy here. If (when) your AI blows up the codebase you can go back to the last commit.
#asknostr where can I learn more about the "-" tag?
My relay accepts notes with this tag from Jumble, but rejects notes with this tag from n8n.
I went looking for the NIP but I can't locate it.
Jumble makes a pretty good Agent web UI.
Pictured:
- Jumble
- connected to a private relay (SW2 with Read Auth)
- a websocket trigger (nostr-webhook)
- triggering an n8n agent (Jonny)
- with Nostr read/write/zap tools
Thanks to nostr:nprofile1qqsgzfdez8ksa9xmuvqg5zly3nl9e5xqkpvj8nllj9aw06ra4pqq3qcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9nhwden5te0dehhxarj94ex2mrp0yhxzurs9uqsuamnwvaz7tmwdaejumr0dshstm459s nostr:nprofile1qqsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36cpr3mhxue69uhhyetvv9ujucnfw33k76twwpshy6ewvdhk6tcpzdmhxue69uhhwmm59e6hg7r09ehkuef0qy2hwumn8ghj7un9d3shjtn4w3ux7tn0dejj7ne6u4e nostr:nprofile1qqszclxx9f5haga8sfjjrulaxncvkfekj097t6f3pu65f86rvg49ehqpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qy88wumn8ghj77tpvf6jumt99uj4cs7t nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhkcmmrdd3x77pwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9ux73xm6
I added NIP-42 Read Auth to SW2 relay, and my goal is to use it for small communities.
Then, to dogfood that I built a Websocket to Webhook trigger for my AIs, and I've been chatting with them on the relay today, using Jumble like an agent chat UI.
Disconcerting (but awesome) to post loads of notes to a private (read auth) relay, then see them all appear in all your clients.
Hopefully only I (and team, and robots) can see the posts.
Impossible to tell from the client UI!
As a good friend reminded me recently "if you're not embarrassed by your first release, you waited to long." 🤙
Oh my yes. What are you building kat?
I hear the kids call this "vibe coding" now.
Cline with Claude 3.7 very good.
I'd use it.
Should we keep the convention of 5000's for request and 6000's for responses?
E.g. 5999 ping, 6999 pong, 7000 some other message
MCP Server marketplace (discovery) added to Cline. How to get DVMCP discovery into here? nostr:nprofile1qyg8wumn8ghj7mn0wd68ytnddakj7qgkwaehxw309ahx7um5wfjkc6t5v4ejummjvuhsqgzqh8y9lll2lsw2m7xrpf89ezrxplmwf9c6phrj84dtva94ucd52yr8jvw7 nostr:nprofile1qyg8wumn8ghj7mn0wd68ytnddakj7qg3waehxw309ahx7um5wgh8w6twv5hsqgyehd2erjg3vcq0s3gs05clndv79a78uzdpl7qzap836s762472vsrjsxlx
Just created an automated AI pull request reviewer using o1, #n8n and webhooks.
nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8 nostr:npub1fgz3pungsr2quse0fpjuk4c5m8fuyqx2d6a3ddqc4ek92h6hf9ns0mjeck nostr:npub1s5rq2ztdh76shy578znvympa2mzz2vjushs9mc5mwkdupewke67qeuf7u3
Hey JB, this may interest you I have just written an n8n agent which can use MCP tools over the Nostr DVM network.
Any MCP tool you can use with Claude Desktop can be hosted and used with n8n over Nostr.
