# Changelog

Versions follow the date in `VERSION` (YY.MM.DD).

## 26.11.16

- Account blocks now hide posts in profiles, search, threads, quotes and
  streaming, and stop new follows, mentions, replies, favourites, reactions,
  poll votes, boosts and direct messages in both directions. Blocked profiles
  keep only the account's identity and block/report actions. Existing direct
  conversations stay readable, and email and push notifications check for
  blocks before sending. Other accounts on the same server remain reachable,
  even when they share an inbox. Public posts remain available to anonymous
  readers and other instances.
- Static blog pages now leave out unlisted replies. Only replies with public
  visibility are included. Rebuild existing blogs after upgrading to remove
  unlisted replies from pages generated by earlier versions.
- Content warnings now display apostrophes and other HTML entities correctly
  in posts and notifications, instead of showing codes such as `&#39;`.
- Source builds now require Go 1.27.4. Updated the Go dependencies, bundled
  Alpine.js and htmx, and the security tools used in CI. Rebuild existing
  binaries to pick up the Go security fixes.
- With `housekeeping.max_delete_per_run = 0`, status pruning now keeps
  going in batches of 500 until no eligible posts remain. Previously, remote
  pruning stopped after 500 posts and local pruning after 500 per account.
  Positive limits still apply across local and remote posts. Failed deletions
  are left for the next run rather than retried in a loop.
- The inbox no longer fetches a key for an unknown actor's self-delete.
  Requests with a Signature header are acknowledged with `202` and dropped
  when the actor and deleted object are the same URI and the account is absent
  locally. Domain blocks still apply; deletes of known accounts and posts
  still need authentication.
- Incoming HTTP signatures now have their timestamps and body digests checked
  before fetching a public key or verifying the signature. Stale requests and
  damaged bodies can be rejected without a network request.
- Public instance counts on `/about` and the v1/v2 instance APIs are cached
  for 30 seconds, instead of counting the database on every request. The
  admin dashboard still reads fresh counts.
- SQLite reply and quote indexes now leave out NULL entries. This reduces
  their size and avoids a slow query plan when loading RSS feeds. Migration
  007 rebuilds all four indexes at startup and can be slow on large databases,
  especially on SD cards. Allow extra time for the first startup after
  upgrading; later starts skip the migration.
- The interface is now available in Catalan, thanks to Jolupa, who
  translated it. It can be picked in the settings like the other languages,
  and Catalan is also in the list of languages a post can be tagged with.
  Strings added after the translation was made were filled in afterwards and
  are the ones most worth a second look.
- Boosts can be scheduled, to spread them out instead of filling followers'
  timelines all at once. Hold the boost button for half a second, or open the
  post, and pick a time under "Boost later". A quick press still boosts right
  away. Scheduled boosts show up on the Scheduled page next to scheduled
  posts and can be moved or cancelled there. If the post is deleted or
  becomes impossible to boost before then, the boost is dropped. Mastodon
  apps have no notion of a scheduled boost, so the API leaves them out.
- Scheduled posts can now be edited, not just moved to another time. The
  Edit button on the Scheduled page opens the post in the composer with
  everything it had, including the time, and saving puts it back on the
  schedule. Before, the only way was to cancel it and write it again. A post
  that is already being published can no longer be edited.
- Posts can be saved as drafts. The composer has a "Save draft" button next
  to Post, and the new Drafts page lists them, newest first. Opening one
  brings back the text, content warning, audience, language, attachments,
  poll and expiry, and the post it replies to or quotes. Posting or
  scheduling a draft removes it. Everything is a plain form, so it works
  without JavaScript and in text browsers. Drafts live on the server and are
  not shared with Mastodon apps, which have no API for them.
- The image viewer can now move between the pictures of a post. Use the
  arrows on screen, the left and right keys, or swipe on a phone. Before, each
  picture had to be closed and the next one opened by hand. Without
  JavaScript nothing changes: each picture still opens on its own.
- In French the image viewer had no name for screen readers. The apostrophe
  in "Visionneuse d'images" broke the expression that sets it. Translated
  labels are now read from data attributes, so quotes in a translation can no
  longer break the script.
