generated from exteraGramPlugins/pluginBase
lyuksovannyyandClaude Opus 5.5
af23d2e682
Publish plugin / publish (push) Successful in 3s
With an offset the newest analyzed message is usually outside the loaded window, so placement asks the chat to load it first. That path could leave the view away from the card while offset 0 always worked: - Placement gave up after ~3 s (25 x 120 ms) and asked for the anchor only once. scrollToMessageId drops the request while waitingForGetDifference, and a load can be superseded. It now waits ~10 s and re-requests every ~2 s. - Loading a far anchor makes ChatActivity run its own postponed scroll, and a cache-then-server reload can re-scroll or replace the list. Either can land after the jump. Settle checks at 0.25/0.7/1.5/3 s re-jump if the card row is outside the visible range, and re-place the card if a reload dropped it. They stop as soon as the user drags the list. Also logs each run's count/offset, the fetched id range, pre-stream failures, load requests, placement and jumps to the diagnostics file, since bulletin-only errors previously left no trace. Verified on device with count 1000, offset 1000: anchor loaded on the first retry, card placed after it and the chat jumped there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
15 lines
363 B
JSON
15 lines
363 B
JSON
{
|
|
"id": "chat_summaries",
|
|
"name": "Chat Summaries",
|
|
"description": "Summarize the last N messages (with offset) in any chat, group, channel, or topic using AI.",
|
|
"author": "@lyuksovannyy",
|
|
"version": "1.1.1",
|
|
"icon": "exteraPlugins/1",
|
|
"app_version": ">=12.5.1",
|
|
"sdk_version": ">=1.4.4.3",
|
|
"requirements": [
|
|
"requests",
|
|
"debugpy"
|
|
]
|
|
}
|