Документация fedtail on fedtail

Быстрый старт

Mon, 01 Jan 0001 00:00:00 +0000

В каждом релизе fedtail приложение собрано одним исполняемым файлом (внутри уже упакованы Python и библиотеки Qt) — ничего дополнительно ставить не нужно.

Способ 1. Одним файлом без установки (рекомендуется)

Linux (x86_64)

Debian 12 и новее, Ubuntu 22.04 и новее и тому подобное. Команды — для последнего релиза, 0.16.0:

# Скачать и сделать исполняемым:
curl -LO https://github.com/eugene-vereshchagin/fedtail/releases/download/v0.16.0/fedtail-0.16.0-linux-x86_64
chmod +x fedtail-0.16.0-linux-x86_64

# добавить в меню с иконкой (и выйти), потом запускать
./fedtail-0.16.0-linux-x86_64 --install-desktop
./fedtail-0.16.0-linux-x86_64

Возможности fedtail

Mon, 01 Jan 0001 00:00:00 +0000

Состояние на версию 0.17.0 (в работе). Это полный перечень возможностей fedtail: что делает каждая, чем включается и выключается, с какой версии есть, на каком API или протоколе стоит и как то же самое сделано у других клиентов. Здесь же — планы и то, от чего отказались, с причинами.

Справочник настроек

Mon, 01 Jan 0001 00:00:00 +0000

Справочник по всем ключам конфига, таблицами по главам.

Что за возможность стоит за ключом и как это у других клиентов — список возможностей.

Как устроен конфиг

Здесь все настройки — со значениями по умолчанию и пояснениями. Поменяй, что нужно, и перезапусти fedtail. Программа этот файл только читает и никогда не перезаписывает.

fedtail и другие клиенты

Mon, 01 Jan 0001 00:00:00 +0000

Те же возможности, что в полном списке, — одной матрицей на главу: есть ли такое у других клиентов. ✓ — есть, пусто — нет или неизвестно. Сведения — из README и заметок к релизам (осень 2026 года) и общих знаний, без проверки каждого вживую; подробности и оговорки — в столбце «У других» полного списка.

Альфа-тестирование и багрепорты

Mon, 01 Jan 0001 00:00:00 +0000

Спасибо, что пробуете fedtail! Программа находится в стадии активной разработки, поэтому нам очень важна обратная связь от пользователей.

Что посмотреть в первую очередь

