View this deployment live ↗ · 4057862a
View this deployment live ↗ · 5f905e11
View this deployment live ↗ · 81611d1e
View this deployment live ↗ · 9d7329ba
View this deployment live ↗ · 0a50825b
View this deployment live ↗ · ba6bf30f
View this deployment live ↗ · 17f54845
View this deployment live ↗ · bada2a58
View this deployment live ↗ · 6555e52f
View this deployment live ↗ · a3c019ea
View this deployment live ↗ · a2f81707
stop button on the Discord site dashboard.View this deployment live ↗ · e0f94d0b
stop button on the Discord site dashboard.View this deployment live ↗ · 5df82c06
stop button on the Discord site dashboard.View this deployment live ↗ · 22882643
View this deployment live ↗ · 89057b20
View this deployment live ↗ · 6a1464db
View this deployment live ↗ · d9e20530
View this deployment live ↗ · bff7e876
View this deployment live ↗ · 8c7562a8
frame-ancestors none.View this deployment live ↗ · 1e922a7c
View this deployment live ↗ · 0166dfce
View this deployment live ↗ · f486e1e8
View this deployment live ↗ · 2cb2c402
View this deployment live ↗ · e9a11ef1
View this deployment live ↗ · b2d71908
/api/presence: the Discord bot pushes a status into KV, and the card shows online, idle, do not disturb or offline, checked every second.View this deployment live ↗ · 56db5fc0
/api/profile, the view count and the location.View this deployment live ↗ · f4bceccd
/api/hit: the homepage itself counts one view per visitor per day. Before this, only the owner opening the dashboard moved the number.View this deployment live ↗ · 1419a479
View this deployment live ↗ · 6c0af773
/api/stats now answers 401 without the dashboard password.View this deployment live ↗ · 692e1e2b
View this deployment live ↗ · a84e871c
View this deployment live ↗ · 91424912
View this deployment live ↗ · 2376c7f0
View this deployment live ↗ · 4d2cb430
View this deployment live ↗ · 285066c6
View this deployment live ↗ · 52fe7c36
/stats page and /api/stats endpoint: views and people on the site right now, per deployment.View this deployment live ↗ · 46e1f361
stop button on the Discord site dashboard.View this deployment live ↗ · fd2d3ceb
View this deployment live ↗ · b3072c12
View this deployment live ↗ · 17d4801f
stop button on the Discord site dashboard.View this deployment live ↗ · 891d2177
View this deployment live ↗ · b0ef899e
View this deployment live ↗ · 8755f15c
View this deployment live ↗ · 026155d0
View this deployment live ↗ · d7a084ec
View this deployment live ↗ · d6e1112d
Heads up: the version number goes backwards here (v9 → v6)
Nothing was lost between these two builds. The number in each badge is the site's ?v= cache tag, not a release counter.
Before August 14, every file kept its own number: style.css and script.js were on v9, the background video was on v3, and the avatar and icons had no number at all. A number only moved when that one file changed, which is why the early badges skip (v5 → v8).
The mistake that caused: the video's poster image had no number, so after it was regenerated three times, returning visitors were still shown an old copy from their browser cache.
The fix, on August 14: every file was put on one shared number, so any change bumps them all together and nothing can drift out of step again. That shared number started at v6 rather than carrying on from v9, and it has counted up by one ever since.
View this deployment live ↗ · b33b991c
View this deployment live ↗ · a5873321
Heads up: the version number skips from v5 to v8 here
v6 and v7 never went live. No deployment on Cloudflare - production or preview - carries either number. These two builds were deployed seven minutes apart on August 12, so v6 and v7 can only have been used on the local copy in between, while the change was being tried.
What actually changed from v5 to v8: one thing. The speaker icon in the music button was nudged sideways by 0.92 px (0.22 px when muted) so it sits visually centred in its circle.
The mistakes: at the time, each file had its own number and it was raised on every local try, so numbers were used up without ever shipping. And script.js was byte-for-byte the same in both builds but its number still went from v5 to v8, so returning visitors downloaded an identical file again for nothing.
The fix: the one in the v9 → v6 warning above - on August 14 every file moved to one shared number, raised together once for each build that goes out.
View this deployment live ↗ · 6b6bbb29
View this deployment live ↗ · 42514f6e
?v=) so returning visitors pick up new files instead of stale cached ones.View this deployment live ↗ · aa3b3caf
View this deployment live ↗ · fe954529