Skip to content

Releases

v0.1.0-rc.10

v0.1.0-rc.10 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 11 Nov 04:28
Immutable release. Only release title and notes can be modified.
54ecdbf

Main changes

  • Events. You can create events with a place, a visibility, invitations, co-organizers and attendee approval, and people can answer them (RSVP). Organizers can run a date poll among candidate dates and then confirm one. Events send notifications and reminders that you can set in your preferences, and you can export an event as an .ics calendar file. An event can have a voice room that opens when the event starts. Moderators can cancel events, and you can report one. The server side came in #2797, notifications and .ics in #2799, date polls and moderation in #2802, the list, page and editor in the web client in #2804, and date polls and voice rooms in the web client in #2807.
  • Articles. Besides short posts, you can write long-form articles with a title, summary, cover and tags, in Markdown. You can preview them, save them as drafts and schedule them. The server side came in #2797. Articles federate as Article, and remote articles can be read in full (#2799). They appear as cards, on their own page, on a profile tab and in Atom feeds (#2802). The web client has an article editor (#2804). Auto-delete can keep your articles (#2807).
  • One-time tips. Supporters can send the server a one-time tip as well as subscribing, through Stripe or PAY.JP. The core came in #2812 and the providers in #2813. The web client has a page for the payer, and the finance screens show income by source (#2814).
  • Funding meter. The server can show how well it is funded. The server side came in #2799 and the web client in #2802.
  • Profiles and accounts.
    • You can keep private notes on other accounts (#2797).
    • You can hide your follows and followers lists (#2799).
    • Profiles and hashtags have Atom feeds (#2797).
    • A profile can list that account's posts with a given hashtag, at /@{acct}/tagged/{tag} (#2804).
  • Voice rooms can be opened by a schedule (#2797).
  • Interface.
    • Controls you can press now show that they can be pressed when you point at them (#2797).
    • After you accept a blocklist subscription's drafts, focus moves to the drafts' heading again instead of getting lost (#2819).
  • Moderation.
    • From the moderation screens you can open the page of any remote server. You can type a domain, a handle on the server such as @alice@mastodon.example, or a URL. Remote accounts, reports about remote accounts and audit log entries about a domain also link to the server's page (#2822).
    • That page lists the deliveries to the server with every attempt (#2814).
  • Translations and documentation.
    • Every untranslated string of the interface is now translated in German, Spanish, French, Brazilian Portuguese, and Simplified and Traditional Chinese. The documentation site is up to date in every locale (#2820).
    • The sidebar of the documentation site lists only the current section in full (#2814).
    • The README and the landing page show the sponsors (#2798).

For operators

  • Data upgrade step finance.income_sources (#2812): it gives the income movements recorded before tips their source. Subscriptions' movements, with their refunds and chargebacks, become subscription, and the rest stays unknown. Run my db upgrade -check and then my db upgrade, as for every release. This release upgrades from the same minor version (v0.1.Z), rebuilds no projections, and asks for no manual step.
  • The schema of most modules changed: identity, account, moderation, content, graph, timeline, notification, federation, instance, finance, supporters, voice and the new gathering module for events. Before you upgrade, run this release's my schema apply -dry-run on a copy of your database and read the plan.
  • my schema apply now replaces a CHECK constraint whose expression changed (#2801). Before, on PostgreSQL, it kept the old one. An instance upgraded from v0.1.0-rc.8 to v0.1.0-rc.9 therefore kept 13 stale constraints. Writes of the values that rc.9 added then failed with SQLSTATE 23514, for example new notification types, reply / announce deliveries, new instance settings and the Cloudflare billing import. On such an instance, the plan of this release shows one DROP CONSTRAINT …, ADD CONSTRAINT … per stale constraint, and none of them destroys data. SQLite was not affected.
  • No settings were removed or renamed.
  • Tips need a payment provider. Stripe and PAY.JP now take one-time tips, and PAY.JP uses its API v2 for tips, next to the v1 subscriptions (#2813). You set the tip amounts and limits in the operator's settings (#2812, #2814).
  • The federation.deliver log line now says whether a delivery reached the remote server (#2813).
  • The server also answers its health checks on /health/live and /health/ready, because Cloud Run reserves the paths that end in z (#2813).
  • The OpenTofu targets offer opt-in bucket versioning, and the documentation gives backup guidance for the cloud targets (#2813).
  • Moderators with manage_domains can list the deliveries to a remote server. The deliveries of non-public activities are masked, and revealing one is written to the audit log (#2812).

For API and library users

  • VoiceStreamEnd.reason gains the values host_absent and unattended, for voice rooms opened by a schedule (#2797, #2804). It is still required. A client that rejects unknown values must accept these two.

  • New scopes read:events and write:events, with operations to:

    • list, read, create, update and cancel events: listEvents, getEvent, createEvent, updateEvent, cancelEvent;
    • answer an event: answerEvent;
    • manage invitations, attendee approval and co-organizers;
    • vote on date candidates: listEventCandidates, addEventCandidate, voteEventCandidate, confirmEventCandidate;
    • export an event as a calendar: getEventCalendar;
    • set event reminders: getEventReminders, updateEventReminders.

    Moderators can cancel an event with cancelEventAsModerator. Reports and notifications can carry an event_id. These came in #2797, #2799 and #2802.

  • Articles:

    • createArticle, previewArticle and editArticle;
    • the article field on Status, StatusEdit, StatusSource, Draft and DraftRequest;
    • the articles parameter of listAccountStatuses;
    • InstanceLimits.articles and Instance.article_authoring;
    • AutoDeletePolicy.keep_articles and AutoDeleteLimit.allow_articles.

    These came in #2797, #2799 and #2807.

  • listAccountStatuses takes a tagged parameter (#2804).

  • Tips:

    • startSupporterTip, getOwnSupporterTip and getInstanceTipAmounts;
    • getSupporterTips and setSupporterTips for admins;
    • Instance.tips_enabled;
    • income by source in IncomeMovement.source, IncomeMovement.tip_id, IncomeTotals.tips, AdminIncomeTotals.tips and AdminIncomePeriodTotal.net_by_source.

    These came in #2812 and #2813.

  • Instance.funding_meter (#2799).

  • Account notes: setAccountNote, deleteAccountNote and Relationship.note (#2797).

  • Hidden follow lists: follows_visibility on CredentialAccount and UpdateCredentialsRequest (#2799).

  • Atom feeds: feed_enabled on CredentialAccount and UpdateCredentialsRequest, and CredentialAccount.feed_follows_indexable (#2797).

  • Deliveries to a remote server: listInstanceDeliveries and revealInstanceDelivery (#2812).

  • lookupStatus (GET /statuses/lookup) is new.

  • mykit and mybot are released at v0.1.0-rc.10 with no change of their own listed for this release.

Upgrading

Follow Upgrading. Run my db upgrade -check and my db upgrade even when this section lists no step; they then do nothing.

Data upgrade steps:

  • finance.income_sources: Gives the income movements recorded before tips their source: the subscriptions' movements and their refunds and chargebacks become subscription, the rest stays unknown.

Projections that my db upgrade rebuilds: None.

Upgrade from: the same minor version (v0.1.Z).

To do by hand: None.

Breaking changes

Settings: None.

Client API:

  • VoiceStreamEnd.reason: string enum left / moved / disconnected / removed / blocked / suspended / room_ended / replaced / host / empty / host_disconnected / host_ineligible / moderator / time_limit / disabled / host_absent / unattended, required, was string enum left / moved / disconnected / removed / blocked / suspended / room_ended / replaced / host / empty / host_disconnected / host_ineligible / moderator / time_limit / disabled, required

Schema contract:

  • schema/01-identity/postgres.sql changed: review it for removed tables and columns, type changes, and new constraints
  • schema/01-identity/sqlite.sql changed: review it for removed tables and columns, type changes, and new constraints
  • schema/02-account/postgres.sql changed: review it for removed tables and columns, type changes, and new constraints
  • schema/02-account/sqlite.sql changed: review it for removed tables and columns, type changes, and new constraints
  • schema/03-moderation/postgres.sql changed: review it for r...
Read more

v0.1.0-rc.9

v0.1.0-rc.9 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 10 Nov 12:14
Immutable release. Only release title and notes can be modified.
7b05b78

Main changes

  • Who can reply, boost, and quote. Each post now has its own rules for replies, boosts, and quotes, which replace the single quote setting. In the composer, a "Who can reply, boost, and quote" tool lets you choose who may do each one right away. Everyone else can do it only with your approval. You can change the rules later from the post's menu, and set your defaults for each kind in Settings.
    • These rules apply on this server and over federation. Other servers learn them through canReply, canAnnounce, and canQuote.
    • A reply or boost that falls outside the rules either waits for your approval or is refused. Requests that wait are listed at /settings/interaction-requests, where you approve or decline them.
    • Posts hide the reply button, or disable the boost, when you may not use them. When your reply, boost, or quote will wait for approval, the post says so.
    • Deleting a reply or undoing a boost that still waits for approval withdraws the request.
    • These changes come from #2739, #2746, #2752, #2760, #2761, and #2764.
  • Direct messages by conversation.
    • A new "Direct messages" screen lists your conversations of direct posts, including posts from accounts you do not follow. The navigation shows how many conversations are unread, the list updates live, and replies in a thread stay direct (#2744, #2749).
    • Conversations follow the thread across servers, so threads hold together when posts arrive out of order. Threads also load with far fewer database reads (#2738).
  • Keyword filters. You can filter posts by keywords, and matching posts are folded. Keyword filters are included in the data export (#2778, #2790).
  • Notification controls.
    • A notification policy lets you choose what to do with notifications from different kinds of accounts. Notifications held by the policy are gathered as requests, which you can accept or dismiss.
    • You can mute a thread to stop its notifications.
    • These come from #2778 and #2790.
  • Hashtags.
    • You can follow hashtags and read their posts on your home timeline. Followed hashtags are included in the data export.
    • You can feature hashtags on your profile, and these federate.
    • When a remote account stops publishing its pinned posts or featured hashtags, the copies on this server are now cleared (#2780).
    • These come from #2769, #2778, and #2790.
  • Drafts and scheduled posts. You can save posts as drafts and schedule them to be published later. You get a notification if a scheduled post fails to publish (#2769, #2790).
  • Link previews.
    • Pages without an image of their own now fall back to the server's thumbnail, then the logo, then a new built-in image (the colourful wordmark on white).
    • Every page now carries site-wide preview tags.
    • og:locale includes the territory, as in ja_JP.
    • Administrators can set the link preview image and its alt text in Settings → General.
    • These come from #2759.

For operators

  • Upgrading. No data upgrade step and no projection rebuild is listed for this release, but still run my db upgrade -check and my db upgrade. The schema of several modules changed. Review the schema diff before upgrading:
    • Conversations become their own tables (conversations, status_conversations, conversation_merges), which replace statuses.conversation_uri (#2738).
    • Interaction policies replace status_quote_policies and user_preferences.default_quote_policy (#2739).
    • The timeline module gains the direct message projections (#2744).
    • outbound_activities.object_type now accepts reply, announce, and quote, instead of quote for every kind (#2760).
    • The finance schema accepts the new billing source and method (#2747).
  • Federation allowlist mode and blocklist subscriptions.
    • Administrators can federate only with allowed domains. getFederationScopeImpact shows what a change of the federation scope would cut off.
    • Administrators can subscribe to blocklists, then review the drafted changes and accept or reject them.
    • Both have their own pages in the admin screens (#2769, #2790).
  • Media proxy. The media proxy no longer fetches from suspended domains, or from domains that the allowlist does not admit (#2774).
  • Monitoring. The metrics snapshot log line is now written under metrics_exporter = none, which is the default and what monitoring-gcp sets on Cloud Run. Before, the alerts built on that line read nothing, and MyMetricsSnapshotStale fired for as long as the server ran (#2751).
  • Cloudflare billing source. billing_sources = cloudflare imports the usage charges of a pay-as-you-go Cloudflare account. Plans, taxes, and credits are not imported.
    • New setting billing_cloudflare_account_id.
    • New secret billing_cloudflare_api_token, which also has a _FILE form and is redacted in logs.
    • The build tag no_billing_cloudflare leaves the source out of the build.
    • These come from #2747.
  • Letting another service use the admin API. An account can issue itself a token with an admin:<permission> scope, such as admin:manage_invites. With that token, an outside service can call the admin operations of that one permission, and the account's roles are still checked on every call. The operator guide has a new section on this (#2792).

For API and library users

  • setStatusQuotePolicy (PUT /statuses/{id}/quote_policy) is removed, although it was not deprecated in v0.1.0-rc.8 (#2739).
    • The single quote policy was replaced by interaction policies, which set reply, boost, and quote rules together. Use setStatusInteractionPolicy (PUT /statuses/{id}/interaction_policy) instead.
    • The pull request gives no reason for skipping the deprecation period beyond this replacement.
  • Schema QuotePolicy is removed; use InteractionPolicy (#2739).
  • Schema SetQuotePolicyRequest is removed; setStatusInteractionPolicy takes an InteractionPolicy (#2739).
  • CreateStatusRequest.quote_policy is removed; use CreateStatusRequest.interaction_policy (#2739).
  • Preferences.default_quote_policy is removed; use Preferences.default_interaction_policy (#2739).
  • Status.quotable is removed; read Status.permissions instead, which gives allowed, pending, or denied for reply, announce, and quote (#2761).
  • Status.quote_policy is removed; the author reads Status.interaction_policy (#2739).
  • UpdatePreferencesRequest.default_quote_policy is removed; use UpdatePreferencesRequest.default_interaction_policy (#2739).
  • BillingImport.method gains the value billable_usage, used by the Cloudflare billing source. Clients that switch over every value need a case for it (#2747).
  • RelationshipSeverance.kind gains the value allowlist_cutoff, for relationships cut off by the federation allowlist mode. Clients that switch over every value need a case for it (#2769).
  • New operations:
    • Interaction approval requests: listInteractionRequests, acceptInteractionRequest, and rejectInteractionRequest (#2761).
    • Conversations: listConversations, getConversation, markConversationRead, and hideConversation, plus a conversation event on the stream (#2744).
    • Keyword filters: listKeywordFilters, createKeywordFilter, and the related operations (#2778).
    • Notification policy and requests, and thread mutes (muteStatusThread, unmuteStatusThread) (#2778).
    • Followed and featured hashtags (followTag, setFeaturedTags, and the related operations) (#2769, #2778).
    • Drafts and scheduling (#2769).
    • Admin operations for domain allows and blocklist subscriptions (#2769).
  • New fields on Status: Status.filtered, Status.muted, Status.followed_tags, Status.approval, and Status.boost_approval.
  • Admin settings: AdminSetting.image gives a media setting its image (#2759).
  • New scopes:
    • read:filters and write:filters.
    • 14 admin:<permission> scopes, from admin:manage_accounts to admin:view_audit. Only a token that an account issues to itself through issueOAuthAppTokens can hold them. The authorization endpoint refuses them with invalid_scope (#2792).
  • mykit: regenerated for these changes. setStatusQuotePolicy is removed from the generated client.
  • mybot: no changes.
  • API reference: an operation's page now links the schemas it holds instead of expanding them, and every object schema has a page of its own (#2794).

Upgrading

Follow Upgrading. Run my db upgrade -check and my db upgrade even when this section lists no step; they then do nothing.

Data upgrade steps: None.

Projections that my db upgrade rebuilds: None.

Upgrade from: the same minor version (v0.1.Z).

To do by hand: None.

Breaking changes

Settings: None.

Client API:

  • setStatusQuotePolicy (PUT /statuses/{id}/quote_policy): not deprecated in v0.1.0-rc.8, which only a security fix allows; say why
  • schema QuotePolicy
  • schema SetQuotePolicyRequest
  • `CreateStatusRequest....
Read more

v0.1.0-rc.8

v0.1.0-rc.8 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 10 Nov 01:06
Immutable release. Only release title and notes can be modified.
8869b15

Main changes

This release candidate makes the server faster. Many pages and jobs used to make one or more database round trips for each status, account, or recipient. They now read and write what they need together, so their cost no longer grows with the size of the page or the number of people involved. What you see stays the same; it should just appear faster, especially on busy instances.

  • Timelines load faster. The local, federated and home timelines read a page's accounts, statuses, revisions, relationships, interactions, quotes, polls, attachments and link cards together. A page of 30 statuses now takes as many round trips as a page of 10. Tests check that each status looks exactly as it does when shown alone. (#2672, #2686, #2687)
  • Link cards cost less. Checking the sites behind link cards now takes the same work however many different sites a page links to. (#2715)
  • Live streams scale with connected users. A new public post on the local or federated timeline is now checked and prepared once for every open stream on the server, rather than once per connection. With 8 connections, one new post went from 376 round trips to 48. The streams send the same events as before. (#2735)
  • Stream heartbeats are cheaper. Each heartbeat now checks the sign-ins of all open streams together. A revoked token still ends its stream within one heartbeat. (#2713)
  • Posting is faster with many mentions or hashtags. Mentions, hashtags, custom emoji and attachments of a new post are resolved and saved together. A post with 15 mentions went from 474 round trips to 122. (#2716, #2726)
  • Notifications are created and listed faster. This covers:
    • mentions, post subscribers, and followers of a voice room that opens (#2705, #2706, #2707);
    • announcements, service closures and webhook messages (#2730);
    • the notification list, which takes the same work for 40 notifications as for 12 (#2689).
  • Account and status lookups are faster. This covers:
    • checking your relationships with many accounts at once (#2691);
    • account search as you type (#2732);
    • status search, which went from 530 round trips to 86 for 20 hits (#2708);
    • the instance information page (#2714).
  • Voice rooms are faster. Showing a room or the list of rooms no longer reads each host and participant separately. A list of 11 rooms went from 720 round trips to 66. (#2709, #2710)
  • Moderation and administration pages are faster. This covers:
    • reports, moderation actions on statuses, and incoming reports from other servers (#2728, #2733);
    • the audit log, account actions, report notes, invites and hook decisions (#2731).

For operators

There are no breaking changes, no removed settings, and no data upgrade steps. You can upgrade from the same minor version (v0.1.Z). As always, run my db upgrade -check and my db upgrade; in this release they do nothing.

The main change for you is lower database load:

  • Federation delivery needs fewer queries.
    • Delivering a post to remote servers reads inboxes, relationships, domain suspensions and server health together (#2693).
    • Deliveries are inserted together, which also makes the fan-out of a post's deliveries much cheaper (#2694).
    • Jobs are inserted together. This applies to every caller that enqueues several jobs at once, on both PostgreSQL and SQLite (#2694).
    • Each delivery attempt now makes 5 queries instead of 12 (#2717).
  • Other federation work needs fewer queries.
    • Refreshing stale remote actors (#2718).
    • Serving followers, following, outbox and featured collections (#2692). This also stops timelines and status pages from reading custom emoji that were never shown.
    • Building the Note of a local status that mentions remote accounts (#2729).
  • Relationship jobs work in batches. Suspending a remote account, suspending a domain, and my admin federation sever now end follows a batch at a time (#2719, #2720). So do moving an account's followers, blockers and muters (#2721, #2734) and erasing a deleted account (#2723). Their cost per batch no longer grows with the number of accounts involved.
  • The key-value store can read many keys at once. It now does so on both the database and Valkey, which voice rooms use for heartbeats (#2710).
  • Sign-in use is recorded per stream on the same schedule as for requests. Streams now record that a token was used once per LastUsedInterval, as normal requests do (#2713).

For API and library users

The client API, mykit and mybot have no changes in this release.

One streaming change is worth knowing about. A voice room stream used to send the room's state on every 15-second heartbeat. Now, when the state has not changed since the last state event, the heartbeat sends only the heartbeat comment (#2710). Clients should rely on state events for changes, not on a state event arriving with every heartbeat.

Upgrading

Follow Upgrading. Run my db upgrade -check and my db upgrade even when this section lists no step; they then do nothing.

Data upgrade steps: None.

Projections that my db upgrade rebuilds: None.

Upgrade from: the same minor version (v0.1.Z).

To do by hand: None.

Breaking changes

None.

API changes

None.

mykit

The client library of the client API, released with this version of the server
(pkg/mykit, MIT).

  • Go: go get github.com/mycroblog/my/pkg/mykit@v0.1.0-rc.8
  • npm: npm install @mycroblog/mykit@0.1.0-rc.8 (dist-tag next, with provenance)

None.

mybot

The bot library on top of mykit, released with the same version
(pkg/mybot, MIT).
Its npm package depends on @mycroblog/mykit@0.1.0-rc.8 exactly.

  • Go: go get github.com/mycroblog/my/pkg/mybot@v0.1.0-rc.8
  • npm: npm install @mycroblog/mybot@0.1.0-rc.8 (dist-tag next, with provenance)

None.

Full Changelog: v0.1.0-rc.7...v0.1.0-rc.8

Container image

ghcr.io/mycroblog/my:0.1.0-rc.8@sha256:dbc112533183fe7225aa3b6ea792eaaaf018aad0fdff8c0b5968e578b208ce6d

v0.1.0-rc.7

v0.1.0-rc.7 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 09 Nov 14:42
Immutable release. Only release title and notes can be modified.
bb5f11d

Upgrading

Follow Upgrading. Run my db upgrade -check and my db upgrade even when this section lists no step; they then do nothing.

Data upgrade steps: None.

Projections that my db upgrade rebuilds: None.

Upgrade from: the same minor version (v0.1.Z).

To do by hand: None.

Breaking changes

None.

API changes

None.

mykit

The client library of the client API, released with this version of the server
(pkg/mykit, MIT).

  • Go: go get github.com/mycroblog/my/pkg/mykit@v0.1.0-rc.7
  • npm: npm install @mycroblog/mykit@0.1.0-rc.7 (dist-tag next, with provenance)

None.

mybot

The bot library on top of mykit, released with the same version
(pkg/mybot, MIT).
Its npm package depends on @mycroblog/mykit@0.1.0-rc.7 exactly.

  • Go: go get github.com/mycroblog/my/pkg/mybot@v0.1.0-rc.7
  • npm: npm install @mycroblog/mybot@0.1.0-rc.7 (dist-tag next, with provenance)

None.

Full Changelog: v0.1.0-rc.6...v0.1.0-rc.7

Not gated by the slow suite

This pre-release was made in an emergency without the slow suite: the full E2E, the live federation test, the contracts on real services, the upgrade test, and the restore drill did not run on it.

Container image

ghcr.io/mycroblog/my:0.1.0-rc.7@sha256:43c5283d14680c6f3571774296ca6a80cad4cd723157bee92441bc0e25fd65e8

v0.1.0-rc.6

v0.1.0-rc.6 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 09 Nov 14:03
Immutable release. Only release title and notes can be modified.
27b6c5c

Main changes

  • On a remote account's profile with a pending follow request, the follow button, the bell, and the menu stay at the end of the avatar's row again. The line saying the request is waiting for approval now sits on its own row below them (#2656).
  • Admin pages no longer show the details of a description list one character per line on wide screens. This affected the state card of a job's page (/admin/jobs/<id>) and the assignee and resolution of a report's page (#2647).
  • Other servers can fetch your posts more reliably when your server has to look up their key first. If a remote server is slow, the database step after the fetch is no longer cut short. If the remote server does not answer within 5 seconds, your server answers 503 so the sender retries, instead of failing with 500 (#2658).

For operators

There are no breaking changes, no removed settings, and no data upgrade steps in this release. Still run my db upgrade -check and my db upgrade as usual; they do nothing.

  • Error report fingerprints change once. A reported error's stack now starts where the error came from, not in the helper that reported it. Database errors start at the repository method, such as (*Repository).ListKeys, and request errors start at the caller of the reporting helper. Errors from different places no longer share one group. After the upgrade, each error that had no stack of its own opens a new group and notifies once (#2662).
  • The report line of a request's error now carries context.httpRequest, with method, url, and responseStatusCode. On Cloud Run, Error Reporting can then show the response code, which read 0 before. The url is the route pattern, never the request's path, so it holds no personal data. Errors from jobs and goroutines, and a web client's errors, get no httpRequest. The Sentry sink is unchanged (#2663).
  • A slow remote server no longer fills your error reports. When resolving an unknown signing key takes longer than 5 seconds, the 5-second limit now applies to the network fetch alone. A fetch cut by that limit is answered with 503 and is not reported as an error (#2658).
  • Error Reporting on Cloud Run reads the error report line. This was checked with v0.1.0-rc.5: it reads the severity, the service and version, and the Go stack, and it groups lines by their stack and notifies new groups (#2661).
  • A nightly image is published between releases as ghcr.io/mycroblog/my:nightly. It is built from the latest main commit that passed the Nightly checks. It has no upgrade path and is not for production. Its version is a pseudo-version after the latest release tag, which my version and NodeInfo report. See the running guide for how to verify its signature (#2654).
  • A pre-release can now be published in an emergency without the slow suite. Its release notes then carry a section Not gated by the slow suite. Full releases always pass the slow suite (#2652).

For API and library users

None.

Upgrading

Follow Upgrading. Run my db upgrade -check and my db upgrade even when this section lists no step; they then do nothing.

Data upgrade steps: None.

Projections that my db upgrade rebuilds: None.

Upgrade from: the same minor version (v0.1.Z).

To do by hand: None.

Breaking changes

None.

API changes

None.

mykit

The client library of the client API, released with this version of the server
(pkg/mykit, MIT).

  • Go: go get github.com/mycroblog/my/pkg/mykit@v0.1.0-rc.6
  • npm: npm install @mycroblog/mykit@0.1.0-rc.6 (dist-tag next, with provenance)

None.

mybot

The bot library on top of mykit, released with the same version
(pkg/mybot, MIT).
Its npm package depends on @mycroblog/mykit@0.1.0-rc.6 exactly.

  • Go: go get github.com/mycroblog/my/pkg/mybot@v0.1.0-rc.6
  • npm: npm install @mycroblog/mybot@0.1.0-rc.6 (dist-tag next, with provenance)

None.

Full Changelog: v0.1.0-rc.5...v0.1.0-rc.6

Not gated by the slow suite

This pre-release was made in an emergency without the slow suite: the full E2E, the live federation test, the contracts on real services, the upgrade test, and the restore drill did not run on it.

Container image

ghcr.io/mycroblog/my:0.1.0-rc.6@sha256:3e5586ce28dde3cc97f6e9a662c389bf6615c4b99546e0d34799e20974aeb90d

v0.1.0-rc.5

v0.1.0-rc.5 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 09 Nov 12:28
Immutable release. Only release title and notes can be modified.
957392b

Main changes

  • Translating a post is easier to find and to undo (#2634).
    • A "Translate" icon button now sits in the post's actions row, after the bookmark. It shows as pressed while the translation is displayed.
    • On narrow cards the icon is hidden. At every width, the "More actions" menu offers "Translate" and "Show original".
    • One line under the translated text names the source language and the translation service, with a "Show original" link, for example: "Translated from French · LibreTranslate · Show original". The line also shows when a translation is still on its way, with progress for in-browser translation, and why a translation failed.
    • Keyboard focus stays on the button, or moves back to it after "Show original".
    • In moderation, where a reported post has no actions row, a text button after the text does the same.
  • External links in text no longer break the line (#2621). The icon of an inline external link now stays on the same line as the text. This affects, for example, the translation note of a post and the website field of a profile.
  • Emoji search handles text full of colons in linear time (#2542). Before, a search text with many colons could make the search very slow.

For operators

  • No data upgrade steps. This release has no data upgrade steps and no projections to rebuild. Still run my db upgrade -check and my db upgrade as usual; they do nothing.
  • Background jobs run again on Cloud Run with Cloud Tasks (#2642). With queue = cloudtasks, v0.1.0-rc.4 refused every push from Cloud Tasks and Cloud Scheduler with 401 (azp "<unique ID>" is not the client), so no job ran. The server now accepts the ID token that Google issues for a service account. Upgrading is enough; there is no setting to change.
  • The Cloud Run console job can be turned off again (#2643).
    • What changed: in the app-gcp-cloud-run OpenTofu module, the console job now always has deletion_protection = false. The service and the migration job still take the module's input.
    • Why it matters: before, tofu apply -var console_enabled=false failed with "cannot destroy job without setting deletion_protection=false". Every later apply without console_enabled = true failed the same way.
    • What to do: a console created before this change still has deletion_protection = true in the state. Run tofu apply -var console_enabled=true once to write false to the state. Then tofu apply -var console_enabled=false turns the console off.
  • A Grafana dashboard is available (#2547). The dashboard in deploy/monitoring/grafana/my.json covers HTTP, jobs and the queue, federation, and the process. It has variables for the data source and the job, so you can import it into your own Grafana. docs/operations/alerts.md describes it.

For API and library users

None.

Upgrading

Follow Upgrading. Run my db upgrade -check and my db upgrade even when this section lists no step; they then do nothing.

Data upgrade steps: None.

Projections that my db upgrade rebuilds: None.

Upgrade from: the same minor version (v0.1.Z).

To do by hand: None.

Breaking changes

None.

API changes

None.

mykit

The client library of the client API, released with this version of the server
(pkg/mykit, MIT).

  • Go: go get github.com/mycroblog/my/pkg/mykit@v0.1.0-rc.5
  • npm: npm install @mycroblog/mykit@0.1.0-rc.5 (dist-tag next, with provenance)

None.

mybot

The bot library on top of mykit, released with the same version
(pkg/mybot, MIT).
Its npm package depends on @mycroblog/mykit@0.1.0-rc.5 exactly.

  • Go: go get github.com/mycroblog/my/pkg/mybot@v0.1.0-rc.5
  • npm: npm install @mycroblog/mybot@0.1.0-rc.5 (dist-tag next, with provenance)

None.

Full Changelog: v0.1.0-rc.4...v0.1.0-rc.5

Container image

ghcr.io/mycroblog/my:0.1.0-rc.5@sha256:cf47c60218cb70e2b9305da41d20e6083885dbfa52336f7870ddb59940330a79

v0.1.0-rc.4

v0.1.0-rc.4 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 08 Nov 17:23
Immutable release. Only release title and notes can be modified.
39a1896

Main changes

  • Full-text search of posts. On a server with a search engine, signed-in people get a "Posts" tab on the search screen. Results follow the same visibility rules as timelines, and authors can opt out. Operators choose Elasticsearch, OpenSearch, Meilisearch, or a plugin as the engine, and choose which visibilities are indexed (#2280, #2284, #2427, #2433, #2282).
  • Post translation. A "Translate" button shows a post in your language and lets you switch back to the original. The server can use LibreTranslate, DeepL, Google Cloud Translation, Amazon Translate, or a plugin, within monthly limits the operator sets. The server can also let the browser's built-in translator do the work, so nothing leaves your device. Moderators can translate reported posts and the reporter's comment (#2273, #2283, #2278, #2292, #2416, #2281, #2294, #2302).
  • New languages. The interface and the documentation are now available in Simplified Chinese, Traditional Chinese, Spanish, Brazilian Portuguese, German, and French. These are machine translations (#2474, #2531, #2532, #2533, #2536).
  • One-person server mode. A server can be run for a single person. Visitors land on that person's profile, sign-up is closed, and the local and federated timelines are turned off (#2450).
  • Automatic deletion of old posts. Operators can set a server-wide default and maximum for how long posts are kept, with a grace period. You are notified when the maximum applies to you, and the about page shows the limit (#2449).
  • Automated reviews with appeals. Operators can have a plugin review sign-ups, new and edited posts, uploads, follows, and incoming posts, as well as profiles (#2276, #2285, #2289, #2288, #2296, #2303, #2314, #2440).
    • If a post or an edit of yours is refused, you can appeal, and you are told the outcome.
    • Moderators review appeals under Moderation > Automated reviews.
  • Moderation and administration.
    • Moderators can forward a report to the other server after it was filed (#2297).
    • Every admin and moderation screen is split into list and detail pages, and every list is paginated and fits narrow screens (#2410).
  • Fixes.
    • Staff menu items appear on the first render (#2451).
    • Toasts no longer cover the last control of a page on small screens (#2415).
    • An unknown value sent by a newer server no longer breaks a page (#2197).

For operators

Run my db upgrade -check and my db upgrade as usual. This release candidate changes the schema in ways that can remove data:

  • Destructive schema change. Upgrading from v0.1.0-rc.3 drops status_sensitivity_overrides.source_action_id, because that projection gets a new primary key. Apply the schema with my schema apply -allow-destructive, as releases before v0.1.0 allow (#2309, #2541).

  • Renamed instance setting. retention_hook_decisions is renamed hook_decisions_retention_days. No compatibility shim is kept (#2309).

  • Renamed job types. Three job types are renamed (#2190):

    • webhook.purge → webhook.purge_messages
    • voice.media_event → voice.apply_media_event
    • finance.billing_import → finance.import_billing

    A queued job of an old type ends up dead. A worker_job_types that names an old type stops the server from starting.

Settings:

  • kms_key: it is now required only when key_manager is gcpkms or awskms. It is not required with the new key_manager = plugin, and setting it together with a plugin key manager is refused (#2290).
  • media is removed. Use media_image, media_video, and media_audio instead, each native or plugin, each with its own plugin_media_<kind>_* destination (#2407).
  • queue_sqs_queue_url is removed together with queue = sqs and AWS Lambda. On AWS, use ECS Fargate with another queue (#2315).
  • queue_sqs_routes is removed with queue = sqs (#2315).
  • queue_sqs_events_path is removed with queue = sqs and its Lambda event path (#2315).
  • queue_sqs_events_budget is removed with queue = sqs (#2315).

Breaking commits:

  • 46bfd0dc1: the media plugin kind and setting are split into image, video, and audio. Each kind can go to its own plugin or stay on the built-in processor (#2407).
  • 741687f6d: AWS Lambda is no longer a deployment target. The app-aws-lambda module, the queue-aws-sqs module, and the no_sqs build tag are removed. monitoring-aws now targets ECS and requires load_balancer_arn_suffix (#2315).
  • 208b62e0f: the libsql database option is removed. It never had an adapter (#2183).
  • 16a175251: status_sensitivity_overrides gets a primary key, so the projection is rebuilt, and the hook decision retention setting is renamed (#2309).
  • 758b90a2c: my admin relay remove is renamed my admin relay delete. A script that calls the old name now exits 2 (#2190).
  • 50150e98b: three more job types are renamed, as listed above. Check worker_job_types and drain the queue before upgrading (#2190).
  • 53e825035: in the OpenTofu modules, a network is a module role, and every module that needs one takes it from outside (#2267).
  • 69ff2ea04: the modules of one cloud work only with that cloud's app. Every backend must return platform, and a deployment that names no queue fails the plan (#2265).
  • 7fe3d1b74: the Cloud Run example uses the load balancer. Low cost is no longer treated as a design constraint (#2265).
  • 8cc20ae12: a db module returns both a direct and a pooled connection (#2264).
  • d1da1be6c: Cloudflare and CloudFront close the origin with the server's secret header (#2211).
  • c6ff00907: the service's ingress is an explicit setting of the app (#2211).
  • 91c7053fb: Cloud Tasks and Cloud Scheduler call the service's own run.app URL (#2211).
  • caf479b86: the module contract's roles are now permissions (#2211).

Also new for operators:

  • origin_secret makes the server refuse requests that did not come through the CDN (#2213).
  • ingress-aws-cloudfront now sits in front of the ALB for ECS (#2442).
  • Plugins can now take over the key manager, the mailer, the billing source, the media processor, the translator, and the search index (#2290, #2277, #2275, #2293, #2281, #2433).
  • PostgreSQL now returns times in UTC (#2530).

For API and library users

  • unfollowRelay: POST /admin/relays/{id}/unfollow is removed without a deprecation period. It is replaced by DELETE /admin/relays/{id}/follow, and the operation ID stays the same. The change was not a security fix. It came from the client API re-audit before v0.1.0, which corrected the API before it freezes (#2193).
  • Schema AdminAnnouncementList is removed. listAdminAnnouncements is now paginated: it returns AdminAnnouncementPage and takes state, cursor, and limit (#2410).
  • BillingImport.method gains the value plugin, for billing imported through a plugin (#2275).
  • 37a39175f: other fixes from the API re-audit (#2193):
    • Some fields of notifications now need the matching read scope.
    • Editing or deleting a direct post, or changing its quote policy, answers 404 to a token without read:direct.
    • Empty values answer 422.
    • testWebhook and redeliverWebhookDelivery answer 202.
    • AdminAccountRegistration.id is added.
  • New operations:
    • searchStatuses (#2280)
    • translateStatus (#2273)
    • The report translation operations (#2294)
    • forwardReport (#2297)
    • The hook decision and appeal operations (#2276, #2303, #2314)
    • New fields of Instance for search, translation, one-person mode, external reviews, and automatic deletion (#2449, #2450)
  • POST /statuses can answer 422 status-rejected when an automated review refuses the post (#2303).
  • AdminQueue.adapter no longer lists sqs (#2315).
  • mykit: the generated client no longer has POST /admin/relays/{id}/unfollow. unfollowRelay now sends DELETE /admin/relays/{id}/follow (#2193).
  • mybot: no changes.

Upgrading

Follow Upgrading. Run my db upgrade -check and my db upgrade even when this section lists no step; they then do nothing.

Data upgrade steps: None.

Projections that my db upgrade rebuilds: None.

Upgrade from: the same minor version (v0.1.Z).

To do by hand: None.

Breaking changes

Settings:

  • kms_key: required changed from when key_manager is not local to when key_manager is gcpkms or awskms
  • media is gone without an entry in the renamed and removed settings
  • queue_sqs_events_budget is gone without an entry in the renamed and removed settings
  • queue_sqs_events_path is gone without an entry in the renamed and removed settings
  • queue_sqs_queue_url is gone without an entry in the renamed and removed settings
  • queue_sqs_routes is gone without an entry in the renamed and removed settings

Client API:

  • unfollowRelay (POST /admin/relays/{id}/unfollow): not deprecated in v0.1.0-rc.3, which only a security fix allows; say why
  • schema AdminAnnouncementList
  • BillingImport.method: string enum cost_explorer / bigquery / ...
Read more

v0.1.0-rc.3

v0.1.0-rc.3 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 04 Nov 15:02
Immutable release. Only release title and notes can be modified.
60762ac

Main changes

  • A supporter is charged at most once for a subscription. Starting a Stripe checkout again used to leave the earlier page payable, so paying both pages charged twice. If you start again with the same plan and interval, you return to the open page with what you already typed, unless it has less than 15 minutes left. Any other start expires the earlier page and makes a new one. If an earlier page was already paid, you go to the return screen and get no new page. If two payments still meet, the server keeps the first subscription and cancels and refunds the other. (#2173)
  • Pending subscriptions close cleanly. When a pending subscription closes, for example because its plan was retired or its account was deleted, its checkout pages expire. A payment that still arrives is cancelled and refunded. (#2173)
  • Returning to a PAY.JP checkout works. If you left PAY.JP's checkout page and pressed "支払いに進む" again in the same hour, you got an error. You now get a page. (#2170)
  • The PAY.JP card page fills in your email. It uses the address entered at your first payment, not your account's current address. (#2170)
  • More Stripe currencies are accepted for plans. Plans in ARS, COP, IDR, ILS, KRW, PHP, RUB and ZAR were refused before and are now accepted. (#2168)

For operators

  • Before upgrading, check Stripe for duplicate subscriptions. Look for customers with two subscriptions that have the same metadata.my_subscription_id. (#2173)
    • The first reconciliation after the upgrade cancels the subscription that is not in use. It refunds all of that subscription's paid invoices, renewals included, because it gave the user nothing for any period.
    • To settle a case by hand instead, cancel that subscription in the Stripe dashboard before upgrading. The server then leaves it and its charges alone.
    • On PAY.JP, this bug cannot create a second subscription.
  • A restricted Stripe key needs one more permission: Refunds, Write (POST /v1/refunds). Without it, the server still cancels a second subscription, but it cannot refund it. Until the refund is done, the new warning duplicate_charge shows in the "Payment provider" section of /admin/supporters and in GET /api/v1/admin/payment_status. (#2173)
  • The supporters schema changed in schema/postgres/13-supporters.sql and schema/sqlite/13-supporters.sql. No data upgrade step is needed. Run my db upgrade -check and my db upgrade as usual; they do nothing here.
  • Stripe currency rules now match Stripe's documentation. (#2168)
    • BGN is no longer in the table of minimum amounts, because Stripe's list no longer has it.
    • UGX is now handled with two decimal places. This only affects how balance transactions are formatted.
  • Stripe's read limit is now documented. docs/operations/payments-stripe.md explains that the read limit is an allocation: 500 per transaction over 30 days, and at least 10,000 a month. On a quiet account, the 15-minute reconciliation interval comes close to that minimum. The document also rewrites its "Items to verify" section and the test clock passage. (#2168)
  • PAY.JP test-mode results are recorded. docs/operations/payments-payjp.md records what PAY.JP's test mode confirmed and rewrites its "Items to verify". Chargebacks remain unverified. (#2172)

For API and library users

  • PaymentStatus.warnings can now hold the new value duplicate_charge, in addition to no_webhook and reconciliation_corrected. The server reports it after cancelling a second subscription whose refund has not yet succeeded. A client that rejects unknown values of this enum must accept the new one. (#2173)
  • mykit and mybot have no changes of their own in this release.

Upgrading

Follow Upgrading. Run my db upgrade -check and my db upgrade even when this section lists no step; they then do nothing.

Data upgrade steps: None.

Projections that my db upgrade rebuilds: None.

Upgrade from: the same minor version (v0.1.Z).

To do by hand: None.

Breaking changes

Settings: None.

Client API:

  • PaymentStatus.warnings: array of string enum no_webhook / reconciliation_corrected / duplicate_charge, required, was array of string enum no_webhook / reconciliation_corrected, required

Schema contract:

  • schema/postgres/13-supporters.sql changed: review it for removed tables and columns, type changes, and new constraints
  • schema/sqlite/13-supporters.sql changed: review it for removed tables and columns, type changes, and new constraints

Commits marked !: None.

API changes

Added operations: None.

Added fields: None.

Added scopes: None.

Deprecated in this release: None.

Removed: None.

Changed:

  • PaymentStatus.warnings: array of string enum no_webhook / reconciliation_corrected / duplicate_charge, required, was array of string enum no_webhook / reconciliation_corrected, required

May be removed in this release (deprecated in an earlier release, Sunset passed): None.

Deprecated earlier and kept: None.

mykit

The client library of the client API, released with this version of the server
(pkg/mykit, MIT).

  • Go: go get github.com/mycroblog/my/pkg/mykit@v0.1.0-rc.3
  • npm: npm install @mycroblog/mykit@0.1.0-rc.3 (dist-tag next, with provenance)

None.

mybot

The bot library on top of mykit, released with the same version
(pkg/mybot, MIT).
Its npm package depends on @mycroblog/mykit@0.1.0-rc.3 exactly.

  • Go: go get github.com/mycroblog/my/pkg/mybot@v0.1.0-rc.3
  • npm: npm install @mycroblog/mybot@0.1.0-rc.3 (dist-tag next, with provenance)

None.

Full Changelog: v0.1.0-rc.2...v0.1.0-rc.3

Container image

ghcr.io/mycroblog/my:0.1.0-rc.3@sha256:fb46824a1545e22edc9f8d3bc71a4adc1c46a5a659be179bdf7eeeafe26efa04

v0.1.0-rc.2

v0.1.0-rc.2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 04 Nov 06:55
Immutable release. Only release title and notes can be modified.
b38c472

Main changes

Supporter subscriptions

  • An upgrade, or a move to the yearly price, now takes effect only after its payment is confirmed. If the payment fails, the subscription stays on its current plan and you see an error with a button to update your card in the payment portal. A card that asks for authentication counts as a failed payment, and the message tells you to update the card. If the payment is still processing, the plan changes once it succeeds. With PAY.JP, a difference below 50 yen, or a move to the yearly price of the same plan, has nothing to charge and applies at once. (#2167)
  • A cancellation made in Stripe's customer portal now shows on the server as a cancellation at the end of the period. You can undo it from the server's screen. While a cancellation is pending, the plan cannot be changed. (#2166)
  • A plan change scheduled for the end of the period can be made again after you withdrew it in the same period. Before, the second attempt failed with an error or silently scheduled nothing. (#2163)

Moderation

  • A reported post now shows its poll, quoted post, and link card to moderators.
    • Poll results are shown without a vote form.
    • A quoted post that is public, local, or unlisted is shown. A private or direct one only shows that a quote exists. (#2160)
  • Reactions now show correctly on reported posts and on posts where a reaction's emoji was deleted. (#2158)

For operators

  • Stripe restricted keys need Invoices: Write. When a plan change's payment fails, the server voids the unpaid invoice. Without this permission the void fails. Add it before upgrading if you use a restricted key. (#2167)
  • Stripe balance transactions need Balance Transaction Sources Read. Reading GET /v1/balance_transactions needs the "Balance Transaction Sources" Read permission (balance_transaction_source_read). The documentation in docs/operations/payments-stripe.md named "Balance" before. When Stripe refuses a key, the log now carries Stripe's message, which names the missing permission. The API and the administration still show only the kind of error. (#2161)
  • The release notes now give the container image with its digest, in the form to pin. (#2156)
  • This release has no breaking changes, no data upgrade steps, and no projections to rebuild. Follow the upgrading guide as usual.

For API and library users

  • A supporter plan change can now answer with two new problem types:
    • 402 supporter-payment-failed: the payment failed and the plan did not change.
    • 409 supporter-payment-processing: the payment is still processing, and the plan changes if it succeeds. (#2167)
  • A plan change on a subscription that is being canceled, including one canceled in Stripe's portal, is now refused. (#2166)
  • GET /admin/reports/{id} now fills the poll, the quote, and the link card of a reported post.
    • The poll has its options and counts, without voted and own_votes.
    • A quote the moderator may not read has state: unauthorized and no quoted_status.
    • quotable and quote_policy stay omitted. (#2160)

Upgrading

Follow Upgrading. Run my db upgrade -check and my db upgrade even when this section lists no step; they then do nothing.

Data upgrade steps: None.

Projections that my db upgrade rebuilds: None.

Upgrade from: the same minor version (v0.1.Z).

To do by hand: None.

Breaking changes

None.

API changes

None.

mykit

The client library of the client API, released with this version of the server
(pkg/mykit, MIT).

  • Go: go get github.com/mycroblog/my/pkg/mykit@v0.1.0-rc.2
  • npm: npm install @mycroblog/mykit@0.1.0-rc.2 (dist-tag next, with provenance)

None.

mybot

The bot library on top of mykit, released with the same version
(pkg/mybot, MIT).
Its npm package depends on @mycroblog/mykit@0.1.0-rc.2 exactly.

  • Go: go get github.com/mycroblog/my/pkg/mybot@v0.1.0-rc.2
  • npm: npm install @mycroblog/mybot@0.1.0-rc.2 (dist-tag next, with provenance)

None.

Full Changelog: v0.1.0-rc.1...v0.1.0-rc.2

Container image

ghcr.io/mycroblog/my:0.1.0-rc.2@sha256:c86f5bb24f0f0755f387d80801fcdd6be6eedccc20cb896c03ad2e5c244ced42

v0.1.0-rc.1

v0.1.0-rc.1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 04 Nov 02:55
Immutable release. Only release title and notes can be modified.
c262538

Main changes

This is the first release of my, an ActivityPub microblog server with its own web client.

  • Posting. Write posts with a content warning, a language, images, video and audio, polls, and quotes of other posts. You can choose who may quote you (#898, #904, #926, #772, #798). You can also:
    • Edit your posts and read their edit history (#688).
    • Pin posts to your profile (#689).
    • Send a post with Ctrl/Cmd+Enter, and attach media by pasting or dropping it into the form (#1896).
    • Complete mentions, hashtags and emoji as you type, with highlighting in the text (#1229, #1221).
  • Timelines and lists.
    • Home, local, federated and hashtag timelines. New posts arrive in real time on the local and federated timelines too, and are inserted automatically by default (#1914, #1915, #1912).
    • Lists of people you follow, each with its own timeline (#1893, #1899).
    • Bookmarks (#690).
    • Link cards for URLs in posts, in a large or a small layout (#773, #2031).
  • Reactions and emoji. React with any emoji, custom emoji included (#702, #726, #1196). The emoji picker has every Unicode emoji, sections, skin tones and search (#1188, #1189). Custom emoji are created through requests that administrators approve (#941).
  • Notifications.
    • Choose per type which notifications appear in the app, by Web Push, by email, and with a sound (#1633, #1636, #691).
    • Ring the bell on a profile to be notified of that account's new posts (#1894, #1897).
    • The latest notifications show beside the timelines on wide screens (#1937).
    • If this browser has no Web Push subscription, the notifications page offers to turn it on (#1993).
  • Voice chat rooms.
    • Open a room, speak or listen, raise a hand, and invite co-hosts (#1374, #1377, #1386, #1399).
    • The room page is laid out as a stage, and a mini-player follows you to other pages (#1435, #1436).
    • A room can have an emoji icon (#1892).
  • Accounts and sign-in.
    • Sign in with a password, a passkey, or TOTP two-factor authentication (#785, #696).
    • Sign in with external login providers that administrators set up: OpenID Connect, GitHub, Discord and Mastodon (#1592, #1593, #1600, #1594). You can also link and unlink these providers from the settings (#1596).
    • Reset and change your password (#800).
    • List the browsers signed in to your account and sign them out (#1989).
  • Managing your account and data.
    • Move your account to another server, and set aliases (#1268, #1275).
    • Deactivate your account for 30 days instead of deleting it (#2118). You can also delete it and export your data (#693).
    • Export and import follows, blocks, mutes and bookmarks as Mastodon CSV (#766).
    • Delete old posts automatically, and see how many posts the rules would delete before you save them (#765, #1802).
    • The app follows your browser's language and time zone by default (#1932).
    • Members can create invites when the server allows it (#1622, #1628).
  • The server's pages.
    • A landing page about the server (#1713).
    • An about page with the rules, terms and moderated domains (#760).
    • Server-wide announcements with a page for each (#768, #1898, #1939).
    • A supporter program with plans and a supporter list (#940, #947).
    • Published running costs and income (#897, #953).
  • Moderation and administration.
    • Reports, appeals, actions on accounts and domains, registration review, an audit log, and roles with badges (#437, #444, #429, #455, #763, #934).
    • Webhooks (#750) and an errors screen (#1463).
    • A custom server icon and logo (#1715, #1736).
  • Federation. Federation with Mastodon, Misskey, GoToSocial and Akkoma, including relays (#782), moves (#1256), and Object Integrity Proofs (#715). Administrators can choose whether the server sends, receives, or does both (#984).
  • The web client.
    • Installs as a PWA (#203).
    • The last loaded home timeline can be read offline (#745).
    • Uses the "my" design system (#1042).

For operators

This is the first release, so there is nothing to upgrade from and no breaking change. To start an instance, follow the Running and Database guides linked in the facts.

  • Container image. The server ships as a container image on ghcr.io/mycroblog/my, with provenance attestations (#2086). The Docker Compose file pulls the version you set in MY_VERSION (#2087).
  • Schema and backups.
    • my schema apply applies the schema from the binary itself, with no separate schema image (#1902).
    • my db backup takes a consistent copy of a SQLite database while the server runs (#1752).
  • Database, storage and keys. The database is SQLite or PostgreSQL. Media goes to the filesystem, S3-compatible storage, or Google Cloud Storage (#1762, #1863). Keys stay local or go to Google Cloud KMS or AWS KMS (#1858, #1859). my kek rewrap moves stored secrets after a key rotation (#1749).
  • Jobs.
    • Jobs run in the database queue. Cloud Tasks or SQS can carry the wake-up signals (#1860, #1861, #1862).
    • A worker can run only chosen job types (#2006) and several jobs at once (#2014).
  • Monitoring.
    • Metrics, tracing and error reporting, with optional export to Sentry-compatible or OTLP backends (#695, #827, #1453, #1456).
    • A public health endpoint (#1241).
    • A maintenance mode (#1240).
  • Configuration checks. my config check reports production-readiness problems and settings that my serve would refuse (#1330, #2149).

For API and library users

This is the first release of the client API, mykit, and mybot, so nothing changed for existing users.

  • The client API under /api/v1 is described by api/openapi.yaml, which the server also serves (#1223).
  • Third-party apps can register as OAuth clients, by Client ID Metadata Document, or by dynamic registration (#1227, #1225, #1226).
  • mykit is the API client library for Go and TypeScript, including the event stream (#1255, #1258, #1265).
  • mybot builds bots on top of it, in Go and TypeScript (#1271, #1281).

Upgrading

None. This is the first release, so there is nothing to upgrade from. To start an instance, follow Running and Database.

Breaking changes

None. This is the first release.

API changes

The first release of the client API (/api/v1): 362 operations and 33 scopes, described by api/openapi.yaml.

mykit

The client library of the client API, released with this version of the server
(pkg/mykit, MIT).

  • Go: go get github.com/mycroblog/my/pkg/mykit@v0.1.0-rc.1
  • npm: npm install @mycroblog/mykit@0.1.0-rc.1 (dist-tag next, with provenance)

None. This is the first release of mykit.

mybot

The bot library on top of mykit, released with the same version
(pkg/mybot, MIT).
Its npm package depends on @mycroblog/mykit@0.1.0-rc.1 exactly.

  • Go: go get github.com/mycroblog/my/pkg/mybot@v0.1.0-rc.1
  • npm: npm install @mycroblog/mybot@0.1.0-rc.1 (dist-tag next, with provenance)

None. This is the first release of mybot.

Full Changelog: https://github.com/mycroblog/my/commits/v0.1.0-rc.1