- The Roost theme works better on phones. Post actions fit on one row, the
  back link is a flat row instead of a pill against the screen edge, the
  profile banner and avatar no longer fill the first screen, and the bottom
  bar marks the current page without a filled block.
- Unread mentions and direct messages now stand out from the other unread
  notifications. In Roost the mention colour was the same blue as the unread
  mark, and in every theme their rows took the same background as any unread
  row. Herd and Ink also get mention colours further from their accent.
- Filters set to warn now work on the catch-up page. The filtered posts were
  shown in full, without the filter notice. Filters set to hide already
  worked there.
- Direct message notifications have a magenta edge, an envelope icon and their
  own label, so they stand apart from public mentions.
- Boosts from a followed account can now be hidden from the home timeline,
  with the "Hide boosts" button on their profile or the matching switch in
  Mastodon clients. Their own posts still show up. Boosts already in the
  timeline go away too, and come back if boosts are shown again. The
  `reblogs` parameter of the follow API was accepted but ignored until now.
- Push delivery now follows up to three 307/308 redirects within the same
  HTTPS origin. The Mastodon app relay redirects endpoints without a trailing
  slash; those pushes previously failed after all retries.
- Pushes for favourites, boosts and federated mentions now carry
  `notification_id`. Those jobs were built before the notification was stored,
  so the ID was missing, and the official iOS app showed only the relay's
  placeholder trumpet instead of the notification.
- The bookmark button on boosted posts now stays in sync after refreshing
  the home timeline. Before, it could appear inactive while the post was still
  bookmarked, and clicking it again removed the bookmark.
- Replies no longer show the previous post as unavailable after it has been
  downloaded. Refreshing or reopening the reply now keeps the correct reply
  target in timelines, boosted posts and Mastodon clients. The open thread
  page also updates its reply label as earlier posts arrive.
- Redrew the quote icon. The old one, two squared-off hooks side by side,
  could be read as "SS". It now looks like a pair of quotation marks.
- Logging in with toot from the command line now works. toot opens
  `/oauth/authorize/` with a trailing slash, which returned 404. URLs with a
  trailing slash are now routed like the ones without, as on Mastodon.
- With `require_approval` on, new accounts were created already approved: they
  could sign in at once and never showed up in the approval queue. They now
  wait for an administrator. Accounts registered while the bug was present
  stay approved; check recent signups if the setting is on.
- Filter keywords created from a Mastodon client with `whole_word` turned off
  were saved with it on. Leaving `whole_word` out still means on, as in
  Mastodon.
- Mastodon apps no longer show littleFedi's own notification types (follow
  accepted, unfollows, blocks, emoji reactions, blog rebuilds and others) as
  broken entries, and their unread badge no longer counts them. A client can
  still ask for them with `types[]`, which the notification endpoints now
  honour. `exclude_types[]=pleroma:emoji_reaction` now works too.
- The `user:notification` stream carries only notifications. Before, it also
  sent home timeline posts, which some clients (Tuba) showed as empty
  notifications.
- The instance documents report `image_matrix_limit` as a pixel count, taken
  from `max_image_pixels` and `max_image_dimension`. It was 4096, which clients
  read as 4096 pixels in total and used to shrink uploads to a thumbnail. The
  video limits Mastodon's iOS app requires are there too.
- New client API endpoints: `GET /api/v1/accounts?id[]=`,
  `/api/v1/accounts/lookup`, `/api/v1/accounts/familiar_followers` and
  `/api/v1/notifications/policy`. Mastodon for iOS and Tuba call them.
- Push notifications now reach the Mastodon apps (Mastodon for Android and
  iOS, Tusky, Ice Cubes, Ivory, Mona). Apps that don't ask for
  `standard: true` get the older `aesgcm` encoding, which is the only one
  several of them can decrypt, and every push now carries the access token
  and a numeric notification ID, without which the apps drop it. Form encoded
  subscriptions are accepted, and the subscription ID is a number as the apps
  expect. Subscriptions made before this release keep the old behaviour:
  turn notifications off and on again in the app, or sign in again.
- Polls no longer break Mastodon for iOS and Android. `own_votes` and `emojis`
  are always lists, and `expires_at` uses Mastodon's date format.
