Skip to content
Releases
A line drawing: the main branches of Anahita Services and Anahita Web, the day’s two releases tagged and tied together, over what changed.

Anahita Services v1.2.8 to v1.3.3 and Anahita Web v1.2.4

Anahita Services v1.3.3

Upgrading

  1. One migration, activitypub_quotes: two tables, for the quotes asked of other servers and the stamps given here, run by the migration job as any upgrade's are (Upgrading).

Added

  1. Quotes on Mastodon are quotes (roadmap row 156, FEP-044f): a quote names the post it quotes, with the stamp that its author let it, and Mastodon shows it inside. For a post here, the stamp is this installation's, served at /ap/quotes/:uuid; for a post elsewhere, its author is asked with a QuoteRequest, and the quote is sent again with their stamp when they accept, or without the quote when they refuse. Every post says who may quote it (interactionPolicy.canQuote), by its quote policy, and somebody elsewhere who asks to quote a post here is answered by it.
  2. Quotes from Mastodon are kept as quotes (roadmap row 156): approved by a stamp, or of their own author's post, they show the quoted post inside, read and kept here if it was not.

Anahita Services v1.3.2

Fixed

  1. A quote of a post that is on Bluesky is a quote there (roadmap row 156): one from Bluesky, or one of ours written there, is embedded as a record, Bluesky's own quote, beside the post's own pictures, video or card; the "↪" line and card are for a quoted post that is not on Bluesky.
  2. A quote's card on Bluesky has the quoted post's picture (roadmap row 156): a photo post's first picture, an article's cover, a video's poster, a sound's cover, or the picture of a note's link card. It had its words alone.

Anahita Services v1.3.1

Fixed

  1. A quote reaches Mastodon and Bluesky as one (roadmap row 156, part 1): a post that quotes ends with "↪" and the quoted post's address, its page here when it is public, its own address when it came from elsewhere, and no line when nobody signed out may see it. Mastodon makes a card of it; on Bluesky the post carries a card of it when it carries nothing else. It went out as the note around it alone.

Anahita Services v1.3.0

Upgrading

  1. Websites are channels, and three settings have new names: WEBSITES_FROM is CHANNELS_FROM, WEBSITE_HOURLY_CAP is CHANNEL_FEED_HOURLY_CAP and WEBSITE_READ_EVERY is CHANNEL_FEED_READ_EVERY. With Docker Compose the old names are still read for this release. On Kubernetes, rename the keys in your config.env: the manifests pass only the new ones, and a site that set WEBSITES_FROM would otherwise fall back to administrators. CHANNELS_FROM is now read by actor-service too, which makes channels.
  2. In instance.json, website among actor-service's kinds becomes channel (still read for this release), and a site's own website.json beside the defaults becomes channel.json.
  3. The API's /websites/… addresses are /channels/…, NodeInfo's websitesFrom is channelsFrom, and the kind is channel in custom feeds, recommendations and the accounts list. POST /channels/_connect/:id is gone: a channel is made with POST /channels/, and its feed connected with PUT /channels/_connect/feeds/:channel_id. A web app from before this release does not work with it: run Anahita Web's next release with it.
  4. Four migrations run by the migration job, as any upgrade's do (Upgrading): who sees one's follows (graph_access), servers a person blocked (person_domain_blocks), the rename to channels (channels, which rewrites stored types, two tables and custom feeds that name the kind), and a channel's feed notes marked as such (channel_feed_marks). Take a backup first, as before any upgrade.

Added

  1. Custom feeds that match any, or all (roadmap row 149): match in a feed's definition, any or all. With any, a post from its sources, or with one of its hashtags, keywords or locations, or in its area, is in; kinds of post and profile, language and origin still narrow, and what is excluded is still left out. A definition without it is all, as every feed was, and all is stored as nothing.
  2. Events hosted by a channel (roadmap row 147, phase 5): POST /events/ takes a channel's id in host_group_id, from one of its admins, whose admins are carried onto the event as a group's are; GET /channels/:id/events/ lists the events a channel hosts.
  3. A channel's feed, connected in its settings (roadmap row 147, phase 4): GET, PUT and DELETE /channels/_connect/feeds/:channel_id, for its admins. A site's domain is proved as before (POST /channels/_connect, …/:id/check), then its feed connected to a channel already made: one feed a channel (has_feed). Disconnecting keeps the notes it brought, and connecting the same feed again posts none of them twice.
  4. A channel's admins post as it (roadmap row 147, phase 3): notes, photos, videos and sounds made on a channel are the channel's own, its author shown and sent; the admin who wrote each is kept as written_by, sent only to its admins and the site's administrators, as written_by on a post or a reply. Articles and topics are offered off, for its admins to turn on in its features. Only its admins write on it, whatever its features say. A post's editor is no longer sent for a channel's posts. The notes a feed makes are marked from_feed in their meta (migration 20261122000022), and only those keep their site's words; what its admins write is theirs to change.
  5. Making a channel without a feed (roadmap row 147, phase 2): POST /channels/, by whoever CHANNELS_FROM allows, now read by actor-service too; a channel has a group's privacy (/access, follow requests), who sees its follows (/graph-access), features, archiving and spam removal. A channel that lets people ask is asked to follow.
  6. Whose notifications (roadmap row 146): what is yours, or a website's you look after, tells you of everyone; what you take part in tells you of the people you follow. Replying and reposting subscribe you to the post; a post's subscribers are told of likes, reposts and replies by people they follow; a website's admins are told as its author. Post notifications carry notify_off while the reader is told of the profile; profiles say is_subscribed_by_viewer to whoever follows them.
  7. Blocking a server yourself (roadmap row 152): GET, POST /socialgraph/:actor_id/blocked-servers, DELETE …/:domain. Nothing from the server, or one under it, is shown to the person; no notifications; follows with people there end both ways, their server told as for any follow that ends, and new ones are refused. Bluesky is refused (server_on_bluesky). In the download as domain_blocks.csv. Migration 20261122000020_person_domain_blocks.
  8. Who sees a profile's followers and whom it follows (roadmap row 151): PATCH /people|groups|events/:id/graph-access, an access level or none, never wider than the profile; the lists answer 403 to anybody else, the counts stay, and recommendations name only those who let the viewer see whom they follow. Migration 20261122000019_graph_access.
  9. Mailpit in the development stack: every message is caught and read at http://localhost:8025 (opens in a new tab), nothing sent anywhere. Point .env at it (SMTP_HOST="mailpit", SMTP_PORT="1025", no user or password); see Getting started, Mail in development.
  10. Removing a follower who is on another server tells their server (roadmap row 150), with a Reject of their follow, so that it stops delivering one's posts to them. It is not a block, and they may follow again.

Changed

  1. A channel is made first, its feed connected after (roadmap row 147, phase 4): POST /channels/_connect/:id, which made a channel of a proved feed, is gone, and suggested_name and suggested_alias with it. Make the channel with POST /channels/, then connect its feed.

  2. Websites are channels (roadmap row 147, phase 1: the rename alone; nothing else about them changes yet). Migration 20261122000021_channels renames the type to node.actor.actor-service.channel.v1 everywhere it is stored, the tables to channel_feeds and channel_feed_items, and suggest_websites to suggest_channels, and rewrites custom feeds that name the kind. What an operator renames:

    • WEBSITES_FROM → CHANNELS_FROM, WEBSITE_HOURLY_CAP → CHANNEL_FEED_HOURLY_CAP, WEBSITE_READ_EVERY → CHANNEL_FEED_READ_EVERY; the old names are still read for this release, and say so in the log (on Kubernetes, rename the ConfigMap's keys);
    • website → channel among actor-service's kinds in instance.json, still read as channel for this release;
    • a site's own website.json beside the defaults → channel.json.

    The API's /websites/… addresses are /channels/…, connecting one included (/channels/_connect, and WebSub's callbacks at /channels/_websub/…: a hub given the old address before the upgrade is asked again when its lease runs out); NodeInfo's websitesFrom is channelsFrom; the kind is channel in custom feeds, recommendations and the accounts list. A web app from before this release does not work with it.

Fixed

  1. A channel's post sent to the fediverse once (roadmap row 147, phase 6): one its admins wrote was found twice by the sweep for what did not go out, as a channel's note and as a profile's own post.
  2. A new sound posted (audio_add) can be turned off with the other posts, under posts.
  3. A sensitive post from another server keeps its pictures (roadmap row 122): its warning is read, a Note's summary in its author's words or "Sensitive", or a Bluesky self-label as its kind, and its pictures, video or sound are kept behind it, as a post written here is. They were left out before.
  4. Search finds a photo post by the alt text of any of its pictures, the second, third or fourth as well as the first; a whole word there counts as one in the post's words.
  5. A photo post with several pictures found by search, on a hashtag's or a location's page, or among liked posts, is answered with all of them, as in a feed, not its first picture alone.

Anahita Services v1.2.9

Fixed

  1. Signed out after a renewal that was cut short: a request renewing a session that was cancelled half way (a client giving up, a proxy's timeout) left the old refresh token spent and no new one, and the retries were taken for a stolen copy, signing the person out of that app on every device. Once begun, a renewal is finished.
  2. "New sign-in" emails for no sign-in: a browser given new tokens because its sign-in session was still alive was emailed as a sign-in once half an hour had passed, or its address or browser had changed. The email is sent after a sign-in with a password, a code or a passkey, and only then.
  3. A token forwarded in its last second: auth-service took an access token as valid through its whole last second, which the services refuse. Its expiry is compared to the instant, and /oauth/validate renews a session's token when it has under a minute left.

Anahita Services v1.2.8

Added

  1. Replies without notes: reply is a kind of post in instance.json, offered where it is listed or where note is. A site of photos alone lists {"service": "text-service", "node_types": ["reply"]}: replies under its photos, and no notes of their own (What a site offers). Files that list note keep their replies; nothing to change.

Fixed

  1. A thread of notes where notes are off was refused with a 500; it is refused with 403 {"error": "off"}, as a note is.

Anahita Web v1.2.4

Works with Anahita Services v1.2.6 or later.

Added

  1. Content warnings (roadmap row 122, phase 1): a post or a reply can say what it holds, Adult content, Sexually suggestive, Graphic media, Non-sexual nudity, or Other in its author's words, from Content warning among its choices, or later from its menu. Wherever it is drawn, it shows the warning and View over its photo, GIF, video or sound, blurred behind it, and its words as they are, until the reader chooses to see it; a post of words alone, an article or a topic, has the warning over all of it.

  2. A GIF, a video or a sound in any note of a thread (roadmap row 143), in the composer and in a reply: each note has GIF, Video and Audio beside Photo. The notes after a file are posted once it is ready, in order; the + button shows the files' progress together, and a file that cannot be posted stops the thread there, saying why.

  3. WebP, HEIC and AVIF photos (roadmap row 135), in posts, replies and an article's cover: asked for by the pickers, and shown before they are posted, an iPhone's HEIC too where the browser cannot draw it.

  4. A site that offers less (roadmap row 139): where the services' new instance.json leaves groups, events or websites out, they go from the menu, a group's Events tab, the recommendations and the buttons that make them; the kinds of post a site leaves out go from composers and profile tabs, as video did. Needs Anahita Services v1.2.6 or later.

Changed

  1. One column or several, chosen apart for feeds and for profiles: columns on Home no longer lay profiles out in columns too. Profiles start in one column; the feeds keep what was chosen before.

  2. Colors in the menu shows the colours in use, the site's or those chosen, in one circle, as the picker shows each palette, in place of a palette's icon.

Fixed

  1. A GIF or a video sent as a reply kept its words: they were dropped on the way.
  2. A thread with a photo in a note after the first is shown in a list as a thread, with all its notes counted.
  3. No pictures in a reply where the site offers no photo posts: the whole reply form offered Add pictures on every site, and a reply with pictures, a photo post, was refused where photos are off.