Skip to main content
605Buzz
Today Search Corrections Following About Join waitlist

3 of 17 desks have not been read in over 48 hours, and 2 more have not finished a read in over 14 days. Their pages say when each was last read. Anything those desks show as upcoming or underway may have changed — check the source before relying on it.

605Buzz

Corrections record

community / First published

Pierre's Library calendar lists "Tuesday Night Book Club" for November 3, 2026

Published automatically from public-record data. Whether a person reviewed any later version is recorded against that version below. This heading is the article's current headline.

Article identifier: community-pierre-2865

Read the live article →

Version history

Every published version of this article, newest first. Versions are append-only: a correction adds a row, it never rewrites history. Each version below states what changed against the version before it — which fields moved, and which body lines were added or removed.

The content hash is a SHA-256 fingerprint of that version's stored headline and body, computed when the version was written. Two versions with the same hash hold identical text; a changed hash proves the text moved. It is the tamper-evidence check — recompute it against an exported copy of a version and any silent edit shows up as a mismatch.

How we verify a hash — and how you can

Canonicalization: the hashed bytes are the version's stored headline, then the two characters ||, then the version's stored body markdown — UTF-8, SHA-256, lowercase hex. Nothing else is in the input: no normalization, re-wrapping or rendering is applied first, no trailing newline is added, and no other field (including the parent version's id) is mixed in.

Export a version's stored headline and body, join them with the two characters ||, and take the SHA-256 of the UTF-8 bytes. It must equal the hash printed beside that version. In a shell: 

printf '%s' "HEADLINE||BODY" | shasum -a 256

  1. Version 2

    Source update — the underlying public record changed

    Automated update from the source feed — no human edit

    The body text changed; the headline did not. (compared against version 1)

    Removed (1 line )

    • The city's feed says it published this entry on 2026-10-09 at 16:35, printed as published. That is when the listing went up, not when the event is. The feed labels that time -0600, which is the publishing platform's own default rather than a statement about this city, so it is recorded but not applied.

    Added (1 line)

    • The city's feed says it published this entry on 2026-10-20 at 19:34, printed as published. That is when the listing went up, not when the event is. The feed labels that time -0600, which is the publishing platform's own default rather than a statement about this city, so it is recorded but not applied.

    Content hash: 9eb52e0f34cbbee03e7ee0db9a422653112505915212cd6deda4e0547fde79e2

  2. Version 1

    Initial publication

    Initial automated publication — no human byline

    No earlier version is in this record, so there is nothing to compare against.

    Content hash: ca6067f0c434c9e627fd796f65c79191f3d75091954aa24159401b450e17ca9a

1 correction has been issued.

See something wrong? Read the corrections policy or write to corrections@605buzz.com — though mail to 605buzz.com is not routed yet, so that address currently bounces.