[Feature Request] Expire after reading N times.

[AbstractUmbra]

Niche feature, I know, but good for "secure" pastes you only want to be read once.

We already filter out things like Discord's user agent, so very easy to send a paste over discord, someone views it, it burns.
Or have it read 10 times and it be gone before the 11th.

[EvieePy]

By view once do you mean once per user? Because this is basically impossible, or do you mean total amount of views?

[AbstractUmbra]

Total views by anyone/thing.

[EvieePy]

What if bots somehow consume the views?

[EvieePy]

Or would these pastes always have a password or potentially differnt URL path?

[AbstractUmbra]

A risk to be taken, but this feature is on many other paste services (and personally a favourite of mines haha)

[EvieePy]

To clarify:

If you create the paste on the frontend and you view the paste with your session cookie, does this count? Or does this session cookie get immunity?

Further to the above point, creating the paste on the frontend vs API is currently different, the former always consumes a view automatically, is this considered a view?

Should every self detonating paste require a password?

[AbstractUmbra]

The session cookie would get immunity, yes. Otherwise the "view" just after creation would consume a view from the bucket as it were.

Yes, the paste creation via the frontend consumes a view so ideally this would fall into the above, where the session cookie is present and thus is immune to consuming a view (although a refresh removes that cookie and WOULD consume a view, if my understanding of the current implementation is correct).

A password would be optional I believe, but I'm open to it being a necessity.