If only a dev sees this and can share my excitement about it, im literally losing my mind over this! Nostr has liberated backend services!
Discussion
if the issue is to get around centralized apis, are you supposed to handle multiple return values? how is this not just DVMs. seems pretty complex
Its simpler DVMs. What seems complicated?
Also what do you mean by multiple return values? Like batching requests? If yes, then yes batching could be done.
oh i see there is a callee pubkey so there would be only one response. if you're talking to a single relay its still a centralized API. i don't see what this gives you over a web server
You dont need a static IP. Your npub serves as the identification, you can host production backends from your phone. No one can ban your service.
ah i see, so its like NWC in that sense
Ahh yes, i see the parallels, but this more generic, meant more as an http replacement.
This sounds amazing! So you probably also don't need a dns server. That means a parallel internet without censorship. What about domain names? How will that be different on Nostr?
You don't need domain names just the backends pubkey
So, as a use case literally every business has:
Could the back end of a contact form be hosted on nostr from a statically hosted site such as cloudflare pages, ect...?
(I know we have formstr but in practice it's the same as a Google form regardless of what's "under the hood")
Yes, and it makes formstr even more powerful cause you can connect formstr to a locally hosted backend and it works on production
We built a similar tool, for generic http requests
Send any http request (get / post / put etc) and have it executed by a remote machine behind a relay, response sent back the same way
Uses a nostr event if the payload is small, and a blossom blob if it's bigger
Encrypted e2e
httpN
I know, this was my inspiration for it. But i didnt want the auto conversion stuff and felt it could be much simpler, and generalized into a nip. Thanks for making this, so i cohld build on top!
Is this similar to
https://share.google/gCVpcuwqaYUsAUOrI
nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgkwaehxw309a5xjum59ehx7um5wghxcctwvshszrnhwden5te0dehhxtnvdakz7qrxnfk nostr:nprofile1qqstnffh2gam5t7d46zhmyxc5asdunep88yljrvcda68ee7sasx3w0gpz9mhxue69uhkummnw3ezuamfdejj7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qg4waehxw309aex2mrp0yhxgctdw4eju6t09ujd2r4x
No but it does share common goals and does solve some problems, but not holistically, like services don't need DNS' to be hosted anymore. But its not like web clients can stop using DNS as a distribution mechanism. I think both things are taking steps in similar directions