- Deleting a post from an app returns the deleted post with its source `text`,
  so "delete and redraft" keeps the text. Deleting it twice returns 404.
- Timeline paging: `min_id` returns the page right after the cursor instead of
  jumping to the newest posts, which made apps skip everything in between when
  filling a gap. A cursor pointing at a deleted post keeps working, and an
  unknown `max_id` returns an empty page instead of the top of the timeline.
  `min_id` and `since_id` work for notifications too.
- `Link` headers are now absolute URLs and keep the other query parameters.
  Followers, following, blocks, mutes, favourites, bookmarks, lists and list
  members send them too, so apps can load more than the first page.
- Media sizes are reported under `meta.original` as well, and remote media
  keep their blurhash and size. Apps used them to lay out images before they
  load.
- Accounts without an avatar or header point to a placeholder image instead of
  an address that returned 404. Accounts also report `uri` and
  `hide_collections`, and relationships `requested_by` and `languages`.
- The default post visibility and language set in the profile are reported to
  apps and used when an app leaves them out.
- `/api/v2/instance` reports the VAPID key under `configuration.vapid` and
  `translation.enabled`. Mastodon for iOS reads both.
- Loading images, avatars and emoji no longer counts against the rate limit.
  Scrolling a busy timeline could hit it, and every API call after that failed.
  An API request over the limit now gets a JSON error with `Retry-After`, and
  unknown API routes return JSON 404 and 405 errors instead of HTML.
- littleFedi now logs a warning when requests come from a local reverse proxy
  that is not listed in `http.trusted_proxies`. In that case every visitor
  shares the proxy's rate limit.
- CORS preflight allows the headers the browser asks for (`Idempotency-Key`
  among them) and exposes `Link` and `Retry-After` to web clients.
- `Idempotency-Key` is honoured when posting: a retried request returns the
  post created the first time instead of a duplicate.
- Tokens from `client_credentials` (the app's own token, before a user signs
  in) are treated as anonymous on public endpoints instead of being refused.
- Filters: `keywords_attributes` works when creating and editing a filter, in
  JSON and form encoding, and the `/api/v2/filters/:id/keywords` and
  `/api/v2/filters/keywords/:id` endpoints are new.
- New endpoints: `GET /api/v1/accounts/search`,
  `/api/v1/statuses/:id/history`, `/api/v1/timelines/direct` and
  `/api/v2/notifications/unread_count`.
- The streaming API accepts the token in `Sec-WebSocket-Protocol`, as the
  Mastodon web client sends it, and tokens limited to `read:statuses` and
  `read:notifications`.
- The "Clear all" button on the notifications page is now called "Delete
  all", in every language, since that is what it does.
- Profile fields: up to four label and value rows on your profile, edited in
  Settings or from any Mastodon app, and shown under the bio on the profile
  page. They are sent to other servers like Mastodon's, and the ones remote
  accounts publish are now shown on their profiles. Remote accounts already
  known get theirs the next time their profile is fetched again. Links work;
  `verified_at` is always empty, as littleFedi does not check `rel="me"`
  links.
- Apps can mute a conversation (`POST /api/v1/statuses/:id/mute` and
  `/unmute`). Mentions, likes, boosts, quotes, edits and reactions in that
  thread stop notifying you.
- Apps can keep a private note on an account
  (`POST /api/v1/accounts/:id/note`). Only you see it.
- Followers can be removed from an app
  (`POST /api/v1/accounts/:id/remove_from_followers`). A remote follower's
  server gets a Reject of the follow, as from Mastodon.
- Conversations can be removed from the list from an app
  (`DELETE /api/v1/conversations/:id`); a new message brings them back.
  `POST /api/v1/conversations/:id/read` works too.
- Saving the profile from an app with an empty bio or display name now clears
  it. Before, empty values were ignored and the old text stayed. The default
  post visibility and language set in an app are saved too.
- MastoBlaster could not read its push subscription: the `alerts` object had
  no `update` key. It is now there, and apps can turn on pushes for edited
  posts. Renaming a list and changing push alerts from MastoBlaster failed
  with 405, because it sends `PATCH`; both endpoints now take `PATCH` as well
  as `PUT`, like Mastodon.
- Three database migrations run at startup. One adds the `standard` and
  `access_token` columns to `push_subscriptions`. One adds
  `accounts.fields_json` and the `thread_mutes`, `account_notes` and
  `hidden_conversations` tables. The last adds
  `push_subscriptions.notify_update`. All of them only add, nothing existing
  is changed, and all can be rolled back.

## 26.10.13

- Alt text changed while editing a post from a Mastodon client (Mastodon web,
  Phanpy, Elk, Ivory, Tusky and others) was silently dropped. It is now saved
  and sent to other servers with the edit.
- Alt text of images already attached to a post can now be edited from the web
  composer.
- When a remote author adds or changes alt text by editing a post, the change
  now shows up here too. Before, the post kept its old description, and stayed
  hidden for anyone filtering out media without alt text.
- `PUT /api/v1/media/:id` can now clear a description, and refuses media that
  is already attached to a post, as Mastodon does. Use the status edit instead.
- Alt text is limited to 1500 characters on the server too, not only in the
  browser. Longer remote descriptions are cut at the same length. The limit is
  reported as `description_limit` in `/api/v2/instance`.
- Media without alt text now report `description` as `null` in the API, so
  clients no longer show an empty ALT badge.
- New Favourites page in the web interface, in the main menu, listing the
  posts you liked, most recent first.
- Paging through `/api/v1/favourites` skipped or repeated posts after the
  first page. It now continues from the last post shown, like bookmarks.
- When the timeline tabs or the top menu do not fit on one line, they now
  show only their icons. Before, some themes cut the last items off or split
  them over two rows.
- Keep the canonical instance actor URL public in secure and allowlist modes,
  fixing a key-fetch deadlock with other authorized-fetch servers.
- With split domains, `/api/v1/instance` now reports the handle domain as `uri`,
  and actors carry a `webfinger` property with their canonical handle.
- Hashtags can now be followed from the search in Settings > Followed hashtags,
  even before any post uses them. Hashtag pages with non-ASCII names, such as
  `#caffè`, now open and follow correctly.
- New `[web] redirect_guests_to_about` sends signed-out visitors from `/` to
  `/about`, and `[web] public_blog_directory = false` puts `/blogs` and its
  sitemap index behind the login.
- `public_local_timeline = false` now also hides the links to the local
  timeline and asks for login on `/public/local` and when scrolling, not only
  on `/`.
- Signed-out visitors could load the federated and bubble timelines through
  the scrolling endpoint. They now get the login page.
- Moved profiles now show the destination and replace Follow with a link to
  the new account. Old posts remain accessible, and cached account data is
  refreshed as soon as the move is saved.
- Move notifications now show and link to the destination, while the account
  name still opens the original profile. Moves by different users stay in
  separate notification rows when grouping is enabled.
- Cached timelines now pick up new posts when blog publishing is enabled,
  without waiting for the page cache to expire. Incoming boosts also update
  open timelines through streaming.
- Profile bios can now contain up to 5,000 characters in the web editor,
  up from 500.
- The notifications page now has a Mark all as read button. 
  Clear all still deletes them.
- Follows imported from CSV are now saved before the upload is confirmed and
  resume after a restart. Settings and the API show progress, existing follows
  and failed lookups. Follow requests and their outgoing deliveries are saved
  together, and only one import can run per account. This uses the existing
  database schema.
- CSV files over `migration.max_follows_import` are now rejected instead of
  being silently truncated. Set the limit to `0` to import the whole file.
- CSV imports now leave an internal notification when they finish or stop
  after a terminal error, with a summary and a link to that import. Retries
  do not duplicate the notice; no email or push is sent.
- Multiple Mastodon API Fixes
- Replies in the web interface now keep the original post's content warning,
  both in the timeline and on the thread page.
- Media can be added to a post by dragging files onto the composer or by
  pasting an image, as well as with the file picker. Files dropped elsewhere
  on the page go to the main composer instead of replacing the page.

## 26.10.01

First public release. littleFedi was used privately for a long time before
this, so there's no point listing every change that led here: the README
describes what's in it, and from now on this file will tell you what changed
between releases.
