v0.4.0 — The whole post, nothing left behind.
fetch message with a link to any photo or video of an album now gives the whole post: every message of the album, in order, with the author’s text. Photograph URLs name only the channel, the post and the photograph, not your account: a fetch keeps nothing on disk, the service saves a photograph the first time it is opened, and another computer can show the saved pictures by the same URLs.
The whole album from one link
- A link to any message of an album gives every message of it, in message order, each with its own text and media. The output is the same whichever photo the link points to, and the author’s text is there even when it sits on another photo.
- Each message is emitted once per run, also when several links point into the same album, such as
t.me/<channel>/…andt.me/c/…links to one post. - A member missing between two others, such as a deleted one, is named in a warning, and the others are still emitted.
media.albumis gone: every message carries its ownpreview_url.
Photograph URLs that name only the post
- URLs are
http://indexit.localhost:17840/preview/telegram/v1/c<channel>/<message>/p<photo>.jpg: nothing in them identifies your Telegram account. - A fetch writes nothing for the photographs it describes. The dashboard counts the photographs on disk; “what needs a look” no longer lists photographs nobody opened, and
/api/v1/unsavedis gone. - On the first request the service finds the channel by itself: a channel it found before, the CLI’s peer cache, your dialogs with the archive, the channel’s username. A channel your account cannot see answers
404; fetch the post on this Mac and open it again. - A post or a photograph gone from Telegram, or replaced by the author, answers
410, never another picture. A saved photograph never reaches Telegram again; a saved file that cannot be read answers503and is never downloaded over. - Photographs of channel and supergroup posts get URLs, private ones included. Private chats and basic groups have no message link and get none;
fetch mediastill downloads them.
Share the photographs between computers
imagesunder[service]inconfig.tomlputs the saved photographs in a folder of their own, such as one in Google Drive. Another computer that runs the service with the same folder shows them by the same URLs, without asking Telegram.- A service writes a photograph next to its place under a name of its own, checks that the JPEG is complete, and never replaces one another computer saved. Conflict copies of the cloud folder are ignored.
Before you upgrade
- URLs written by earlier versions no longer open: they named your account. Fetch those posts again and replace the URLs in your notes. The photographs you saved stay on disk; to keep them, stop the service and move
~/.local/share/indexit/images/a<account>/c…to~/.local/share/indexit/images/c…. Thesources/directory is no longer used; remove it. - After the upgrade, run
brew services restart octolab/tap/indexit.
Upgrade: on macOS, run brew update followed by brew upgrade --formula octolab/tap/indexit. For a manual installation, use a v0.4.0 release archive . Run indexit version to check the installed version. If you use the agent skill, replace it with the new binary’s copy.