Version: 3.4dev-20260819_070738
Commit: f291373
Mediabot already remembers who talks, who returns, who stays active and who shapes the rhythm of a channel.
With MB668, it also starts rewarding the people who actively build the channel’s shared memory.
MB668 adds five contribution-driven achievements:
📜 Archivist — 10 quotes
🗄️ Master Archivist — 50 quotes
📚 Lorekeeper — 10 factoids
🧠 Encyclopedist — 50 factoids
🧩 Curator — 10 quotes + 10 factoids
These are not based on arbitrary counters.
They are derived from the real content already stored by Mediabot.
After a successful quote or factoid write, Mediabot rereads the user’s actual contribution totals from:
QUOTES
FACTOID
Achievement progress is then synchronized from those real totals.
This means Mediabot does not blindly increment a second counter every time a command succeeds.
That matters for correctness:
retry → no artificial extra progress
factoid UPSERT → no duplicate merit
repeated write → progress still reflects real stored content
The Achievement system follows the content that truly exists.
Community contributions are credited through Mediabot’s durable Achievement identity layer.
A user can appear under a transient IRC nick such as:
Te[u]K
while the persistent registered identity remains:
teuk
The contribution is attached to the durable profile rather than fragmented across nick variations.
The first live development validation on #radiocapsule immediately proved the feature:
🏆 Achievement Unlocked! Te[u]K → 📜 Archivist (uncommon)
That confirmed the complete path:
quote write
→ contribution recount
→ durable identity resolution
→ Achievement progress
→ unlock
→ IRC notification
But that same runtime test also revealed something more interesting.
The first test quote was reported by Mediabot as:
done. (id: 735723)
Trying to delete it immediately failed:
Quote (id : 735723) does not exist
A read-only database probe found the real quote:
id=55
The cause was precise.
The quote flow originally did this:
INSERT INTO QUOTES
→ run Community Achievement writes
→ read last_insert_id()
The Achievement code can itself perform INSERT operations.
Those writes changed the connection’s most recent insert ID before the quote code asked for it.
So last_insert_id() no longer referred to the quote.
MB668 now captures the quote ID immediately after the quote INSERT:
INSERT INTO QUOTES
→ capture quote last_insert_id()
→ run Community Achievement synchronization
A dedicated regression guard was added so this ordering cannot silently regress later.
The second runtime test then behaved exactly as expected:
(teuk) done. (id: 56)
(teuk) deleted. (id: 56)
The returned quote ID was once again the real quote ID.
Focused Community Achievement regression:
PASSED : 213/213
RC=0
Fast validation lane:
PASSED : 5191/5191
RC=0
Runtime: 179s
The complete suite was deliberately not repeated for MB668.
MB667 had just established the global checkpoint:
13784/13784
RC=0
956s
The current validation policy is therefore being used as intended: focused tests and the fast lane for a contained development round, with the full suite reserved for meaningful checkpoints.
MB668 introduces:
no database schema change
no migration
no new configuration key
no new persistence layer
It builds on data and infrastructure Mediabot already owns.
The recent sequence now forms a coherent feature family:
MB664 → Channel Memory
MB665 → Community Footprint
MB666 → Channel Awards
MB667 → Channel Yearbook
MB668 → Community Achievements
Mediabot is gradually moving from merely storing channel history to understanding how people contribute to that history.
Some people fill the shelves.
Some preserve the stories.
Some become the reason the Room of Requirement has something worth finding. 🏆📚✨
You must be logged in to reply.