PABLOF7z on Nostr: lol, this NIP (data vending machine) I'm writing is hilarious; I just added this note ...
lol, this NIP (data vending machine) I'm writing is hilarious; I just added this note regarding job chaining and how should service providers should behave
(e.g. should they wait for explicit approval from the user? should they wait for payment?)
```
Ambiguity on job acceptance, particularly for job-chaining circumstances is deliberately ambiguous: service providers could wait until explicit job result acceptance / payment to start working on the next item on the chain, or they could start working as soon as they see a result of the previous job computed.
That's up to each service provider to choose how to behave depending on the circumstances. This gives a higher level of flexibility to service providers (which sophisticated service providers would take anyway).
```
(e.g. should they wait for explicit approval from the user? should they wait for payment?)
```
Ambiguity on job acceptance, particularly for job-chaining circumstances is deliberately ambiguous: service providers could wait until explicit job result acceptance / payment to start working on the next item on the chain, or they could start working as soon as they see a result of the previous job computed.
That's up to each service provider to choose how to behave depending on the circumstances. This gives a higher level of flexibility to service providers (which sophisticated service providers would take anyway).
```