Minimum TTL bug? (API) about onetimesecret HOT 5 CLOSED

Funny - I was just about to report the inability to specify a ttl lower than the 7/14 day defaults. Longer works, but not shorter.

from onetimesecret.

from onetimesecret.

Well, discussing it further, 1 hour seems the most appropriate to me, since I can imagine quite a few situtations where lesser ttl can be desired.
BTW, it's been said that this is for abuse prevention, but afaik there's per...day(?) secret limit you discussed right here. So, having these limits and considering common... user speed? I'd say the smallest still-appropriate ttl would be 1 minute. Just a proposal tho.

About s/m ttls. I understand why they are sent back, but generate have them as options. The problem here is that i checked and ttl's weren't set correspondingly to sent request. Do NOT consider this as a bug tho, 'cause I didn't tested it properly. 'll open another issue if I confirm my assumption

from onetimesecret.

Thanks for the follow up and clarification. I removed the unused query params from the docs.

The minimum TTL was a straight up bug as evidenced here:
6205faf#diff-36f8bb4628f358a7841a9c9be443d52dL419

The ticket auto-closed with the commit message but feel free to re-open if you find anything else for this. And thanks all for helping make onetimesecret better.

from onetimesecret.

Thanks.
But providing more functionality, separate metadata_ttl and secret_ttl are could still be reasonable to have in request params. Could be said that number of situtations where it could be usable is, like, almost zero. But still, if you want such a "weird" functionality - why not :D

from onetimesecret.