You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This proposes that the return type of generation endpoints be changed to return objects in the structure of:
{
"seed": 1234,
"url": "https://..."
}
This would mean that applications are able to access the seed by which a ducky is generated, if it's randomly generated (although this would be included for consistency on seeded ducks too).
Note that this format (returning a URL) relies on quackstack being made to use S3 compatible object storage before it can be implemented.
The text was updated successfully, but these errors were encountered:
This proposes that the return type of generation endpoints be changed to return objects in the structure of:
This would mean that applications are able to access the seed by which a ducky is generated, if it's randomly generated (although this would be included for consistency on seeded ducks too).
Note that this format (returning a URL) relies on quackstack being made to use S3 compatible object storage before it can be implemented.
The text was updated successfully, but these errors were encountered: