Zur Startseite
Versionen
Changelog: Versionen und Änderungen
Hier stehen die letzten Versionen mit allen Änderungen, direkt aus dem Repository geladen. Die Einträge entstehen im Entwicklungsalltag und sind deshalb englisch und technisch gehalten. Eine verständliche Auswahl der Neuerungen steht auf der Startseite.
v2.4.0 Aktuell 19.11.2026 Hinzugefügt (4) · Geändert (3) · Behoben (18)
Hinzugefügt
- Accounts that single sign-on creates have no password anyone knows. They can now confirm deleting the account, changing the e-mail address or the password and migrating an account by signing in again at the provider, and they can set a password this way. Such accounts keep their link until they have a password, and the two-factor settings explain that the provider handles the second factor (Redmine #22).
- Admins can switch on single sign-on with an OpenID Connect provider such as authentik or Keycloak under the new Admin menu entry "Settings", so users sign in with the provider instead of a FediSuite password. Users can link their account, and the privacy policy template names the provider while the login is on (Redmine #22).
- New main menu entry "Statistics" between Analytics and Planner: a report for a week, a month or a year across all connected accounts, including team accounts, or for a single account. A week shows daily figures, a month weekly figures and a year monthly figures for growth, reach, interactions and publishing, with charts, gauges, a comparison with the previous period, and CSV, JSON and print export. Every chart has a data table, patterns and keyboard support, and missing figures show as not available instead of zero.
- Daily figures of every account are condensed into a permanent record, so yearly statistics stay stable and fast, and interactions are kept in it before the retention deletes them. The history of existing accounts is filled in gradually after the update; `ENABLE_STATISTICS_ROLLUP=false` turns this off.
Geändert
- The single sign-on settings and the account card now say up front that the Android app does not support single sign-on and signs in with e-mail and password only (Redmine #22).
- The build stage of the Docker image installs ffmpeg and the SVG tools in a cached layer, so development stacks that run this stage start in seconds instead of downloading them on every start. The build argument `ALPINE_MIRROR` selects a faster package mirror when the default one is slow.
- The Statistics report now follows the reading order audience, publishing, reach and response. Its overview is reduced to five central figures; detailed figures sit in clearly labelled groups, and the publishing work queue is separate from completed output.
Behoben
- PostgreSQL integration tests now run sequentially, so instance-wide settings cannot affect parallel authentication tests in CI.
- The test setup resets the instance-wide OpenID Connect setting before every database test file, so coverage runs start from the same authentication state.
- Coverage thresholds now apply only when the full PostgreSQL suite is available, while local partial-suite reports remain informative.
- The OpenID Connect and Statistics integration tests now honor the current sign-in return format and their real data contracts, so they run consistently in CI.
- The Statistics chart canvas now follows the project formatter, so the release quality check completes successfully.
- The public configuration remains available if reading the optional single sign-on settings fails, mobile discovery no longer promises a login when password login is off, and single sign-on tickets now stay out of server-visible URLs (Redmine #22).
- OpenID Connect provider requests now guard every connection and redirect destination against private targets and DNS rebinding (Redmine #22).
- The message after linking an account to the sign-in provider, and the new confirmation, now appear. The app rewrote the address on sign-in before they could read it (Redmine #22).
- Single sign-on accounts stay linked, and the check before password login can be switched off keeps counting them, when the saved issuer spells the trailing slash differently from the provider (Redmine #22).
- Single sign-on accepts the discovery URL that authentik shows (ending in `/.well-known/openid-configuration`) as the issuer, instead of failing the connection test on the missing trailing slash (Redmine #22).
- With single sign-on set to accept unverified e-mail addresses, an existing account is no longer refused with the misleading hint to verify the address at the provider; the user is told to link the account in the account settings (Redmine #22).
- Statistics now use an A4-specific print layout: every chart stays within the page width, chapters can paginate naturally and individual diagrams remain together.
- Saving Statistics as PDF now waits for the finished, non-animated chart drawing before Chromium captures the page.
- Statistics charts now constrain their SVG canvas as well as their outer container during A4 printing, preventing diagrams from spilling past the right edge or into following content.
- Statistics charts are no longer blank or cut off in the PDF export: they are now drawn at the size of the A4 page when printing instead of keeping the screen size. The print styles now live in their own file.
- The Statistics account picker now shows each account's platform, so identical display names are distinguishable.
- Statistics now preserve post-state events when a draft is scheduled, rescheduled, published or fails, instead of deriving historical figures from the current post state. Profile post totals, reach coverage, quote counts and interaction contacts are included in the report, and its UTC day boundary now matches the stored rollups.
- The best-times heatmaps no longer widen the page on narrow screens.
v2.3.1 14.11.2026 Hinzugefügt (1) · Geändert (1) · Behoben (1)
Hinzugefügt
- Admins can link the privacy policy and the imprint to a page on their own website instead of writing the texts in FediSuite; visitors are sent to that page (Redmine #20).
Geändert
- The German texts say "Datenschutzhinweise" instead of "Datenschutzerklärung", because the latter suggests a binding declaration (Redmine #21).
Behoben
- The best-times heatmaps show cells with few posts in the color of their value with hatching on top, instead of a nearly invisible hatched box, so small accounts and short periods still show their best times. Cells with posts but no engagement are no longer drawn like empty ones.
v2.3.0 12.11.2026 Hinzugefügt (19) · Geändert (11) · Behoben (6)
Hinzugefügt
- New users are guided through a first-run setup after signing in: a short welcome, connecting the first Fediverse account (with the existing connection flow), optional time zone, language and color scheme, and a summary. The setup can be postponed and resumed on any device, existing users are not set up again, and users who already reach an account through a team can continue without connecting one. The footer has a "Setup help" link to open it again.
- Pages that need an account (dashboard, analytics, notifications, archive, calendar, posts and composer) show a clear "Connect your Fediverse account" page instead of error messages while no account is available. The start page says that missing figures are expected while the first import of an account is still running.
- Analytics is now a section with its own submenu: the overview, a campaign comparison, a campaign report, a label comparison and a label report. Campaigns and labels of teams are evaluated for every member who may read the connected accounts.
- Campaigns can have goals for posts, reach and engagement; the campaign report shows their progress, a cumulative timeline, accounts, labels, top and weakest posts and the comparison with the other posts and with the period before, and exports the figures as CSV.
- The label report compares the labels across all accounts, shows how they develop and which pairs of labels are used together, and lists labels that were not used.
- Campaign and label reports can be exported as CSV and raw data (JSON), the campaign report also lists every measured post, and all report pages can be printed or saved as PDF.
- The goal cards of a running campaign show whether the goals are on course at the pace so far.
- A campaign can be duplicated with its goals, labels and scope, and the campaign report builds tracking links with UTM parameters.
- Campaigns can save defaults for the tracking link (source, medium and campaign value) and their own domains; the campaign report uses the defaults, and links to the own domains in posts of the campaign get the tracking parameters when the post is published. The composer shows how many links are affected. All of it is part of the data export and the instance migration.
- The campaign comparison can put two to four campaigns side by side, measure by measure.
- A campaign has a status (draft, running, paused, completed) and an optional goal (awareness, community, website visits, followers, information, custom). Running campaigns still show as upcoming, active or ended by their dates. The campaign list shows the state, the goal and the progress of the published posts towards the post goal. Both fields are part of the data export and the instance migration.
- The label field of the composer uses the same search field with badges, and still creates a new label from the typed text.
- The campaign report names the goal of the campaign and the figures that matter for it, and its edit link opens the campaign form. The campaign CSV files and the Markdown part of the data export include status, goal and tracking defaults.
- The campaign choice in the composer no longer offers completed campaigns and marks draft and paused ones.
- Admins can edit the privacy policy and the imprint in a new "Legal pages" section of the admin area: operator name, address, contact and data processing details fill a German template, or each page can be replaced by an own text. The pages are public at `/?legal=privacy` and `/?legal=imprint`.
- Registration requires accepting the privacy policy. The privacy policy and the imprint are linked on the sign-in screen, in the footer and in the account menu, and the footer links to www.fedisuite.com.
- The footer shows the Liberapay donate button from the instance itself and no longer loads images from liberapay.com and shields.io, so no visitor data goes to third parties.
- The Mastodon profile of FediSuite (@FediSuite@lsbt.me) is linked next to the creator's profile in the footer and on the credits page.
- The page source now carries complete meta tags: description, author, website, repository and license (also as schema.org data), and `fediverse:creator` for the creator and the project, so Mastodon can attribute shared links.
Geändert
- Plugins can no longer provide their own sign-in or registration. They only add or change functions and behavior inside FediSuite; the plugin sign-in, its scaffold preset and the related public config fields were removed.
- Audit log entries are deleted after 30 days. The log is now written in one file per day, and files from earlier versions are trimmed by entry.
- A failed account connection now returns to FediSuite with an explanation (authorization refused, expired sign-in, instance refused access, bot protection, other) instead of a plain error text. The message for an unknown or unreachable instance address no longer suggests that the platform is incompatible.
- The connect form puts the error at the address field, stacks on narrow screens and lets a stuck attempt be cancelled.
- The campaign baseline now compares against posts that belong to no campaign, and posts sent from outside FediSuite are reported separately from untagged ones.
- Deleting a label or campaign now warns that its report is lost and recommends archiving.
- The campaign list counts published and planned posts separately instead of one total, and campaigns and labels link straight to their report.
- Creating and editing a label or campaign now has its own page instead of a form beside the list, so the form is wide enough on large screens and the list shows the overview only. Unsaved changes are guarded when the page is left.
- The labels of a campaign are chosen in a search field with suggestions and shown as badges inside the field, instead of a long list of checkboxes. It works with the keyboard and announces its changes to screen readers.
- The campaign form shows the basics first (name, goal, description, period, status, labels); goal values, tracking defaults and own domains sit in folding advanced settings.
- A copy of a campaign starts as a draft.
Behoben
- Importing a migration archive with a wrong recovery code, or a damaged archive, now shows the explanatory message again instead of a raw encryption error (the Node 26 runtime reports the failed check differently).
- Campaign dates are limited to 2000–2100 and long timelines are capped, so absurd dates can no longer produce huge reports.
- Reports count each published post once even if a post row is duplicated, and the goal card warns when unmeasured posts make reach or engagement progress too low.
- Submenu entries in the sidebar no longer show stray bars next to their labels when hovered; the links now fill the full row (#18).
- FediSuite now identifies itself as `FediSuite/<version>` instead of a `Mozilla/5.0 (compatible; …)` browser string, so instances whose firewall or bot protection rejects browser-like clients (for example mastodon.bawue.social) can be connected again.
- When an instance turns FediSuite away with access denied or a challenge page, the connection now says so and asks the instance administrators to allow FediSuite, instead of reporting an unknown platform. A challenge page is no longer mistaken for a Loops instance.
v2.2.1 09.11.2026 Behoben (19)
Behoben
- In the public analytics card settings, the "Methodology" badge no longer overlaps the figures next to reach; it now sits under the reach value (#16).
- Accounts with the same username on different platforms, such as Mastodon and Pixelfed, can be told apart in the public analytics card settings, because the handle now names its platform (#17).
- Text, borders, buttons and chart colors reach WCAG AA contrast in the dark and the light theme, and every control shows a visible keyboard focus ring (#18).
- On narrow screens and at high zoom the sidebar becomes a menu button with a drawer, so the app needs no horizontal scrolling at 320 px (#18).
- Every page sets the browser tab title and moves the focus to its heading, and every dialog traps the focus, closes with Escape and returns the focus to its opener (#18).
- Forms in sign-in, two-factor, settings, composer, teams and labels name their fields, mark required ones, tie error messages to the field and announce results to screen readers (#18).
- Charts and heatmaps have a text summary, a legend and a data table and no longer rely on color alone (#18).
- The admin user table, calendar, archive and reach list work with the keyboard, and actions that only appeared on hover are always visible (#18).
- The focus no longer drops to the page body after deleting, removing or saving in teams, labels, campaigns, composer media and admin lists (#18).
- Changing a team role or assigning an account no longer fires on the first arrow key press, an apply button confirms the choice (#18).
- Toasts stay as long as their text needs to be read, success messages in settings stay eight seconds, and the browser's own font size setting is respected (#18).
- Navigation entries are real links with an address, so they open in a new tab, and the browser's back and forward buttons move between pages, also with the unsaved-changes question (#18).
- The calendar is a keyboard grid with arrow keys, Home, End and Page up and down, entries open and move with one tab stop each, and a visible switch shows it as a list instead (#18).
- Heatmaps are keyboard grids whose cells are read out with weekday, time, value and number of posts (#18).
- Before a post with media that lacks an alternative text is published or scheduled, a question names the files and leads straight to the missing text (#18).
- The color theme follows the system setting until the user picks one, a "Like the system" choice returns to it, and increased contrast and forced colors modes are supported (#18).
- Languages whose translation covers less than half of the texts no longer appear in the language list, so the page language always matches the text (#18).
- Folding the sidebar now shows the same menu bar with a drawer that small screens use, instead of a second, icon-only navigation, and the drawer brings the fixed sidebar back on wide screens (#18).
- The admin user list and the calendar list show cards instead of a squeezed table when the content area is narrow, and the month grid always shows all seven days (#18).
v2.2.0 09.11.2026 Hinzugefügt (10) · Geändert (4) · Behoben (6)
Hinzugefügt
- Teams let several people work on the same accounts. The person who connected an account assigns it to a team, and the members see its posts, drafts, calendar, archive, analytics and notifications, direct messages included (#12).
- Anyone with an open team invitation gets a notice after signing in, with a link to the teams page where the invitation is accepted, and the invitation mail links there too.
- Admins and editors can publish a public analytics card for each team account and see the team next to it; the card goes offline at once when they lose the role or leave the team. The overview card still adds up only the accounts a user connected.
- Team members are admins, editors or analysts: admins manage the team, editors write, publish and reply, analysts only read.
- Admins invite registered users by e-mail address, and the invited person accepts inside FediSuite. Addresses without an account never receive anything, so closed registration cannot be bypassed, and admins cannot look up the addresses of other users. Each account can create one team, a team has at most 10 members, and an admin can send 10 invitations per hour.
- Labels and campaigns can be personal or shared with a team, and they only apply to accounts of the same scope. Moving an account into or out of a team carries the labels and campaigns of its posts along.
- The teams page guides through the setup: it explains the three steps before the first team exists, shows each team's open steps (invite people, assign accounts) and leads to the connected accounts, where the team is assigned.
- Every team member sets a personal signature such as "(cl)" for each team. It is attached with a single space to every post of the member on the team's accounts when the post is published, also to scheduled posts, thread parts and replies to notifications, and the composer counts it against the character limit.
- The new switch `ENABLE_TEAMS` (on by default) turns the team features off.
- Instance admins now get an e-mail when a newer FediSuite version is published, in their own language (English if none is set), with the changelog of the new version and links to the repository and the update guide. It is sent at most once per day and admin; the new switch `ENABLE_UPDATE_NOTICE_MAIL` (on by default) turns it off (#13).
Geändert
- On team accounts the post list names the author, and posts of accounts where the user is only an analyst offer no edit actions.
- Disconnecting an account removes the posts of every author, and deleting a user keeps the posts and team content that others still use. A user who is the only admin of a team with other members, or who connected an account that such a team uses, cannot delete the own account until the team is handed over.
- Posts can now be scheduled to the exact minute: the time in the composer has separate hour and minute selects, and the minute offers every value from 00 to 59 instead of steps of 15 minutes (closes #11).
- The instance migration covers personal accounts, labels and campaigns only; team accounts and team content stay out of it.
Behoben
- An account id that is not a number now gets "account not found" on the analytics routes instead of a server error.
- Disconnecting the default account no longer makes the account list fail to load, which made the remaining accounts look gone.
- Every user who has accounts now always has a default account: at the start, accounts without a usable default get the oldest one, and disconnecting an account, removing a user or leaving a team assigns a new default at once. Resetting the default in the settings or the mobile app picks the oldest account instead of leaving none (#14).
- A login the server cannot accept (expired after 30 days, forged or from before a key change) no longer leaves the web interface stuck on an error message: the server now answers with 401, so the user is signed out and sees the login form. Opening `/logout` signs the browser out as well. Signing out, by button, at `/logout` or because the login became unusable, now also ends the session on the server (`POST /api/auth/logout`), so a token that was copied before stops working. The error text for the account list was missing in all languages and is added (#14).
- The server log now names the reason when a login token is refused (expired, invalid signature, wrong algorithm), at most once per user and ten minutes and without the token, so sign-in problems can be traced (#14).
- The HTTP redirect library `follow-redirects` is updated to 1.16.3, which closes a high-severity advisory about credentials following redirects.
v2.1.2 26.10.2026 Behoben (2) · Hinzugefügt (7)
Behoben
- Migration imports now reserve enough disk space for uploads, decrypted archives and restored media, including uploads without a declared size. Canceling during the password confirmation no longer starts an upload afterwards.
- The migration interface now builds correctly with the cancellation regression coverage enabled.
Hinzugefügt
- Users can move to another FediSuite instance with an encrypted archive of everything not covered by the historical import: posts, drafts, media with alt texts, labels, campaigns and preferences. The import can be repeated safely, so posts of accounts connected later are added without duplicates.
- The migration export and import now run in the background with progress, a queue, cancellation and e-mail notification for longer jobs. The finished export is downloaded manually within 72 hours, and every refusal explains the reason and what to do next.
- Import and export refuse data that would exceed the storage limits before anything is written, and the export warns about attachments that could not be included.
- The migration now carries the follower history, follow events and interactions of the connected accounts, because they cannot be fetched again. Existing rows are never overwritten.
- Former accounts without a counterpart, for example after a Fediverse account moved to a new handle, can be assigned to a connected account, and matching ignores spelling differences of the address and the platform type.
- A user can import an archive of another FediSuite account of the same instance. Only importing one's own archive on the instance it came from is refused.
- Exports read from one consistent snapshot, a database copy gets its own instance id, media copies of an import that crashed are cleaned up, and users with an authenticator app confirm export and import with a code.
v2.1.1 24.10.2026 Behoben (1) · Geändert (8) · Hinzugefügt (1)
Behoben
- The social image of public analytics cards could not be rendered in the container image because `rsvg-convert` and a font were missing.
Geändert
- The public analytics profile settings now live with general preferences instead of account-security settings.
- Composer controls now explain themselves on hover, use a warning icon for content warnings and place visibility choices in a distinct group.
- Attached JPEG, PNG and WebP images can now be cropped, resized and re-encoded locally before posting, individually or with shared settings for several images.
- Media controls stay visible in the composer, stored draft images can also be edited, and the smallest interface hints now use a readable size.
- Composer media previews now use larger icon controls, and image editing reads the original stored file instead of its thumbnail.
- The image editor now also previews and measures the original stored image rather than its thumbnail.
- Composer media remove controls are now more compact while keeping their clear close icon.
- Campaigns and labels in the composer now use a dedicated, more actionable workspace.
Hinzugefügt
- Users can opt in to public, shareable analytics cards, one for each connected account and one that adds up all accounts, each with a private preview, crawlable Open Graph page and social-card image. The cards show reach first and a daily trend line under every figure, and state that they are Fediverse analytics together with the platform of the account.
v2.1.0 10.10.2026 Hinzugefügt (1) · Sicherheit (1) · Geändert (6)
Hinzugefügt
- New "Federation" tab under Analytics: it shows which other instances favourite, boost or reply to your posts, how much of the resonance comes from outside your own instance, how the number of active instances develops, and which posts reached the most instances. It uses the interactions already recorded for the community analysis and is switched off together with it (`ENABLE_COMMUNITY_INTELLIGENCE`).
Sicherheit
- Updated the dependencies `proxy-addr` (IP spoofing via IPv4-mapped IPv6 addresses behind a trusted proxy) and `source-map-js` to their patched versions.
Geändert
- Fixed seven test files that failed without a `JWT_SECRET` in the environment or depended on the default app address. The test suite now runs without extra setup. The behavior of the application does not change.
- The update notice for admins now offers "How to update" (linking to the update guide) and "View Changelog" instead of the Docker tag list, in the language of the interface where documentation exists (closes #9).
- Tidied up the source code documentation and the tests: shorter and more varied comments, file headers in every file, and granular tests merged into tables. The behavior of the application does not change.
- Merged duplicated helper functions on the server and in the web client into shared modules, and wrote the code documentation and test titles with more variety. The administration pages now use the translated interface texts in all five languages.
- Removed empty and redundant `@param`/`@returns` tags from the source documentation and added a quality check against empty tags. The behavior of the application does not change.
- Corrected the developer documentation: `.env.example` lives in the self-hosting repository, and the installation, backup and plugin guides now cover `ACCOUNT_ENCRYPTION_KEY` and the UID 1000 folder permissions.
v2.0.2 05.10.2026 Hinzugefügt (1) · Behoben (1)
Hinzugefügt
- A post can be marked with a text format (plain text, Markdown or HTML) for Pleroma and Akkoma accounts: the server stores it with posts and drafts, shows it in post lists and the edit data, and sends it when publishing. The account lists show which formats each account supports (closes #7).
Behoben
- Added the French interface texts that were still missing (archive, multi-account posting, reach tips and credits) and translated "Active" and "Inactive" in the two-factor settings.
v2.0.1 04.10.2026 Behoben (2)
Behoben
- A newly uploaded image remains visible after draft autosave, and stored attachments count toward the composer limit. Post lists show the original image if its thumbnail is missing (Redmine #6).
- The containers now refuse to start, with a step-by-step message and a link to the upgrade guide, when `ACCOUNT_ENCRYPTION_KEY` is missing, empty, still the example value or malformed. The check runs before the first database statement, so the database stays untouched.
v2.0.0 03.10.2026 Hinzugefügt (19) · Geändert (38) · Behoben (28)
Hinzugefügt
- Connected-account credentials are now encrypted in the database with a separate required key; startup migrates existing values and refuses a missing or incorrect key.
- E-mail verification and password-reset tokens are stored as SHA-256 digests; verification links expire after 24 hours and are single-use. Previously issued links are migrated without exposing the tokens again.
- Login sessions expire after 30 days, including sessions issued before this change.
- Added drafts: a post can be saved without a time, for one or several accounts at once, with a stage (idea, in progress, ready), and the scheduler never publishes it.
- Added a Drafts tab to the posts page and autosave to the composer, which shows whether the draft is saved.
- Added a question before leaving the composer or the page with changes that are not saved: save and leave, discard, or stay.
- Added the content calendar as a page of the planner, with month and week view, filters for account, platform and status, a detail drawer and moving scheduled posts by drag and drop with a confirmation.
- Added "Publish now" and "Try again" for scheduled and failed posts, and routes to turn a scheduled post back into a draft or copy any post into a new draft.
- Added labels and campaigns: internal tags and groupings for posts that are never published or turned into hashtags, managed on their own planner pages and usable as filters in posts, calendar and archive.
- Added content recycling: an archive post can be made into a new draft, old posts that reached clearly more than usual get the badge "Interesting again", drafts can be marked as evergreen, and the composer warns about similar posts.
- Added content insights: the analytics tab "Content" compares media, links, text length, visibility, language and labels, shows combinations that stand out, and explains how it was calculated.
- Added the card "Insights for this post" to the composer and markers for good time windows to the week view of the calendar.
- Added the community analysis: the analytics tab "Community" shows interacting, new and returning accounts, the return rate, the kinds of interaction and how many accounts come back often.
- Added the recording of who interacted with the posts of Mastodon-compatible accounts, which the community analysis needs.
- Added the switches `ENABLE_DRAFTS`, `ENABLE_CONTENT_CALENDAR`, `ENABLE_CONTENT_LABELS`, `ENABLE_CONTENT_RECYCLING`, `ENABLE_CONTENT_INTELLIGENCE` and `ENABLE_COMMUNITY_INTELLIGENCE` (all on by default) to turn the new features off.
- Added the average replies to the comparisons and the label table of the content insights.
- The personal data export now includes labels, campaigns, their assignments, draft details and the interactions of other accounts, and says when a long list was cut to the newest 10,000 rows.
- Recorded interactions of other accounts are deleted after 730 days by default; `ENGAGEMENT_RETENTION_DAYS` changes the period.
- Added "sign out of all other sessions" to the API, and the setting `TRUST_PROXY` for the number of trusted proxies.
Geändert
- Plugin login redirects now require a matching browser nonce, even when an older server omits one; the Docker image runs as a non-root user and pins its Node base image by digest.
- The response CSP now also restricts base URLs, embedded objects and form targets; script and resource directives remain deferred for trusted-plugin compatibility.
- The CI database smoke test uses the same disposable encryption key as the integration tests.
- Bug report links in the app now open the support site so reports reach the right place.
- Restructured the navigation around the workflow of a post: Dashboard, Analytics, Planner (Calendar, Posts, Composer, Campaigns, Labels), Archive, Notifications, Settings (Account, Connected accounts, Preferences) and the admin area. Old addresses still lead to the pages that replaced them.
- Split the settings into three pages in a submenu of the sidebar.
- Editing a post now happens on the page of the composer instead of in a dialog, with every field filled in and a way back to the previous page.
- The composer card "Scheduling" is now "Publishing", and labels and campaign sit in a card of their own in the right column.
- The actions of a draft are buttons with text instead of a menu, and the drafts list keeps its rows, selection and focus while it reloads.
- The pages Labels and Campaigns show the list next to a form that stays in view.
- The attachment files of a post are no longer deleted when it is published, so a published post can be used again as a draft.
- The tab bar of the analytics scrolls sideways on a narrow screen.
- The notice of the operator is a calmer card with an icon, and every user can hide it; it shows up again as soon as the operator saves or changes the notice.
- The filters of the calendar sit in a panel behind one "Filters" button that counts the active filters, so the toolbar above the calendar is a single clear line.
- The unsaved-changes dialog is also used on logout, and the save status says "Unsaved changes" as soon as the text changes.
- Delete confirmations use the shared accessible confirm dialog and are translated.
- Animations are switched off for users who prefer reduced motion.
- Time windows are only marked when they clear a stricter bar that accounts for the many windows tested at once, and the label trend, the data basis and the composer hints use the same rules and sample size as the other comparisons.
- The content and community tabs load their data only when opened and show a clear message with a retry button when loading fails.
- Community insights only tell new from returning accounts when the recording reaches back at least one period before the period, and the time series marks days or weeks that lie only partly in the period.
- Spanish, French and Italian community texts follow the renamed wording ("accounts", "return rate"), and percentages are written the way each language does.
- Planned times are read strictly (ISO 8601 with time zone, at most five years ahead) in every route that takes one; invalid, empty or legacy values are rejected.
- Split many large files (sidebar, post creation, archive, posts list, publishing, profile routes, calendar and composer parts) into small modules with tests; the behavior is unchanged except for the points listed here.
- The CI also runs for the branch `feature/fedisuite-2.0` and installs ffmpeg for the thumbnail tests.
- Updated the duplicate-code checker used in development to a version without the known `braces` vulnerability, so the dependency audit of the CI passes again.
- Changing the password, e-mail address or second factor, resetting the password and admin changes to an account now end the other sessions of that account.
- Unknown accounts and wrong passwords get the same answer at login, repeated failed logins are slowed down per account, and password, e-mail, account deletion, data export, e-mail verification and single sign-on are rate limited.
- An authenticator code can no longer be used twice, wrong second-factor answers are limited per login, passwords longer than 72 bytes are refused instead of being cut off, and new passwords are hashed more strongly.
- Single sign-on checks the ID token completely, refuses unverified e-mail addresses and accounts with a second factor, and respects the registration setting; the last admin can no longer delete their own account.
- Responses forbid framing, unknown API paths answer 404 as JSON, broken JSON gets a clean error, and the time zone, `days` and `limit` parameters are validated.
- Answers from remote instances are limited in size and total time, the outbound address check also covers NAT64, 6to4, Teredo and IPv4-compatible addresses and proxies, and new instance connections must use https.
- WordPress follow-up addresses are only requested with the access token when they belong to the connected instance, and disconnecting an account or deleting a user revokes the access token at Mastodon-compatible instances.
- Posts to Mastodon-compatible instances carry an idempotency key, and the server runs in UTC and reads timestamps without a zone as UTC, so planned times no longer shift on hosts in another time zone.
- Rate limits during an account refresh pause the remaining optional steps and give the instance a cooldown; interaction recording adapts to instances that refuse the page size, the notifications or the paging position.
- Historical imports stop after twelve failed retries with a visible message, and scheduled posts rejected by a rate limit or a refused connection are retried up to three times.
- Replies no longer distort the content insights, language and content warnings come from every archived post, and drafts from archive posts limit and check the attachments they download.
- Post and notice HTML is sanitized more strictly, plugin sign-in is protected against login fixation, links and redirects from remote data only open for http(s) addresses, and fallback avatars no longer contact a third-party picture service.
- The signed-in app waits for the server configuration and treats a missing one as "larger features off"; contrast, touch targets, toasts and the save status of the interface were improved.
Behoben
- The boost and reply rate chart now labels both curves and names each percentage in the hover details, so the values can be identified at a glance.
- Posting activity dates now stay in the correct weekday row across time zones, so calendar labels match the hovered dates.
- Saving a draft no longer turns a post that was planned or published in the meantime back into a draft, and parallel saves no longer delete files another save still uses.
- Removing the first account of a multi-account draft no longer drops its labels and campaign, and drafts for accounts added later inherit the evergreen mark and the archive source.
- Reopening a draft no longer loses the values of plugin fields in the composer.
- The unfiltered post list no longer starts with drafts and no longer exposes an internal grouping key.
- Reposting no longer deletes the attachments of the published copy, takes the attachments from the platform when stored files are gone, and answers server errors with a generic message instead of raw platform text.
- Files uploaded with a refused or failed post request are removed again, and editing a post in place is atomic.
- Ids and label lists are validated strictly, and an invalid campaign or archived value gets a clear error.
- Mentions imported from the archive keep their server, and the similar-post warning links to the post on its platform where the address is known.
- Copying a part of a thread as a draft is refused, while reusing an archive post still works.
- PeerTube title statistics count only published posts.
- Moving a scheduled post to a time that is not in the future is refused by the server.
- The week view of the calendar shows its seven day columns again instead of a single one.
- The lists of posts and of the archive no longer show a blue-green background behind each row.
- The calendar refreshes by itself while a post is being published, always shows the platform, opens on the correct day in every time zone, and a drop on the own time slot or outside the grid no longer creates a bogus move.
- Double-clicking "Post now" while a draft is still saving no longer posts twice, and discarding changes no longer leaves a stray draft behind.
- A failed label or campaign creation keeps what was typed, and archive and post rows have a proper toggle button so screen readers can reach their buttons and links.
- Deleting the account and changing e-mail, password or time zone no longer fail with a server error when the request has no body.
- The community key figures, table and time series agree on new and returning accounts, and the new/returning bar always adds up to 100 %.
- Made a calendar test wait for the focus after a deleted post instead of reading it too early, which made the CI fail on slow runners.
- Editing a post can no longer make the server copy or download the same attachment over and over, and a post that is being published can no longer be deleted.
- Planning a post for a time more than five minutes in the past is refused, and posting right now no longer leaves a window in which the scheduler could publish the same post twice.
- Search terms are limited, broken character references in imported posts no longer cause errors, and uploads are limited in total size, field count and thumbnail time.
- A post is only removed from the archive when the instance really answers "not found", and the similarity warning no longer reports a post as similar to itself.
- A draft that the platform refused no longer hangs in the composer, and refused autosaves retry with growing waits.
- Replies to other people's posts are no longer treated as original posts in the archive search and the recycling hints, and two admins can no longer remove or demote each other at the same moment and leave the instance without an admin.
- A post that failed once gets its automatic retries back after being retried, edited or withdrawn, and a WordPress import reads at most 50 outbox pages per run and no longer restarts when a run ends on the last page.
v1.7.3 30.09.2026 Geändert (1) · Behoben (7)
Geändert
- A rate limit without a `Retry-After` header now puts the work off for a minute, not for the few seconds the worker had guessed.
Behoben
- Fixed the reach queue growing without a limit: an account now holds at most `REACH_QUEUE_PER_ACCOUNT_LIMIT` open jobs, where every call used to add that many more and one account could fill the queue with thousands of jobs.
- An instance that keeps rate limiting the reach worker is now left alone by all workers for a minute, doubling up to 15 minutes, and its jobs are no longer moved one by one in the database; before, every worker asked it again every few seconds.
- Fixed the reach workers claiming next to nothing for minutes: the jobs with the highest priority often belonged to one instance that was busy or limited, filled the batch and were thrown away, while other instances waited. The limits of the instances now apply before the batch is cut.
- Fixed an account refresh that ran into its time limit carrying on in the background, writing data and queueing reach jobs while the account stayed marked as unreachable. The refresh is now cancelled, and the timeline step stops asking for more pages when there is not enough time left for another one.
- Accounts marked as unreachable that answer with 401 or 403 now switch to "reconnect" at once instead of being retried for ever, and plugin accounts whose token was revoked (Bluesky) are recognised by the message.
- Pixelfed requests over HTTP/2 now follow the request timeout and the cancellation of the refresh.
- A cancelled Vernissage refresh no longer moves the cursor of its notifications.
v1.7.2 30.09.2026 Hinzugefügt (8) · Geändert (14) · Behoben (15)
Hinzugefügt
- Added an Interactions tab to the dashboard, between Growth and Engagement, with one chart each for favourites, boosts and replies per day, every chart with a summary and a data table for screen readers; plugins can place widgets on it too.
- Added Víctor Fancelli Capdevila to the credits (`CREDITS.md`, `CREDITS.de.md` and the in-app credits page) for checking, correcting and completing the Spanish translation.
- Added a rotation that reads a few of the posts fetched longest ago again every hour, posts with likes, boosts, replies or quotes first, so the counters of old posts stay current; `STALE_POST_REFRESH_BATCH_SIZE` sets how many (0 switches it off).
- Added a note to the reach methodology page, in all languages, that instances delete the boosts of old posts and that FediSuite therefore only lets reach grow.
- Logged how many old posts each account refresh read again.
- Added step-by-step timing to the log: a refresh that takes 20 seconds or more, or runs into its time limit, is logged with the time of each step, request and rate limit wait (`SLOW_REFRESH_LOG_MS`).
- Added log lines for the reach queue (its state every ten minutes, the result of every batch, jobs that gave up), for old posts that were removed or skipped, and for accounts that are retried or reachable again.
- Added a load lab (`scripts/load-lab/`): a made-up fediverse with 60 fake instances in different states, a seeder for a production-sized database, a scenario runner with a time jump and reports, and a QEMU VM setup without any outbound network, so FediSuite can be tested at live size without touching live data or the real fediverse.
Geändert
- Renamed the start page card "Top Posts" to "Top posts by reach" (in all languages), since it is ranked by net reach now.
- Removed the unused top posts call of the web client and split its contract test into one table per area.
- The best posts card on the start page now shows the five posts with the most net reach instead of the most favourites, with net reach, favourites, boosts and replies under each post instead of beside it.
- The overview tab now has one list, "Top 20 posts", in the reach widget, ranked by net reach and sortable by gross reach, favourites, boosts or replies; the separate top posts card and its count selector are gone.
- The postings page now opens on the published posts instead of the scheduled ones, which were empty for everyone who does not plan ahead.
- Split the dashboard data hook, the overview widgets, the post analytics routes and the dashboard and postings tests into small files with tests; the behavior is unchanged except for the points above.
- The README, the contributing guide and the translating guide no longer call the Spanish translation unchecked, since a native speaker has now proofread it; French still needs a native speaker.
- Likes, boosts and quotes of a post can no longer decrease, and neither can the boosters stored for its reach: the reach of a post is now calculated from every booster ever seen, because instances delete old boosts while the boost counter stays.
- Posts older than 90 days are calculated for reach again as soon as they gain likes, boosts, replies or quotes, so new boosters of old posts are collected while an instance still lists them.
- Split the reach worker, the thread rollup, the snapshot job and the cleanup of empty posts into small files with tests, and gave the touched files real descriptions; the behavior is unchanged.
- Documented in the translating and contributing guides that new texts go into every language file, not only English and German.
- A recent post is only calculated for reach again when its counters changed or after 24 hours (`REACH_RECALCULATE_AFTER_HOURS`), no longer every time it is fetched again, which removes most of the repeat work of the reach queue.
- Split the account refresh worker into claiming, refreshing an account and the timer, and the API calls with rate limit handling into one shared wait, with tests.
- The responsive UI scale now starts at 100% below 1600px and reaches 140% (instead of 160%) on 4K viewports, with the steps in between scaled in proportion.
Behoben
- Fixed the best posting hours and weekdays by engagement showing twice, once as a plain tip and once as an "underused" tip with the same numbers; now only the fitting one is shown.
- Fixed the top posts request failing with a server error for a negative limit; it now returns one post.
- Fixed the reach tips showing twice: the best reach time and the best reach weekdays were offered once as a plain tip and once as an "underused" tip with the same numbers, now only the fitting one is shown.
- Fixed a saved dashboard tab that no longer exists leaving the dashboard without a tab.
- Fixed the app navigation test that checks the account handed to the dashboard, which failed on slow CI runners because it did not wait for the default account to be chosen.
- Limited the CI tests to two workers and let the image build start only after the checks, so a push no longer overloads the shared build server.
- Restored, once per account, the reach of posts whose stored boosters had been lost from their reach numbers.
- Fixed the retry delay of failed reach jobs, which waited twice as long as intended (10, 20, 40 and 80 instead of 5, 10, 20 and 40 minutes).
- Failed refreshes of posts named by like and boost notifications are now logged instead of being ignored.
- Added the missing French translation of the quote note on the reach methodology page.
- Limited the rotation over old posts to the time an account refresh has left and gave each of its requests a timeout, so a slow instance no longer pushes the refresh over its time limit and shows up as unreachable.
- Fixed accounts that were marked as unreachable after a timeout never being refreshed again until their owner opened the dashboard: they are now tried again every six hours, and once a day after three days, and a successful refresh clears the mark.
- The statuses named by like and boost notifications are now read within a time budget and oldest first, so a slow instance no longer keeps a refresh busy until it runs into its 45 second limit and the account is wrongly marked unreachable.
- Every request of an account refresh now has a timeout of 20 seconds, and an instance that asks to wait longer than half the refresh time limit (a rate limit) postpones the refresh instead of counting as a failure.
- The reach worker now works off the jobs of different instances at the same time, gives every job a time limit and a short request timeout, and puts the jobs of an instance that asked to wait off instead of waiting for it, so one slow or rate-limited instance no longer holds a worker for minutes.
v1.7.1 28.09.2026 Hinzugefügt (3) · Geändert (40) · Behoben (26)
Hinzugefügt
- Added PDF attachment support to the composer for vutuv accounts, since vutuv started accepting PDFs on posts on 2026-09-28. Every other platform still only accepts images/videos as before.
- Expanded development-branch CI with database and image smoke checks, dependency and shell audits, coverage reporting, and a report-only code quality review that can become strict after refactoring.
- Added ESLint, Prettier and a TypeScript type-check for the server's JavaScript code as an enforced quality gate, now run automatically on every push and pull request so problems are caught before they reach `main`.
Geändert
- Split the 816-line file of shared type definitions into small files per area (plugins, posts, accounts, analytics and others); the types are imported exactly as before.
- Split the 641-line account response parsers into small files per report (accounts, performance, audience, hashtags, notifications); the checks are unchanged.
- Split the 846-line file of platform helpers (names, badges, supported features, composer profiles) into small files, described the composer profiles of all platforms in one table, and recorded the full output of the helpers in a test so nothing changed.
- Split the 643-line admin routes into files for users, plugins, plugin settings and system information, and added tests for the plugin settings, the admin plugin routes and the exact changes made to users.
- Split the 675-line post editing route into small services (lookup, form, attachments, saving, edit source), which also fixes uploaded files staying behind when the post id in the request is invalid, and added tests for the edit source, rejected edits and published edits.
- Split the 839-line platform request file into token errors, login state, refresh guard, OAuth tokens and request executors, removed an HTTP/2 retry branch that could never run, and added tests for the token exchange, the refresh and the PeerTube, Misskey and Pixelfed request paths.
- Split the 890-line plugin loader into the plugin context, boot, record, translation and state files, removed a restart flag that was always false, and added tests for the context handed to plugins, scanning the plugin directory, translations and switching plugins at runtime.
- Split the 879-line plugin scaffold into files for the presets, the manifest, the translations in five languages, the server code, the web files and the readme, and recorded everything it writes in a test so the generated plugins stay the same.
- Split the 910-line historical import into a paging loop with one small description per platform, the follow events, the follower history, the finish and the failure handling, and added 54 tests that cover every platform, the mail, the audit log and the retry rules.
- Split the 957-line database initialization into the base schema and eight files of migration steps in the same order, and recorded every statement it sends in a test so the schema stays exactly the same.
- Split the 986-line app root into hooks (session, plugin pages, data, settings, shared selection, update notice) and small components (verification screen, notices, footer, pages), added 92 tests for it, and fixed that a plugin page named in the address fell back to the dashboard before the plugin list had loaded.
- Split the 625-line user administration page into a list hook, an edit hook and small components (toolbar, table, row, accounts, edit dialog) and added 20 tests for it.
- Split the 787-line postings page into hooks and small components (tabs, toolbar, list, row, edit dialog) and added 42 tests for it.
- Split the 800-line accounts page into hooks and small components (cards, connect panel, import and login-error badges) and added 47 tests for it.
- Split the 769-line settings page into one small component per card (e-mail, password, time zone, colour scheme, language, plugins, account deletion) and added 53 tests for it.
- Split the 811-line dashboard into tab, chart-data and hero-number modules plus one small renderer per widget, and added 57 tests for it; the post-count helper for accounts is now shared between the dashboard and the accounts page.
- Split the 713-line dashboard start page into a report loader, number cards, best posts, charts and tips, reusing the formats and growth figures of the dashboard, and added 57 tests for it.
- The interface tests now wait up to five seconds for the page to change and may run up to twenty seconds, so a busy CI runner no longer makes them fail by chance.
- Shortened the longest functions in the newly split pages (accounts, postings, settings, dashboard, user administration) so they stay within the hard limits of the coding standards.
- Shortened or simplified more functions in the split server code (thread splitting, focal points, plugin helpers, scaffold texts, token exchange, post editing, import) and added 54 tests for the composer payload helpers.
- Split the repost route into a lookup, an attachment copier and a publisher, and added 5 tests for it.
- Simplified the conversion of notifications from Mastodon, Misskey and Vernissage, documented it, and added 92 tests for it.
- The Docker image and the CI now run on Node.js 26 instead of Node.js 20, and the Node type definitions were updated to match.
- Split the 1,268-line API client into a shared request core and small files per area (sign-in, accounts, posts, user, administration), removing about 85 copies of the same request code, and added a contract test for every call. Refreshing the account counts now reports a failure instead of hiding it.
- Split the 2,378-line post composer into small, documented parts (pure functions for the rules and the sending, hooks for the state, small components for the view) and added about 340 tests for them; how the composer looks and behaves is unchanged. The account choice also no longer updates endlessly when the list of accounts is rebuilt on every render.
- Added automated tests for every route group (authentication, users, admin, posts, ownership) and for the scheduler, and split the scheduler into small functions so a pass can be run and tested directly.
- Database tests can no longer be skipped silently in CI, the test database is migrated once per test run, and the HTTP application is built in `server/create-app.js` so tests can exercise all routes without starting the server.
- Added frontend tests that render the sign-in screen (login, second factor, registration, password reset link) and the application shell in a simulated browser and check what the user sees, what is stored in the browser and what is sent to the server. Tests that need browser storage now behave the same on Node 20 and on newer Node versions with their own `localStorage`. The test tools `@testing-library/react`, `@testing-library/dom` and `@testing-library/user-event` were added as development dependencies.
- Extended the type check to the newly written server tests and helper scripts, and documented the extra tools the tests need (`git`, `curl`, `jq`).
- Releases are now protected by a gate: a tag only builds, publishes and deploys if it is a plain `vX.Y.Z` version, matches the version file, lies on `main` and the same files passed CI. Container images and the release action are pinned by digest, and the release notes no longer mix up versions such as 1.7.1 and 1.7.10.
- Added hand-written runtime validation (no schema library dependency) for the 17 most complex API responses the frontend receives (plugin discovery and settings, reach summary/posts, notifications, post analysis, paginated posts/archive search, post edit source/status, user profile/sessions, public config, and the admin version/plugins/users endpoints), replacing unchecked `any` casts with parsers that throw a clear error on a malformed response instead of passing bad data silently into the UI. Centralizes the previously five-times-duplicated `isRecord()` type-guard pattern into one shared validation module with its own unit tests, plus dedicated tests for every new response parser.
- Extended that same runtime validation to every remaining `api.ts` method (auth/registration/login/2FA, per-account analytics and hashtag breakdowns, account insights, notification actions, post create/publish/edit/update/repost, plugin settings, the global notice banner, and the admin plugin-toggle/instance-registry endpoints), including correctly handling several analytics fields PostgreSQL can return as numeric strings instead of numbers. The only method left deliberately untyped is `providers.connect`, since each plugin provider defines its own response shape. The new parsers' own tests caught two pre-existing bugs before release: a notification's actor and a plugin's web manifest were both validated as required when the API can omit them entirely.
- Split the dashboard's ~1,750-line widget-rendering switch into 22 documented, independently typed widget components grouped by tab, moved its ~19 near-identical data-fetching effects into a single `useDashboardData` hook, and added the project's first component-level tests (45 render smoke tests covering every widget's loading/empty/populated states) alongside a locale-aware formatting module with its own unit tests.
- Replaced positional post-list and composer API arguments with documented request objects, centralized multipart post-body construction, and removed unsafe non-null assumptions from cross-post failure summaries. Publish-status polling now receives one named options object, and stored publish errors are narrowed from `unknown` before use.
- Consolidated repeated insight evidence construction, plugin-handler cleanup branches, and post-edit JSON-array parsing into documented shared helpers. Plugin boot and validation errors now live in separate class modules, and migration SQL is wrapped without changing its statements.
- Split the 1,700-line dashboard tip formatter into documented, tip-specific renderer modules, replaced its eight positional dependencies with a named options contract, and gave built-in insight evidence an explicit TypeScript transport type. Embedded example posts are now validated before the UI renders them; contract and extraction-equivalence tests protect all 57 built-in tip variants.
- The tenth server refactoring pass extracted plugin-provider routes, the mobile dashboard query bundle, and all platform-specific post-refresh workflows into documented route, service, and worker modules, leaving `server/index.js` as a small composition root. PostgreSQL-backed contracts now cover successful refreshes across Mastodon, Misskey, PeerTube, WordPress and Vernissage as well as the existing Loops failure path, protecting provider behaviour during the structural split.
- The ninth server refactoring pass extracted the 2,580-line insights engine from `server/index.js` into documented metric loaders, small topic evaluators, plugin and persistence adapters, a dedicated route, and a periodic worker. PostgreSQL-backed contract tests now cover insufficient samples, representative generated and persisted tips, the mobile dashboard integration, the current manual refresh contract, and account-refresh timeout behavior; generated tip sets are also replaced atomically so a failed insert cannot leave a partial result behind.
- Continued splitting the monolithic `server/index.js` into focused modules (`config.js`, `db.js`, `app.js`, `lib/`, `services/`, `middleware/`, `providers/`).
- Audited all eight refactoring passes for missing documentation and leftover duplication. Added a `@file` header to every module that was missing one (72 files across `lib/`, `services/`, `routes/`, `workers/`, `middleware/`, `providers/` and `server/index.js` itself), explicitly documenting side effects and disambiguating similarly-named modules. No behavior change. Confirmed no dead code was left behind by the refactoring; the remaining duplication found (mainly a repeated account-ownership check across many routes, and a few smaller copy-pasted helpers) is tracked for a future cleanup pass rather than fixed here.
Behoben
- Workers now wait until the application has finished database initialization and responds as healthy before starting; a failed migration stops startup instead of exposing a partially migrated schema.
- The best posts on the dashboard start page now show readable text, with characters such as `&` decoded and script text left out, and late answers for an account that is no longer selected are ignored.
- A success message under a settings form no longer makes a newer error message disappear early, and the fallback texts of the settings forms are now translated.
- A finished import that loaded no posts no longer shows a stray "0" on the account card.
- Error logs no longer contain access tokens, client secrets, authorization codes, passwords or database row values. Failed requests to other servers are logged with their status, address and a shortened answer, without headers and request bodies.
- A repost is no longer published twice when the scheduler runs while it is still being published, and a restarted server process no longer takes back posts and import jobs that another process is still working on: only work that has not changed for 30 minutes counts as abandoned now.
- The server no longer connects to private network addresses when an instance is connected or when the attachments of a remote post are copied for a repost or an edit, and it no longer sends the account token to other hosts than the account's instance. Operators with an instance in their own network set `ALLOW_PRIVATE_INSTANCE_URLS=true`; copied attachments are limited to 50 MB.
- The post list no longer turns a server error (for example HTTP 500 or 503) into an unreadable validation message. The signed-in area now shows the message of the server, as it already did for the account list.
- Fixed the one-minute limit for requesting a new e-mail login code not applying when the server and the database run in different time zones.
- Fixed scheduled posts being set one hour off when the chosen time lies around a daylight saving switch, and made the scheduler's time zone conversion independent of the browser's date formatting.
- Fixed the notification list of an account failing to load completely when a single notification came without a date, which some platforms send. Such notifications are now shown without a time.
- Fixed uploaded files being able to run as a web page in the app's own origin (for example HTML or SVG disguised as an image). Uploads are now checked by their actual content and stored with the matching extension, `/uploads` serves only known image and video types inline, and all responses forbid content sniffing.
- Fixed the single-sign-on login redirect being able to send the fresh session token to another website through a crafted `redirect_url`. The redirect now stays inside the app, and the token travels in the URL fragment so it no longer appears in server or proxy logs.
- Fixed API authentication accepting any correctly signed token, including the short-lived two-factor login challenge token, without a session check. Only tokens of an active session are accepted now, so tokens from before session management existed require one new login.
- Fixed a cross-site scripting hole in the plain-text post previews of the archive and dashboard, where markup from a remote instance could run script in the app; previews are now built from an inert document.
- Fixed the Fediverse OAuth callback trusting a forged `state` parameter, which allowed attaching an account to another user; states must now be issued by the server, expire after 15 minutes and work only once, and Loops no longer places its client secret in the authorize URL.
- Restored connected accounts, account selection, follower figures, and notifications after API validation rejected nullable account and post fields. Account loading now survives an independent post-summary failure and reports loading errors visibly.
- Fixed two-factor login silently never applying its intended clock-drift tolerance, caused by an outdated option name for the underlying TOTP library; logins could fail for users whose device clock had drifted even slightly.
- Fixed a file upload weakness where a crafted filename from the client could influence where the uploaded file was written on disk.
- Fixed a third-party OAuth error being logged together with the account's client secret in plain text.
- Fixed an admin-permission check that silently treated a failed database lookup as "not an admin", without any record of the failure.
- Fixed a startup issue where a failed database migration was only logged, letting the server start anyway against an inconsistent database.
- Fixed several places where background/background-like tasks (imports, notifications, connecting or managing accounts) could fail silently without any visible error.
- Fixed two slightly-off Viridis colormap constants in the dashboard charts that could never be represented exactly as floating-point numbers.
- Updated `nodemailer` to resolve several known security advisories (arbitrary file access, domain-validation bypass, a denial-of-service vector).
- Fixed a 2FA login challenge that could be reported as already expired minutes after being created whenever the server process ran in a non-UTC timezone, caused by comparing a database timestamp using the wrong timezone assumption instead of letting the database itself decide.
v1.7.0 27.09.2026 Hinzugefügt (3) · Geändert (2) · Behoben (5) · Credits (1)
Hinzugefügt
- Added a full-text archive search over every post FediSuite has ever seen for an account, not just the ones scheduled through FediSuite itself (#15). Matches anywhere inside a word, not just at the start, so results narrow as you type and German compound words are found from any part of them. Search the current account or all connected accounts at once, optionally include private and direct posts (off by default), and jump straight from a result to the post on its original instance. Results show the same expandable metadata and reach figures as the rest of the dashboard.
- Added eight new tips based on the actual net-reach calculation instead of only favourites, boosts and replies: your best time window and weekdays for reach, whether media or text posts reach further for you, a warning when your reach is almost entirely your own followers with barely any boosts from outside, and a reach-decline alert. These are always shown above every other tip under Übersicht → Tipps.
- Added cross-posting to the composer: a new checkbox lets you select several accounts at once instead of just one. Character limit, media rules, content-warning and visibility support then use the strictest combination of every selected account, so the same text is guaranteed to be valid everywhere. Publishing sends the post to each selected account independently (same as an existing thread already being several independent posts), so one account failing never blocks the others, and only the accounts that failed stay selected afterwards for an easy retry. Works for scheduling as well as posting immediately. Accounts with genuinely incompatible media requirements (e.g. one image-only, one video-only) are called out with a clear message instead of silently picking one side. Plugin-provided composer fields are only shown with exactly one account selected, since there's no defined way to merge two different plugins' custom fields.
Geändert
- Updated the net-reach formula to also count quotes (Mastodon's quote-post feature, available since Mastodon 4.5), matching an update FediWings' Ralf Stockmann made to keep reach numbers comparable between FediWings, FediSuite and other tools using the same formula. Quotes are weighted the same as boosts. Only the Mastodon family reports a quote count; reach for a post with zero quotes is unaffected. Already-analyzed posts are automatically recalculated over time as the reach queue works through them.
- Acknowledged FediWings as FediSuite's sister project: added a "FediWings – the sister project" section with a link to try it on the Reach Methodology page, and a footer link next to Credits and Bug Reports, mirroring the FediSuite mention FediWings already carries on its own homepage and methodology page.
Behoben
- Fixed follower and following counts showing as -1 and throwing that same -1 into totals and growth calculations when an account's instance reports that count as private (#14, affects GoToSocial accounts in particular). The count now shows as "hidden" instead of a number, and is left out of growth comparisons instead of being treated as a real value. Existing accounts and follower-history entries that already had a stored -1 are cleaned up automatically on the next start.
- Fixed accounts on platforms without notifications support (Loops, PeerTube, WordPress) being unselectable in the account picker under Notifications, so there was no way to see why. They're now selectable like any other account and show a clear explanation instead of notifications for the currently selected account.
- Fixed the account selected under Notifications not following the account selected everywhere else in the app (Dashboard, Übersicht, Archiv). Notifications now shares the same session-wide account selection as the rest of the app instead of resetting to the default account on every visit.
- Fixed the "Schedule" button in the composer looking like a plain link with no background, unlike every other primary action button. It now matches "Post now" exactly.
- Fixed a database migration step being silently skipped when it hit a deadlock during a fresh deploy (the app and every worker start at once and can genuinely collide on the same table), which had left a large number of already-analyzed posts stuck on the previous net-reach formula. That specific case has been repaired directly; migration steps now retry a few times on a deadlock or serialization failure before giving up, instead of treating it the same as a step that simply doesn't apply anymore.
Credits
- Credited Elena Brescacin for the complete Italian interface translation on the in-app Credits page and in `CREDITS.md`/`CREDITS.de.md`, which had been missing it.