Reflection delay

When you press Prepare to share, sizuq saves your writing as a draft and opens a screen called the Reflection moment. It shows the drop, asks you one question about it, and offers two ways out: Reconsider, which takes you back to the editor, and Share, which publishes.

If you set a Reflection delay, the Share button stays unavailable until that time has passed. The question on the screen changes between visits. It is not a checklist — it is there to make you read your own sentence one more time.

The countdown is not a timer running in your browser. It is a subtraction: sizuq stores when the draft was created and how long you asked it to wait, and works out the rest whenever you come back.

• Closing the tab, reloading, or switching devices does not restart the wait.
• Nothing is lost while you wait — the draft is saved before the countdown begins.
• Coming back after the delay has passed means Share is simply available.

The delay is not enforced by the button being greyed out. It is checked again on the server every time a drop is published, and a request that arrives too early is refused with an explicit too-early response.

This is deliberate. A cooling-off period that a determined person can route around in the console is a suggestion, and sizuq did not want to ship a suggestion. Making it a server rule means the delay you chose is the delay that happens — including for anything you write against the API yourself.

Two minutes is long enough to lose an argument with yourself and short enough that you will not abandon the drop. Immediate is there for the notes that genuinely do not need it, and choosing it is not cheating — the Reflection moment still opens, and still asks.

The delay is set per drop, in the Details card, at the moment of writing. There is no account-wide default, on purpose: the decision belongs to the piece of writing in front of you, not to a settings screen you configured once.