---
title: "Comment by Praneet Brar on \"I built a Codex reset page that only watches the public clock\" | Hashnode"
description: "Separating 'confirmed' from 'we observed it on one account' is a nice honest touch for a public board. Since the rule-change alerts are the quieter, more expens"
url: "https://hashnode.com/posts/i-built-a-codex-reset-page-that-only-watches-the-public-clock/6addfd9fc49e4c03682cd5de/comment/6ae486d6de402a02763f25b8"
---

[Discussion](https://hashnode.com/posts/i-built-a-codex-reset-page-that-only-watches-the-public-clock/6addfd9fc49e4c03682cd5de)

Comment [I built a Codex reset page that only watches the public clock](https://hashnode.com/posts/i-built-a-codex-reset-page-that-only-watches-the-public-clock/6addfd9fc49e4c03682cd5de)

[Praneet Brar](https://hashnode.com/@praneetbrar)

[Oct 30](https://hashnode.com/posts/i-built-a-codex-reset-page-that-only-watches-the-public-clock/6addfd9fc49e4c03682cd5de/comment/6ae486d6de402a02763f25b8)

Separating 'confirmed' from 'we observed it on one account' is a nice honest touch for a public board. Since the rule-change alerts are the quieter, more expensive ones, how do you actually detect a rule change, by reading source posts by hand or something automated?
