Random Beacon gathers short snapshots from a wide variety of independent live public feeds, including seismic, adoption, observatory, weather, water, air, traffic, grid, transit, and satellite sources, through a bounded server-side refresh and emits a beacon only when one or more streams qualify for the request. The app does not show the underlying feed locations, private nonce, counters, prior digests, raw buffers, or source code, and it does not ask your browser to do the entropy work.

How the Beacon Qualifies Data

• Each live stream is read server-side into three contiguous 256 UTF-8 character buffers.
• A stream qualifies only when its first, second, and third buffers are all different from one another.
• Only the second buffer from each qualifying stream is used in the beacon calculation.
• Streams that are unreachable, stale, too short, repeating, or unchanged since their prior fetch are reported as not used.
• If no stream qualifies for a request, the app shows a graceful no-beacon state.

How the Beacon Is Formed

• Each qualifying second buffer is hashed with SHA-256.
• The qualifying hashes are XORed together with private server-side state.
• The resulting bits are reversed and hashed again with SHA-256.
• The final result is shown as language-selected UTF-8 characters, base 16, base 8, and base 2.
• Each representation reports its character length.

Privacy and Transparency

The page reports which pseudonymous buffers qualified, which did not, why, and a source page link for each pseudonym. It deliberately avoids showing raw feed URLs, raw source buffers, private state values, stack traces, or implementation code to the browser.