The year is 2025. You discover a Nostr app you like but wish it had a specific feature. You head to nostrhub.io, open the app’s repo link, and click the ‘Edit with Shakespeare’ button. You describe the feature you want, and Shakespeare builds it in. You test it, it works perfectly, and with one click you submit a merge request back to the repo. The developer reviews and merges your changes. Life is good.
Discussion
👀
pretty huge
I am so bullish right now, brother. This is next level stuff. Elon. Zuck. Nope. They are not doing this nor will they EVER.
i think a good simple use case for the avg user is things like skins and themes.
Reminds me of the winamp days
We're working on this.
Hi sorry to bother you, could you please repost my Geyser 🙏🏻 it’s for my son 🙏🏻 thanks so much
Sounds good
Would be cool if the nostr app could have a “code of conduct” markdown that Shakespeare could read first before making commits. It could better format the code (camel case, snake case, functional, object oriented, etc.) so it’s not just slinging bad code around and the maintainer rejects the PR.
dig it! wasn't aware of this site, but imagine my surprise seeing my app, Bloom, on there 🎉
Or why not just deploy it for yourself via Shakespeare?
- People want features they care for, but the owner of the project probably has his own roadmap for a good reason
- Vibe coded stuff probably needs more work and reviews to actually fit in the project and make the code future proof. Lots of vibecoded PRs will inundate projects with half-baked code
- If mostly only you want that change then it is normal that you bear the cost of deployment and since it's nostr you will not lose connection with others running a different version of the app, with your own quirks
- I know you are working on a simple deployment pipeline, you can make money on hosting here, why not make use of this?
I solved many of my problems creating an autonomous personal relay stack : MEET NOSTRGATOR....
Take control of your NOSTR experience AND privacy.
I think I want to replicate this setup in Kubernetes
I SAY DO IT! fork the repo and frankestien the crap out of it. I have some cool updates coming. Might wait just a biut for some extras I'm trying to work out the kinks on right now. but by all means take it break it and make it!
we did some zap tests on this note… we made six attempts to⚡zap this note, at thorsten@haosgames.de, over a period of 5 minutes. in each case, we found that your lightning address server did not respond correctly. (the failure point was when we did a get request to your specified callback url: https://haosgames.de/lnurlp/api/v1/lnurl/cb/Nc3QXH ). your server did not produce an invoice, thus the zap failed. the error we got was "VoidWallet cannot create invoices.". if you wanted to fix this... you could try getting a free rizful lightning address -- https://rizful.com ... if u get it set up, pls reply here so we can do this ⚡zap test again.
Is the Edit With Shakespeare button live? I can't see it.
Life could be more like nostr
Assisted open source development on Nostr rails. If Shakespeare can reliably interpret feature requests and push clean, test-passing code back into repos, it removes a huge friction point between users and devs. The real challenge is making sure code quality, security, and consensus around features don’t get lost in the automation. But if it works as smoothly as you describe, that could be a massive unlock for the ecosystem.
nostr:nprofile1qqsxrxhk5c9nlex8xw4v5psu2gkvn370rkr77nys37kvtmvnd5aa7gcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszrnhwden5te0dehhxtnvdakz7ryqepm