4 ms·
Hi folks, my project: AlphaDec is a human-readable, lexically sortable UTC encoding. It's designed to be timezone-agnostic, reversible, and safe for use in LLM
by firasd 1y ago
Hi folks, my project:
AlphaDec is a human-readable, lexically sortable UTC encoding.
It's designed to be timezone-agnostic, reversible, and safe for use in LLMs, filenames, and database keys.
Examples like 2025_M4O2_todo.txt carry timing information (seasonal + positional) but avoid ISO collisions.
It encodes the full UTC year as a symmetrical orbital structure:
26 periods × 10 arcs × 26 bars × 10 beats. Each one tickable in JS, Bash, or Python.
Inspired by the clean abstractions of Snowflake IDs, but readable by humans and AIs.
Live clock: https://firasd.github.io/alphadec/ https://firasd.github.io/alphadec/
Interesting images of Claude reverse-engineering it:
1. https://firasd.github.io/alphadec/assets/2025_O3U4_alphadec_ai_reverse_engineering1.png https://firasd.github.io/alphadec/assets/2025_O3U4_alphadec_...
2. https://firasd.github.io/alphadec/assets/2025_O3U4_alphadec_ai_reverse_engineering2.png https://firasd.github.io/alphadec/assets/2025_O3U4_alphadec_...
3. https://firasd.github.io/alphadec/assets/2025_O3U4_alphadec_ai_reverse_engineering3.png https://firasd.github.io/alphadec/assets/2025_O3U4_alphadec_...
4. https://firasd.github.io/alphadec/assets/2025_O3U4_alphadec_ai_reverse_engineering4.png https://firasd.github.io/alphadec/assets/2025_O3U4_alphadec_...
- JimDabell 1y agoI’m a bit confused about the comparison with ULID. Identifiers like that (and KSUID, etc.) have a time component and a random component, so that multiple systems that generate IDs simultaneously won’t collide. This scheme only includes the time component. But in your comparison with ULID you describe it as collision resistant. How is this the case?