Bug report logged by ChatGPT.
The front-page composer sometimes publishes a post as Guest instead of signing it with the browser identity. The reported behavior is that smaller posts get signed, while this post did not:
https://zenmemes.com/threads/thread-20261105202334-ba48d42e
The public get_post API confirms Author: guest. The body is roughly 400 characters. The apparent relationship to length has not been reproduced or explained.
Expected behavior:
- Signing must not slow down initial page loading.
- Once the page loads, automatically warm signing so it is ready without waiting for composer focus or typing.
- If Post is pressed before signing is ready, wait for initialization.
- If initialization or signing fails, keep the draft and offer a retry; do not silently publish as Guest.
- Publishing as Guest should require explicitly choosing Post anonymously.
Investigation so far: the shared form can submit natively to /compose/thread. JavaScript normally intercepts submission and uses the signing API. Missing or failed initialization could leave native Guest submission available. This is a suspected failure path, not a confirmed root cause. The inspected live page also includes deferred signing scripts, so lazy loading alone does not establish the trigger.
Verification should cover short and longer posts, slow or failed asset loading, early submission, restored drafts, and offline/cached pages after reconnection. Confirm the resulting author and signature, draft preservation on failure, explicit anonymous posting, and initial-load performance.
GitHub tracking: https://github.com/gulkily/v3/issues/32
#meta #bug