Repository navigation
feat(bot): welcome a new group and warm it up after its reveal - #98
Merged
Merged
Conversation
A group that added maply heard nothing until the next post, so it took the bot for dead. Now the moment maply joins, the group gets one welcome: its home panel with what maply is, the post time and the reveal in the group's zone, and what comes next. Before the post that is the morning's first place; during the day it is today's real round, which the scheduler already sends within seconds; after the reveal it is a warm-up, since the group would otherwise wait until tomorrow. The warm-up plays the archive's newest day, closed in every zone, from a startapp payload signed for the group and the day (version 3). Each player's game is their own day from the free game's archive, so it counts in no day's table, world, profile, streak or rating, and nobody who answered that day can take it. warmup_game ties those games to the group, and a new warmup job sends the group's table an hour later. One warm-up a group, ever. A supergroup where maply is not an admin is asked once, in the welcome, for the right to pin, with a link that requests just that right; the morning post then does not ask again. /start in a group shows the warm-up's button while it runs. Closes #57 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A group that added maply heard nothing until the next post, so it took
the bot for dead. Now the moment maply joins, the group gets one welcome:
its home panel with what maply is, the post time and the reveal in the
group's zone, and what comes next. Before the post that is the morning's
first place; during the day it is today's real round, which the scheduler
already sends within seconds; after the reveal it is a warm-up, since the
group would otherwise wait until tomorrow.
The warm-up plays the archive's newest day, closed in every zone, from a
startapp payload signed for the group and the day (version 3). Each
player's game is their own day from the free game's archive, so it counts
in no day's table, world, profile, streak or rating, and nobody who
answered that day can take it. warmup_game ties those games to the group,
and a new warmup job sends the group's table an hour later. One warm-up a
group, ever.
A supergroup where maply is not an admin is asked once, in the welcome,
for the right to pin, with a link that requests just that right; the
morning post then does not ask again. /start in a group shows the
warm-up's button while it runs.
Closes #57