What getting a summarization of a NVK (npub1az9…m8y8) 's episode would look like:
👇👇👇👇
Job Request #1: Transcribe bitcoin.review/episode1.mp3 from second 900 to 930; willing to pay between 5000/9000 sats.
```
{
"id": "12345",
"pubkey": "abcdef",
"content": "I need a transcript of Bitcoin.review from second 900 to 930",
"tags": [
[ "j", "speech-to-text" ],
[ "params", "range", "900", "930" ],
[ "input", "http//bitcoin.review/episode1.mp3", "url" ],
[ "bid", "5000", "9000" ]
]
}
```
Job Request #2: Grab the output of that job and summarize it; willing to pay between 300/900 sats.
```
{
"id": "12346",
"pubkey": "abcdef",
"content": "I need a summarization",
"tags": [
[ "j", "summarization" ],
[ "params", "length", "3 paragraphs" ],
[ "input", "12346", "job" ],
[ "bid", "300", "900" ]
]
}
```
Service providers compete to serve this request (if they choose to fulfill it based on their risk analysis).
quotinghas anyone thought/written about data-processing services via nostr?
nevent1q…d6yk
I'm thinking of, as Gigi (npub1der…xzpc) 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 Highlighter (npub1w0r…cu4x) (cc dk (npub1kuy…kdj8) Max (npub18lz…ugm3) ); 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.