> when service provider serves the data the user pays to the "best" service provider
why would I burn server cycles if the chance of payment is totally subjective? seems easy to DDOS.
has anyone thought/written about data-processing services via nostr?
I'm thinking of, as nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc says, a vending machine model.
Money in, data out.
Example:
I publish an event saying I want "X data processed in Y form, will pay Z", services compete to serve me the data back.
Rationale:
I'm integrating audio/video highlights on nostr:npub1w0rthyjyp2f5gful0gm2500pwyxfrx93a85289xdz0sd6hyef33sh2cu4x (cc nostr:npub1kuy0wwf0tzzqvgfv8zpw0vaupkds3430jhapwrgfjyn7ecnhpe0qj9kdj8 nostr:npub18lzls4f6h46n43revlzvg6x06z8geww7uudhncfdttdtypduqnfsagugm3 ); instead of handling the transcription within Highlighter (which is what I'm doing now via the `whisper` model), what if users could query for that specific service and pay for it directly to the right service provider?
Ideally, the user would have no "account" or "balance" on any of the service providers (vending machines don't have balances!), and ideally only the "best" (as understood by the user) is rewarded.
The way I imagine it working is:
* user publishes X event with the job spec
* service providers that can handle that job spec compete to serve it (risk!)
* when service provider serves the data the user pays to the "best" service provider
Ideally there would be no negotiation steps between user<>provider, at least for inexpensive compute.
Obviously there's risk to the service provider here, but it's risk that would be very easy to price/handle for a motivated service provider.
The upside is a transparent, always-on global marketplace for data-processing/compute.
Discussion
You can only DoS yourself; ir service provider, not service slave 😂
maybe I’m misunderstanding. I imagined this working as follows:
- user x publishes a note asking for a service y
- servers 1, 2, and 3 all provide service y. I run 1 and you run 2. we both race to process the job and submit a note
- user x pays server 2
is this how it works?
It can be how it works. User might pay for both, or neither of the results suck