Breaking: The stable branch has been changed from master to stable. If you want to keep using 1.0, the release/1.0 branch will receive security updates for 6 months after 1.1 release.
OTP Note:pleroma_ctl in 1.0 defaults to master and doesn't support specifying arbitrary branches, making ./pleroma_ctl update fail. To fix this, fetch a version of pleroma_ctl from 1.1 using the command below and proceed with the update normally:
Metadata rendering errors resulting in the entire page being inaccessible
federation_incoming_replies_max_depth option being ignored in certain cases
Mastodon API: Handling of search timeouts (/api/v1/search and /api/v2/search)
Mastodon API: Misskey's endless polls being unable to render
Mastodon API: Embedded relationships not being properly rendered in the Account entity of Status entity
Mastodon API: Notifications endpoint crashing if one notification failed to render
Mastodon API: exclude_replies is correctly handled again.
Mastodon API: Add account_id, type, offset, and limit to search API (/api/v1/search and /api/v2/search)
Mastodon API, streaming: Fix filtering of notifications based on blocks/mutes/thread mutes
Mastodon API: Fix private and direct statuses not being filtered out from the public timeline for an authenticated user (GET /api/v1/timelines/public)
Mastodon API: Ensure the account field is not empty when rendering Notification entities.
Mastodon API: Inability to get some local users by nickname in /api/v1/accounts/:id_or_nickname
Mastodon API: Blocks are now treated consistently between the Streaming API and the Timeline APIs
Rich Media: Parser failing when no TTL can be found by image TTL setters
Rich Media: The crawled URL is now spliced into the rich media data.
ActivityPub S2S: sharedInbox usage has been mostly aligned with the rules in the AP specification.
ActivityPub C2S: follower/following collection pages being inaccessible even when authentifucated if hide_followers/ hide_follows was set
ActivityPub: Deactivated user deletion
ActivityPub: Fix /users/:nickname/inbox crashing without an authenticated user
MRF: fix ability to follow a relay when AntiFollowbotPolicy was enabled
ActivityPub: Correct addressing of Undo.
ActivityPub: Correct addressing of profile update activities.
ActivityPub: Polls are now refreshed when necessary.
Report emails now include functional links to profiles of remote user accounts
Existing user id not being preserved on insert conflict
Pleroma.Upload base_url was not automatically whitelisted by MediaProxy. Now your custom CDN or file hosting will be accessed directly as expected.
Report email not being sent to admins when the reporter is a remote user
Reverse Proxy limiting max_body_length was incorrectly defined and only checked Content-Length headers which may not be sufficient in some circumstances
Expiring/ephemeral activites. All activities can have expires_at value set, which controls when they should be deleted automatically.
Mastodon API: in post_status, the expires_in parameter lets you set the number of seconds until an activity expires. It must be at least one hour.
Mastodon API: all status JSON responses contain a pleroma.expires_at item which states when an activity will expire. The value is only shown to the user who created the activity. To everyone else it's empty.
Configuration: ActivityExpiration.enabled controls whether expired activites will get deleted at the appropriate time. Enabled by default.
Conversations: Add Pleroma-specific conversation endpoints and status posting extensions. Run the bump_all_conversations task again to create the necessary data.
MRF: Support for priming the mediaproxy cache (Pleroma.Web.ActivityPub.MRF.MediaProxyWarmingPolicy)
MRF: Support for excluding specific domains from Transparency.
MRF: Support for filtering posts based on who they mention (Pleroma.Web.ActivityPub.MRF.MentionPolicy)