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

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

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

Что будет в 0.17.0

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

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

The server’s rate limit is kept to: fedtail reads its X-RateLimit headers, keeps quiet once fewer requests are left than two poll rounds and a reserve, until the server’s window starts anew, and asks nothing while it is spent. One line in the status bar says until when — instead of a “429” for every lane, every round (as on GoToSocial with a few lists, the live stream waking the poller every few seconds).
Trying a theme from the menu no longer freezes the window for seconds: the lanes out of sight let their cards go first (drawn anew when opened), and the tabs out of sight are rebuilt when they come into view.
Less freezing after a poll: the lanes and their unread counts are worked out in the poll thread before the window hears of news, and unread counts are cached until a lane or a read mark changes — the sidebar asked every lane after every event, reading thousands of stored posts between two frames (250 ms to a second).
fedtail --layout single|columns|split and --theme NAME: the layout or the theme for one run, the config untouched.
Five themes in the spirit of messengers, for ui.layout = "split" above all: qip-retro (QIP Infium’s pale blue), qip-modern (QIP 2012, flat), mra and mra-blue (the Mail.ru Agent’s orange and blue), psi. They write a post as a message: “Name (15:25:43 23/06/2007)” over it, mine and the others’ in colours of their own — shape.card_header = "chat", colors.chat_me / chat_them, words.chat / chat_date for any theme. Their icons and colours are fedtail’s own, not anyone’s skin.
Help gets a “Server and federation” part under its contents: About the server, What it can do (the probe) and Federation status open on its right side, as pages of the same panel — the settings-like window of Psi or QIP, only for what to read, not to set (settings stay a file).
ui.layout = "split" ("qip", its first name, is still understood), the first step of a messenger-style layout (docs/LAYOUTS.md): the lanes in a narrow roster window of their own, as in QIP, Psi or the Mail.ru Agent — who I am and what’s new in Activity on top, a search line, the lanes in folding groups “▾ Personal (2/9)” (with something new / all), each with its count, a line of its newest post and its author’s face. fedtail starts with the roster only; a double click (or Enter) opens a lane in the messages window — the main one, without the sidebar, its tabs drawn as tabs; closing the last tab closes it. Under the tabs, an input line is always there: in a thread’s tab it answers the thread (a private talk stays private), in a lane’s tab it writes a new post; who sees it, a warning, and ⤢ for the full Compose window. At the bottom of the roster, the menu and the accounts (@me ▾); ⚙ (or a right click on empty space) sets how it looks: compact — a line an item, without the header, the search or the buttons, only where there’s something new, without groups, above other windows (ui.roster_on_top says how it starts). Closing the roster closes fedtail (to the tray with ui.close_to_tray). Followed threads and private talks stand there as contacts of their own (“Threads”, “Talks”, the freshest ui.roster_threads): who began it and how, or who is in it.
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.
Every built-in theme comes with its fonts (all SIL OFL 1.1, all with Cyrillic, nothing to install): PT Serif in paper, IBM Plex Mono in terminal, IBM Plex Sans in nord, Source Sans 3 and Source Code Pro in night and solarized, Open Sans in point, Arimo in juick, Comfortaa and Nunito in pink, PT Sans in contrast, Fira Mono in bnw where DejaVu is missing. ui.fonts chooses whose: the theme’s (default), the system’s, or your own (ui.font, ui.mono_font — any of these by name too).
× 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.
Fonts of your own: ui.fonts = "custom" with ui.font (a list works: the first one there), 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).

Roadmap on fedtail

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

Что будет в 0.17.0