nostr-protocol / data-vending-machines Goto Github PK

Hey @believethehype , I have some questions/observations on the image gen job request.

The combination of ratio and upscale does not seem to cover the case where a client wants an output image of a specific size. (i.e. 900x300). We have this use case on tasktiger.io, where a jobchain needs to know the size of the image to be generated.

A couple proposal I could think of

1. Go back to the old way of using ["param", "size", "900x300"]. This way any arbitrary size could be supported
2. Keep ratio and remove upscale. Create a new image upscaling job type that accepts the final dimension (px) as a param. To generate an image of a specific dimension(px), clients have to specify the ratio during image generation, and then feed the output to the image upscaling job to get the exact dimension as desired.

Mostly thinking out loud here, what do you think?

Non dev here, working in big corporate with skills on data process and data management, how do you plan to keep data secure, private, avoid breach, reuse, ..?
Asking to make sure this project succeed in real world scenario and can scale and be used by everyone staying gdpr compliant