Треды деревом. Откройте любое обсуждение (кнопка «Тред» или клик по времени поста): оно отображается древовидной структурой, с номерами комментариев /1 /2 …, целиком — ответы, которые ваш сервер не получал, подтягиваются напрямую с сервера автора по ActivityPub через пару секунд.
Ничего не теряется. Закройте ленты клавишей Esc, оставьте программу на ночь: утром слева появятся счётчики новых постов, новое ждёт непрочитанным, а лента откроется ровно там, где вы остановились.
Ответы мне и подписки на треды (кнопка «Подписаться» над тредом или команда S #abc в командной строке): ответы в отслеживаемых тредах приходят, даже если вас прямо не упомянули.
Уведомления: проверьте через меню ≡ → «Отладка» → «Проверить уведомление».
Командная строка внизу окна (Ctrl+L, введите ? для справки) — привычный интерфейс для пользователей Point.im.
Несколько аккаунтов: правый клик по своей аватарке позволяет переключать профили.
Темы оформления: ключ ui.theme в конфиге (меню ≡ → «Открыть конфиг»).
Суточный прогон без перезапуска. Оставьте окно открытым на длительное время. В логе пишутся строки trend и possible leak, помогающие отслеживать утечки памяти.

Как сообщить о проблеме

Если что-то пошло не так:

История изменений

Mon, 01 Jan 0001 00:00:00 +0000

Все релизы, свежие сверху. Журнал ведётся по-английски — так он лежит в репозитории. Файлы каждого релиза — на странице релизов.

0.16.0 — 2026-10-19

Faster reading deep into big lanes: stored posts are paged from where the last page ended instead of skipping the newer ones again each time, and text is pulled out of a post’s HTML with patterns compiled once. Ctrl+F “in every lane” goes through lanes that share a source together, each post parsed and matched once — on 20 000 stored posts it takes 0.4 s instead of 0.9 s; “Deeper” and long lanes gain the same way.
A click on the time slider of a video or an audio jumps right there; it used to move only one step towards the click, and only dragging the handle really seeked.
Sending no longer gives up after 30 seconds on a slow server: it waits post.send_timeout (90 s). When the answer still doesn’t come, fedtail looks among your latest posts first — the post was usually made, only the answer lost — and treats it as sent if it’s there. If it can’t tell, the message says “maybe sent: look before retrying” instead of a raw “Read timed out”. Each post carries an Idempotency-Key: Mastodon gives back the post already made instead of a double when the same text is sent again.
Ctrl+F “In every lane”: a tick in the find bar searches everything stored in every lane at once; the counter says which lane the match is in, and the next match opens its lane and loads it down to the post. Ctrl+F pressed again in the find bar goes to the next match, as in a browser (Enter, ↓ and F3 still do too).
The point theme closer to point.im: square avatars, the name bold in dark blue with @address · date under it, the post’s #id under the text on the left with the number of replies (#a3f | 4), the buttons on the right, a hatched grey band behind the lane’s and the new post’s title, solid and clearer lines between posts, a dark “Create” button. New theme keys for any theme: shape.avatar_shape (circle, square, rounded), shape.card_header = "stacked", shape.short_id (header, footer), shape.actions_align (left, right), shape.rule (solid, dashed), shape.header_stripes, shape.header_bar (a band above the title strip, point.im’s dark top bar), colors.primary / on_primary, colors.header, colors.header_bar, colors.name.
The lane’s and the new post’s title strip is tinted with the theme’s accent in every theme (colors.header left at “auto”), with a 3 px band of the accent above it (shape.header_bar, 0 turns it off); bnw and contrast keep a white strip under the band. Lines between posts in “rule” style are solid by default (terminal keeps its dashes).
“Add to list” for someone you don’t follow: the lists are dead now, not just greyed — a click on them does nothing at all (it used to send a request the server refused and stall the window). While fedtail is still asking the server whether you follow them, the lists are dead too, with “Checking…” above them, instead of looking clickable.
Video is decoded by the processor by default (ui.video_decode = "software"): on some cards Qt’s hardware decoding fails (“CUDA_ERROR_INVALID_VALUE”, “more than 32 decode surfaces”) and the video stutters or stalls. "hardware" brings the old way back.
The opossum is gone from the icon and About: it comes from an official Telegram sticker pack, and its artist says the rights are Telegram’s, not theirs to give. The drawn thread bubble is the icon again (in the theme’s colours with ui.themed_icon); ui.app_icon is gone with it.
“Activity” counts as seen what came on screen, like the other lanes, checked when you scroll or come back to the window. It used to mark everything once, on opening — rows far off screen too — and a window in the background at that moment left the newest unread for good.
The debug theme: for finding what’s wrong, not for reading. Each state of a post in a loud frame of its own — unread, “on screen but not all of it yet” (not counted read yet), the j/k cursor, what Ctrl+F found, the post you came to — plus the keyboard focus and disabled buttons. shape.debug = true turns the same on in any theme of your own.
“Copy handle”: a button in a profile, “Copy handle @…” in a post’s ⋯ menu (the author, and the booster of a boost) and on the “boosted by” line. Always the full @user@server — people of your own server come as a bare user, your server’s name is added.
⋯ → “Call into the thread…”: a reply to that post with only “@” in it and the people list open — pick who, add a word, send. They get a notification and open the thread at home; no links with service ids. The thread’s others aren’t mentioned; the call has its own draft. post.invite = false hides the item.
≡ → Debug → “Federation status”: how your server is doing — what it runs, how many answers and how fast, polls and the live stream — and what keeps failing that isn’t the client’s doing: what the server can’t do, who waits to go into a list, and every request that keeps getting 404/410/401/timeouts, on your server and on other servers, grouped (ids folded), counted, with when it last happened and what it most likely means. Live while open; “Copy” as text for an issue; “Count anew”. Only what this run saw: nothing is asked of the network for it, no queries or tokens are kept.
Federation status: who waits to go into a list is named (my server is asked who an id is when no post of theirs is here), linked to their profile in a tab, with why they wait — a follow request unanswered, not followed (refused or withdrawn), or followed and going in with the next refresh.
A slow answer about direct conversations no longer fails the whole poll (“Read timed out” on screen, the lanes not fetched): it is only a nicety, skipped till next time.
Someone waiting to go into a list is tried only once they’re followed; while the follow request waits nothing is asked, and once it’s refused or withdrawn they’re let go. (A refused follow was retried with a 404 every ten minutes, for a month.)
What the server hasn’t got — blocked domains on GoToSocial, the notification policy — is asked once a run, not on every silence refresh. Muted and blocked lists no longer ask for an empty second page.
A post’s ⋯ menu is built when it opens, not with every card: two dozen actions and submenus per card were most of a lane’s widgets and of its drawing time; what it shows (unread, subscribed, pinned) is how things are at that moment.
The log’s trend line gives the rate over the whole session beside start → now (and the last minutes apart): 245 → 763 MB over a night read “+1950/h”, the rate of three minutes.

Архитектура и дизайн

Mon, 01 Jan 0001 00:00:00 +0000

fedtail спроектирован для тех, кто помнит Juick и Point.im и устал от хаотичной ленты с обрывками чужих разговоров в современных микроблогах.

Ключевые архитектурные принципы

Ничего не дёргается. Открыл ленту — стоишь на первом непрочитанном. Пришло новое — позиция не меняется, просто растёт счётчик. Читаешь строго по хронологии, как RSS.
Каждый ответ знает, на что он отвечает. Над ответом — полоска с началом исходного поста, клик открывает весь тред деревом.
Ленты строго разделены. Люди отдельно, боты отдельно, ответы мне отдельно от прочих упоминаний.
Приватно по умолчанию. Новый пост — только подписчикам. Ответ никогда не может быть публичнее исходного.
Любое поведение — ключ в конфиге. Окна настроек нет и не будет. По умолчанию поведение настроено продуманно; привычный режим «как у всех» включается простым флагом.
К чужим серверам — без вашего токена. Всё, что fedtail подтягивает с сервера автора напрямую по ActivityPub, запрашивается анонимно: удаленный сервер видит только IP-адрес.
Ядро не зависит от GUI. Интерфейсы — подключаемые плагины: классическое окно на Qt, терминальный TUI, браузерный веб-интерфейс.
Один профиль — один аккаунт. Второй аккаунт — второй профиль (--profile); при необходимости несколько профилей объединяются в одном окне (ui.merge).
Взрослые разбираются сами (режим arts). Режим в честь @arts, создателя Point.im: контент отображается без навязчивой внешней опеки.

Устройство ядра и компонентов

Ядро (fedtail/core): полностью изолировано от графического интерфейса. Общается с фронтендами асинхронно через события (events) и futures.
Хранилище данных: локальная реляционная база данных SQLite (~/.local/share/fedtail/<профиль>/). В ней хранятся закэшированные посты, связи тредов, состояние прочитанности и подписки на треды.
Цикл опроса (Polling): периодический сбор обновлений с инстанса по Mastodon API с защитой от дубликатов и сохранением курсоров.
Сборка тредов (Thread Reassembly): если в треде отсутствуют промежуточные комментарии (потому что ваш домашний сервер их не зафедерировал), fedtail анонимно запрашивает недостающие ActivityPub-объекты непосредственно у сервера автора.
Фронтенды (fedtail/frontends):
- qt — основной десктопный интерфейс на PySide6 (Qt).
- tui — легковесный текстовый консольный интерфейс.
- web — локальный HTTP-сервер со встроенным веб-интерфейсом.
- cli — утилиты командной строки (fedtail lanes, fedtail show, fedtail tail, fedtail post).

Что будет в 0.17.0

Mon, 01 Jan 0001 00:00:00 +0000

Это ещё не вышло: так выглядит раздел 0.17.0 в журнале изменений на сегодня. Последний релиз — 0.16.0. Журнал по-английски, как в репозитории; до выхода что-то может поменяться.

fedtail took GoToSocial 0.22 for Mastodon: its version says only “0.22.1+git-…”. Now it reads the instance document’s source_url and GoToSocial’s own keys, and asks the server’s nodeinfo when still unsure — so × in Activity hides here instead of asking the server, and the probe says right what GoToSocial can’t. Translating is read from the newer instance document (Mastodon said “no” before when it could).
Server info → What it can do: “Copy” (a Markdown table, for a bug report or a chat), “Save…” to a file, Ctrl+C copies the selected rows.
≡ → Server info has a “What it can do” tab: “Check” asks the server about two dozen features with harmless one-item GETs (a few seconds, in the background) and lists yes / no / closed to me / unclear, with the limits; the last check is kept. The answers also decide which buttons fedtail offers.
Help: in the comparison tables the header row stays on top while the rows scroll under it, so a ✓ always says whose it is.
The paper theme comes with its fonts: PT Serif and PT Mono (ParaType, SIL OFL 1.1) are in fedtail, nothing to install.
× on a row of Activity on GoToSocial: the server can’t dismiss one notification (only clear them all), and fedtail used to ask it anyway — a 404 in the log, the row stayed, and “Clear” went missing until a restart. Now × hides the row here (and stays hidden after the next fetch); on Mastodon it goes from the server too. It never mutes anything: new ones of the kind come as before. The tooltip says which it is.
The font over the theme’s and the system’s: ui.font (a list works: the first one installed), ui.mono_font for #ids. Fonts needn’t be installed: .ttf / .otf in ~/.config/fedtail/fonts/ are picked up at start, and a theme can bring its own ([font] files, next to its .toml).
Muting a thread works on GoToSocial: the server can’t, so fedtail mutes it itself — the thread’s mentions are dropped as they come (replies there tag everyone in the thread by themselves), even replies under posts fedtail never saw, and what came before leaves the lanes. It used to say “Your server can’t do that” and hide the item; now the item is always in the ⋯ menu, and on Mastodon it asks the server as well.
Reply with quotes: ⋯ → “Reply with quote” puts the post (or what’s selected in it) into the reply as a > quote; a right click on selected text → “Quote in reply”. With the reply already open the quote goes where the cursor is, so a long post can be answered sentence by sentence without copying. post.quote_prefix.
Web: the ≡ menu (write, my profile, refresh, all read, help, keys, about) and a post’s ⋯ menu (reply with quote, subscribe / leave / mute the thread, copy the link, delete my post); q replies with a quote. A reply shows the whole post it answers: select a piece, “❝ Quote in reply” puts it at the cursor. The picture viewer goes through the post’s pictures with ← / → and the side buttons.
Terminal interface: p shows the profile for real — the screen used to scroll its header away as the first post was highlighted, and what stayed looked like a lane. Lanes by keyboard: [ / ], 1…9, h into the lane list (j / k move there), l back; Tab now really goes between lanes and posts. “Activity” and “Follow requests” show their rows (they were empty: they aren’t post lanes); a / d answer a request. Pictures drawn with half blocks: a post’s first one small in the lane (tui.pictures, tui.picture_rows), v — all of them full screen, ← / →, o — the original in the browser. Needs Pillow (python3-pil).
Unsubscribing from a thread mutes its mentions too (subs.leave_mutes, on): leaving used to stop “Subscriptions” only, while auto-tagged replies kept coming.
The opossum holding its own tail is back: the app’s icon (ui.app_icon) and the picture in About. It is a sticker from an official Telegram sticker pack.
The config’s reference comes in English too: config.example.en.toml lies next to config.example.ru.toml (the old config.example.toml goes). A new config is written in the desktop’s language; --update-config and --rebuild-config keep the language your file is in.
Help inside: ≡ → “Help” opens it as a panel over the lanes, like the compose panel — the contents on the left, search through it all, Back and Forward. Short pages, each ending in “In detail →” links into the full feature list and the settings reference, which come with it and work offline. In Russian and in English.
≡ → “What’s this?”: point the mouse at a button and get the longer story — what it does, which config key changes it, where the help says more. For the session from the menu, or from the start with ui.whats_this. Neither has a key: F1 is next to Esc. The hint is a window of its own, beside the cursor and never under it: a long Qt tooltip there was hidden and shown again round and round until the window froze.
The docs come in Russian and English, docs/ru/ and docs/en/: the feature list now says since which version each feature is there, and fedtail next to thirteen other clients is one matrix a chapter (comparison.md). All of it, the config reference and the shared pieces of the READMEs are built by tools/docs_build.py; a test keeps them in step.
The database no longer grows for ever. Every storage.gc_hours (6) fedtail forgets posts nothing points at any more — no lane, followed thread, activity entry or reply draft; boosted and quoted posts and parents of kept ones up the thread stay, and so do your own posts and anything stored in the last storage.grace_hours (48). A forgotten post is fetched again when needed; short ids are kept for good. The file really shrinks (incremental vacuum; an older file is converted once, at the first start — it may take a moment). If it is still over storage.max_mb (1 GB), lanes get shorter until it fits and grow back later. New [storage] options; storage gc: lines in the log.
Pictures that didn’t come no longer stay blank until a restart. When the server answered with an error twice (busy, restarting, still fetching a remote post’s media), fedtail asks again by itself in 1, 5 and 30 minutes for the cards still waiting, and a card that gave up gets the picture when it comes. The log now says the HTTP status (“HTTP 503”) instead of just “HTTPError”.
The web interface, rebuilt: a “Write” button (and ✎ on a phone) opens a composer with a content warning, who sees it, the language and a character count; drafts are kept in the browser. Replies start with the right @names and never go wider than what they answer. Pictures in a grid with a viewer, video, gifs and audio; a picture that doesn’t come says so, links to the original and is tried again later. Polls with bars and voting, link cards, quotes, custom emoji, a profile’s header, fields with ✓ verified, follow / requested. “More” at the end of a lane loads older posts. The command line has a line of its own. Lanes slide in on a phone; light and dark follow the system.
Inside: the terminal, the TUI and the web interface work on fedtail’s own data model (fedtail/model, fedtail/core/view.py) instead of the server’s JSON — stage 2 of docs/PROTOCOLS.md; so does the Qt window, all of it. The Mastodon API itself lives in fedtail/protocols/mastodon/ behind a protocol interface (stage 3), and what the server can do is kept in one place (stage 4): a button the server refuses goes at once, and stays gone after a reconnect. Nothing changes in what they show, except that the web page and fedtail post -v say “followers” (private still works).