From c9e9bce7ee9f83f07b3bc3542b21b3b28e7e78f9 Mon Sep 17 00:00:00 2001 From: Daniel McCoy Stephenson Date: Wed, 11 Nov 2026 19:45:55 -0700 Subject: [PATCH 1/2] Say where a hand-set server-id counts, and when a count goes untagged The README's "Resetting it" paragraph did not say that only a column-0 server-id: line outside the tags: block is read, nor that a quoted value is accepted, so an operator who indented the line would see a new ID appended. "The wire format" said a coalesced count always carries the coalesced tag, which withCount skips at 32 tags. Co-Authored-By: Claude Opus 5.5 --- README.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 8f7d665..a9fa399 100644 --- a/README.md +++ b/README.md @@ -81,9 +81,11 @@ in memory for that run only — `build()` still never throws. **Resetting it.** Delete the `server-id:` line; the next start writes a new one. Or set your own value (letters, digits, `_`, `.`, `-`, starting with a -letter or digit; at most 255 characters). A `server-id:` line whose value is -anything else is ignored, and the next start appends a new one to the end of -the file. +letter or digit; at most 255 characters; bare or quoted). Only a `server-id:` +line at the start of a line, outside the `tags:` block, counts, and the first +valid one wins. A `server-id:` line that is indented, inside `tags:`, or whose +value is anything else is ignored, and if no valid one is left, the next start +appends a new one to the end of the file. **Opting out.** Every [opt-out](#opting-out) below also stops the ID: a disabled client never generates one, never writes one, and sends nothing. @@ -278,7 +280,8 @@ Shade it into a plugin jar; it is one class. is JSON); `tags` always holds at least `version`, and `install` whenever the client has an [installation ID](#every-event-carries-a-random-server-id) and the event is under 32 tags, and the count of a -[coalesced](#repeated-events-are-coalesced) event also carries `coalesced`. The server assigns the +[coalesced](#repeated-events-are-coalesced) event also carries `coalesced` +unless the event already carries 32 tags. The server assigns the timestamp. A `201` is success; anything else is logged at `FINE` and dropped. Redirects are not followed. The body is streamed with a fixed length, so From ecae0e66d99690637a20d65b3dbea547450d985b Mon Sep 17 00:00:00 2001 From: Daniel McCoy Stephenson Date: Wed, 11 Nov 2026 19:47:08 -0700 Subject: [PATCH 2/2] Say column 0 rather than "a line at the start of a line" Co-Authored-By: Claude Opus 5.5 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a9fa399..5325e94 100644 --- a/README.md +++ b/README.md @@ -82,7 +82,7 @@ in memory for that run only — `build()` still never throws. **Resetting it.** Delete the `server-id:` line; the next start writes a new one. Or set your own value (letters, digits, `_`, `.`, `-`, starting with a letter or digit; at most 255 characters; bare or quoted). Only a `server-id:` -line at the start of a line, outside the `tags:` block, counts, and the first +line that starts at column 0, outside the `tags:` block, counts, and the first valid one wins. A `server-id:` line that is indented, inside `tags:`, or whose value is anything else is ignored, and if no valid one is left, the next start appends a new one to the end of the file.