⚡ Zaps For All ⚡
I’m thrilled to announce our new API enabling zaps in ANY app.
Zaps are a new, jaw dropping customer experience for the world and Nostr Wallet Connect (NWC) is the first Other Stuff killer feature of Nostr.
Use our API to enable zaps in your app without needing to integrate Nostr or Bitcoin and without your users needing a Nostr account.
To show what’s possible, we built the first app - a Zap Bot that enables zapping in Discord. Want to add the bot to your server? Message us at https://www.makeprisms.com/zapbot
Learn more and get API access at https://www.makeprisms.com
$boost $like
Incredible
The fact that it's not called "The Zeus" yet.
Only his fortune and his company's future. But yeah other than that, nothing much.
Odell's all caps are gentle caps. Other people's all caps are aggressive af.
AND THEN THEY WILL GIVE 'BONUSES' TO CERTAIN INDIVIDUALS TO EFFECT DESIRED OUTCOMES. BRIBES. THEN WE'RE BACK IN OLD TIMES. FUN! nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx SAYS HE WON'T ALLOW THAT BECAUSE HE AND HIS FRIENDS ARE SOMEHOW SPECIAL AND IMMUNE TO HUMAN NATURE. WHAT COULD GO WRONG?! LOL.
Calm down, only 610dell has the monopoly on all caps. You need a loicence to all caps, mate.
So it's really a feature of the protocol that following people in different clients will nuke your follows eventually? Is there no good way to prevent this without sacrificing decentralisation? Or just following people strictly on one client even if you use multiple clients for other stuff.
Well, devs in general. Sovereign code isn't limited to nostr projects of course.
It will probably increase the work. But nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 did a great job simplifying the git bullshit for us mere mortals.
It will be interesting to see which workflow nostr devs will prefer once we release our solution to replace github. Not that it will be mutually exclusive at all with the nostrocket&GitStr way but the way things are developing it seems there will be at least two major ways to maintain projects.
With nostr:nprofile1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qgmwaehxw309aex2mrp0yh8wetnw3jhymnzw33jucm0d5hsz9mhwden5te0we5hgmmj9ehx7um5wgcjucm0d5hsqgpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5a3m46r 's GitStr you can now send a git patch to Amethyst through Nostr's relays and fully avoid GitHub.
Instructions here: https://github.com/fiatjaf/gitstr
Do you think it will increase overhead to accept changes both via PR's and GitStr? Or is it always better (more robust) to accept both?
Damn, that's a lot of fixes.
I’m not good with memes. This could be my very first try with a video ever. 🤣 #Bitcoin https://video.nostr.build/e72ecff810f491b3475e7335d79aefa47c4f12989b56592041d1937f121c3cbd.mp4
You did good shock trooper
Cool! Is that frontend agnostic? Can that be displayed in markdown in another more visual tool where you would want to see some pictures etc.?
Also, Nostr users are already sold on the Nostr itself so no need to sell that aspect necessarily.
Does that imply everyone should know a techy person they trust that much? Because that's a big assumption to make. It sounds nice though. Nowadays it's so easy to disconnect from the immediate local community it's refreshing to see plans that financially incentivise making local communities stronger.
My thoughts exactly. And some people will have their whole stack rugged by one mint because they put too much trust in one central custodian. But that's just how it goes.
This is the way.
Once we release it's easy to converge on the individual NIPs specifying the form of an issue event, etc. to ensure interoperability. Then the specs are based on a working solution.