Skip to content

fix: use the comment's actual age for the day count in the crosspost reply - #86

Merged
Toldry merged 2 commits into
masterfrom
claude/actual-elapsed-days
Oct 16, 2026
Merged

Toldry merged 2 commits into
masterfrom
claude/actual-elapsed-days

Conversation

@Toldry

@Toldry Toldry commented Oct 16, 2026

Copy link
Copy Markdown
Owner

Requested by Querent · project thread

Before: the reply under a crosspost said the source comment was "written 90 days ago" and that the bot "waited 90 days", taken from PHASE3_WAITING_PERIOD, even when less time had passed, as with --process-one.

After: both use the number of days since the source comment was actually written, in every language (all locales share the one {timedelta_string} placeholder). 0 and 1 days are not special-cased.

How: reply_to_crosspost computes time.time() - source_comment.created_utc and falls back to the waiting period only if the comment has no created_utc. Added a test across all locales, a CHANGELOG entry, and updated the phrasings-test docstring and AGENTS.md wording.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XxZW1s4sP8XVBUkskD7BLk


Generated by Claude Code

…reply

--process-one skips the Phase 3 waiting period, but the reply still said the
comment was written, and the bot waited, PHASE3_WAITING_PERIOD days ago.

Co-Authored-By: Toldry <toldry@gmail.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XxZW1s4sP8XVBUkskD7BLk
@Toldry Toldry self-assigned this Oct 16, 2026
@Toldry
Toldry merged commit 70335e8 into master Oct 16, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants