Skip to content
Releases
A line drawing: the main branch of Anahita Services, its newest release tagged, over what changed.

Anahita Services v1.0.17 to v1.0.19

Anahita Services v1.0.19

Added

  1. Asking to follow somebody elsewhere who approves their followers (anahita-web row 130): their manuallyApprovesFollowers is kept on their profile as allow_follow_request; following them is a request, sent as a Follow, made a follow by their Accept through the graph's own accept, and taken away by their Reject; taking it back sends an Undo; the sweep asks again about a request whose news the bus lost. POST /activitypub/people/:id/refresh reads somebody elsewhere again when what was kept of them is more than an hour old, asked by the web app when their profile is opened. Profiles say is_follow_requested_by_viewer (Federation).

Changed

  1. Following somebody elsewhere who approves their followers is refused; they are asked instead.
  2. Migration 20261122000012: each profile from the fediverse takes allow_follow_request from what its server last said, and a follow sent to one that approves its followers, still waiting for an answer, becomes a request; their counts are made again.

Anahita Services v1.0.18

Added

  1. Whose feeds, in GET /feeds/discover (anahita-web row 125): whose=everyone, following or mine, for somebody signed in, the web app's Feeds page's list (Discover); without it, as before.
  2. owned_by_followed in the graph's node list: only what is owned by somebody the viewer follows.
  3. A thread in a list (anahita-web row 126): in the home feed, a profile's and a custom feed, a note that opens a chain of its writer's replies carries thread, how many notes it has, and thread_next, the second note.

Removed

  1. The gRPC methods' names before v1.0.17: ListQuotes, ListSaved, ListCitedBy, ListAuthored and the event service's List, served beside their BREAD names for v1.0.17. A service of one's own calls Browse….

Anahita Services v1.0.17

Upgrading

  1. Everybody signed in signs in once more. What a session holds is now sealed with AES-GCM; a session sealed before is no longer read, and is taken as none, not an error.
  2. The file sweep starts as a dry run. The new file-sweeper CronJob counts, each night, the stored files no row names any more, and removes nothing until FILE_SWEEP=on is in anahita-config. Read its log first.
  3. A service of your own calling graph-grpc-service should call the new names: BrowseQuotes, BrowseSaved, BrowseCitedBy, BrowseAuthored, and the event service's Browse. The old names, List… and List, are served in this release and removed in the next.

Added

  1. The file sweep (roadmap row 106): sweeper -files-only, once a night as the file-sweeper CronJob, removes stored avatars, covers, photos and video files that no row names, a day old, kept unless it is sure; a dry run until FILE_SWEEP=on, at most 5,000 a night, counted by folder in its log (The file sweep).
  2. Browse in file-grpc-service: what is stored under a folder of assets/v1/, a page at a time, and nothing outside it.

Changed

  1. Sessions sealed with AES-GCM (row 119), in a cookie and in Redis, where AES-CFB hid them and noticed nothing: one that was changed is refused and taken as no session.
  2. A token must say when it runs out: one without exp is refused by the gateway and by auth-service. Every token auth-service makes has one.
  3. BREAD names in the code (row 127): thirty functions named List, Remove or Update are Browse, Delete and Edit, five of them gRPC methods, served under both names for this release.
  4. The API reference has a section for what every profile has, and one for each kind: people, groups, events and websites.

Docs

New: Features, by FediDB's 128 questions; profiles, people, groups and events, and what each node is. Planned: content warnings, direct messages, moving, threads that read as threads.