2023-07-22 09:38:22 -07:00
|
|
|
0.10
|
|
|
|
|
====
|
2023-07-07 14:14:06 -07:00
|
|
|
|
2023-11-12 13:39:24 -08:00
|
|
|
*Released: 2023/11/12*
|
2023-07-07 14:14:06 -07:00
|
|
|
|
2023-11-12 13:12:06 -08:00
|
|
|
This release is a polish release that mostly focuses on performance, stability
|
|
|
|
|
and federation compatibility.
|
2023-07-07 14:14:06 -07:00
|
|
|
|
|
|
|
|
This release's major changes:
|
|
|
|
|
|
|
|
|
|
* Stator, the background task system, has been significantly reworked to require
|
|
|
|
|
smaller indexes, spend less time scheduling, and has had most of its async
|
|
|
|
|
nature removed, as this both reduces deadlocks and improves performance in
|
|
|
|
|
most situations (the context switching was costing more than the gains from
|
|
|
|
|
talking to other servers asynchronously).
|
|
|
|
|
|
2023-07-22 09:38:22 -07:00
|
|
|
Minor changes also include:
|
|
|
|
|
|
|
|
|
|
* Followers-only mode now works correctly inbound and outbound (though outbound
|
|
|
|
|
may need the other server to refresh the profile first).
|
|
|
|
|
|
2023-09-07 21:06:50 -07:00
|
|
|
* Profile pages are no longer shown for remote identities; instead, users are
|
|
|
|
|
linked or redirected directly to the remote profile page.
|
|
|
|
|
|
2023-11-09 10:58:40 -08:00
|
|
|
* Inbound migration has been implemented, but is disabled by default as outbound
|
|
|
|
|
migration is not yet complete, and we don't want to release a system that
|
|
|
|
|
captures users with no outward path. If you *really* want to enable it, set
|
|
|
|
|
``TAKAHE_ALLOW_USER_MIGRATION=true`` in your environment.
|
|
|
|
|
|
2023-11-09 11:10:31 -08:00
|
|
|
* Federation compatibility has been improved with several other servers.
|
|
|
|
|
|
|
|
|
|
* Blocked domains now receive absolutely zero fetches from Takahē; previously,
|
|
|
|
|
they were still pinged occasionally to see if they were online.
|
|
|
|
|
|
|
|
|
|
* SMTP servers that don't require authentication are now supported.
|
|
|
|
|
|
2023-11-09 11:19:56 -08:00
|
|
|
* Python 3.11 is now the minimum version required; this will not affect you at
|
|
|
|
|
all if you run Takahē via a docker image, as is recommended.
|
|
|
|
|
|
2023-11-12 13:12:06 -08:00
|
|
|
A remote post pruning system, to shrink the database of old data that was no
|
|
|
|
|
longer needed, was in the development version but has been removed in this
|
|
|
|
|
release due to the extra database load it caused. An alternative approach to
|
|
|
|
|
this will hopefully land in a future release.
|
|
|
|
|
|
2023-07-07 14:14:06 -07:00
|
|
|
If you'd like to help with code, design, or other areas, see
|
|
|
|
|
:doc:`/contributing` to see how to get in touch.
|
|
|
|
|
|
|
|
|
|
You can download images from `Docker Hub <https://hub.docker.com/r/jointakahe/takahe>`_,
|
|
|
|
|
or use the image name ``jointakahe/takahe:0.10``.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Upgrade Notes
|
|
|
|
|
-------------
|
|
|
|
|
|
2023-10-01 09:49:10 -07:00
|
|
|
Remote Pruning
|
|
|
|
|
~~~~~~~~~~~~~~
|
2023-07-15 11:37:34 -07:00
|
|
|
|
2023-10-01 09:49:10 -07:00
|
|
|
Post pruning is now in and comes *enabled by default*, as it is not directly
|
|
|
|
|
destructive (it will only delete content that has not been interacted with
|
|
|
|
|
locally and which can be re-fetched).
|
2023-07-15 11:37:34 -07:00
|
|
|
|
2023-10-01 09:49:10 -07:00
|
|
|
Nevertheless, if you want to avoid post deletion triggering on your server at
|
|
|
|
|
all, you should set the ``TAKAHE_REMOTE_PRUNE_HORIZON`` environment variable to
|
|
|
|
|
``0``.
|
2023-07-15 11:37:34 -07:00
|
|
|
|
2023-07-07 14:14:06 -07:00
|
|
|
Migrations
|
|
|
|
|
~~~~~~~~~~
|
|
|
|
|
|
|
|
|
|
There are new database migrations; they are backwards-compatible, but contain
|
|
|
|
|
very significant index changes to all of the main tables that may cause the
|
|
|
|
|
PostgreSQL deadlock detector to trigger if you attempt to apply them while your
|
|
|
|
|
site is live.
|
|
|
|
|
|
|
|
|
|
We recommend:
|
|
|
|
|
|
|
|
|
|
* Temporarily stopping all instances of the webserver and Stator
|
|
|
|
|
* Applying the migration (should be less than a few minutes on most installs)
|
|
|
|
|
* Restarting the instances of webserver and Stator
|
