Tags give the ability to mark specific points in history as being important
  • v1.1.5   Retag with a version bump
    36f4382b · Bump mix.exs version ·
    Release v1.1.5

    [1.1.5] - 2019-11-09

    Fixed

    • Polls having different numbers in timelines/notifications/poll api endpoints due to cache desyncronization
    • Pleroma API: OAuth token endpoint not being found when ".json" suffix is appended

    Changed

  • v1.1.4   1.1.4 release.
    Release v1.1.4

    [1.1.4] - 2019-11-01

    Fixed

    • Added a migration that fills up empty user.info fields to prevent breakage after previous unsafe migrations.
    • Failure to migrate from pre-1.0.0 versions
    • Mastodon API: Notification stream not including follow notifications
  • v1.1.3
    Release v1.1.3

    [1.1.3] - 2019-10-25

    Fixed

    • Blocked users showing up in notifications collapsed as if they were muted
    • pleroma_ctl not working on Debian's default shell
  • v1.1.2
    Release v1.1.2

    [1.1.2] - 2019-10-18

    Fixed

    • pleroma_ctl trying to connect to a running instance when generating the config, which of course doesn't exist.
  • v1.1.1
    Release v1.1.1

    [1.1.1] - 2019-10-18

    Fixed

    • One of the migrations between 1.0.0 and 1.1.0 wiping user info of the relay user because of unexpected behavior of postgresql's jsonb_set, resulting in inability to post in the default configuration. If you were affected, please run the following query in postgres console, the relay user will be recreated automatically:
    delete from users where ap_id = 'https://your.instance.hostname/relay';
    • Bad user search matches
  • v1.1.0
    442acb31 · Fix pleroma_ctl link ·
    Release v1.1.0

    [1.1.0] - 2019-10-14

    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:

    curl -Lo ./bin/pleroma_ctl 'https://git.pleroma.social/pleroma/pleroma/raw/develop/rel/files/bin/pleroma_ctl'

    Security

    • Mastodon API: respect post privacy in /api/v1/statuses/:id/{favourited,reblogged}_by

    Removed

    • Breaking: GNU Social API with Qvitter extensions support
    • Emoji: Remove longfox emojis.
    • Remove Reply-To header from report emails for admins.
    • ActivityPub: The /objects/:uuid/likes endpoint.

    Changed

    • Breaking: Configuration: A setting to explicitly disable the mailer was added, defaulting to true, if you are using a mailer add config :pleroma, Pleroma.Emails.Mailer, enabled: true to your config
    • Breaking: Configuration: /media/ is now removed when base_url is configured, append /media/ to your base_url config to keep the old behaviour if desired
    • Breaking: /api/pleroma/notifications/read is moved to /api/v1/pleroma/notifications/read and now supports max_id and responds with Mastodon API entities.
    • Configuration: added config/description.exs, from which docs/config.md is generated
    • Configuration: OpenGraph and TwitterCard providers enabled by default
    • Configuration: Filter.AnonymizeFilename added ability to retain file extension with custom text
    • Federation: Return 403 errors when trying to request pages from a user's follower/following collections if they have hide_followers/hide_follows set
    • NodeInfo: Return skipThreadContainment in metadata for the skip_thread_containment option
    • NodeInfo: Return mailerEnabled in metadata
    • Mastodon API: Unsubscribe followers when they unfollow a user
    • Mastodon API: pleroma.thread_muted key in the Status entity
    • AdminAPI: Add "godmode" while fetching user statuses (i.e. admin can see private statuses)
    • Improve digest email template – Pagination: (optional) return total alongside with items when paginating
    • The Pleroma.FlakeId module has been replaced with the flake_id library.

    Fixed

    • Following from Osada
    • Favorites timeline doing database-intensive queries
    • 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

    Added

    • 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)
    • Mastodon API: Support for the tagged filter in GET /api/v1/accounts/:id/statuses
    • Mastodon API, streaming: Add support for passing the token in the Sec-WebSocket-Protocol header
    • Mastodon API, extension: Ability to reset avatar, profile banner, and background
    • Mastodon API: Add support for fields_attributes API parameter (setting custom fields)
    • Mastodon API: Add support for categories for custom emojis by reusing the group feature. https://github.com/tootsuite/mastodon/pull/11196
    • Mastodon API: Add support for muting/unmuting notifications
    • Mastodon API: Add support for the blocked_by attribute in the relationship API (GET /api/v1/accounts/relationships). https://github.com/tootsuite/mastodon/pull/10373
    • Mastodon API: Add support for the domain_blocking attribute in the relationship API (GET /api/v1/accounts/relationships).
    • Mastodon API: Add pleroma.deactivated to the Account entity
    • Mastodon API: added /auth/password endpoint for password reset with rate limit.
    • Mastodon API: /api/v1/accounts/:id/statuses now supports nicknames or user id
    • Mastodon API: Improve support for the user profile custom fields
    • Mastodon API: Add support for fields_attributes API parameter (setting custom fields)
    • Mastodon API: Added an endpoint to get multiple statuses by IDs (GET /api/v1/statuses/?ids[]=1&ids[]=2)
    • Admin API: Return users' tags when querying reports
    • Admin API: Return avatar and display name when querying users
    • Admin API: Allow querying user by ID
    • Admin API: Added support for tuples.
    • Admin API: Added endpoints to run mix tasks pleroma.config migrate_to_db & pleroma.config migrate_from_db
    • Added synchronization of following/followers counters for external users
    • Configuration: enabled option for Pleroma.Emails.Mailer, defaulting to false.
    • Configuration: Pleroma.Plugs.RateLimiter bucket_name, params options.
    • Configuration: user_bio_length and user_name_length options.
    • Addressable lists
    • Twitter API: added rate limit for /api/account/password_reset endpoint.
    • ActivityPub: Add an internal service actor for fetching ActivityPub objects.
    • ActivityPub: Optional signing of ActivityPub object fetches.
    • Admin API: Endpoint for fetching latest user's statuses
    • Pleroma API: Add /api/v1/pleroma/accounts/confirmation_resend?email=<email> for resending account confirmation.
    • Pleroma API: Email change endpoint.
    • Admin API: Added moderation log
    • Web response cache (currently, enabled for ActivityPub)
    • Reverse Proxy: Do not retry failed requests to limit pressure on the peer

    Changed

    • Configuration: Filter.AnonymizeFilename added ability to retain file extension with custom text
    • Admin API: changed json structure for saving config settings.
    • RichMedia: parsers and their order are configured in rich_media config.
    • RichMedia: add the rich media ttl based on image expiration time.
  • v1.0.91
    Release v1.0.91

    [1.0.91] - 2019-10-06

    Added

    • Reverse Proxy: Do not retry failed requests to limit pressure on the peer
    • Mastodon API: Add support for fields_attributes API parameter (setting custom fields)

    Fixed

    • 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
    • ActivityPub: Correct addressing of Undo.
    • ActivityPub: Correct addressing of profile update activities.
    • ActivityPub: Polls are now refreshed when necessary.
    • Mastodon API: Ensure the account field is not empty when rendering Notification entities.
    • Report emails now include functional links to profiles of remote user accounts
    • Mastodon API: Fix private and direct statuses not being filtered out from the public timeline for an authenticated user (GET /api/v1/timelines/public)

    Removed

    • ActivityPub: The /objects/:uuid/likes endpoint.

    Changed

    • The Pleroma.FlakeId module has been replaced with the flake_id library.
  • v1.0.90
    Release v1.0.90

    [1.0.90] - 2019-09-30

    Warning: This is the first 1.1.x release candidate and may be unstable. It is recommended to use 1.0.7 instead if stability is required.

    Security

    • OStatus: eliminate the possibility of a protocol downgrade attack.
    • OStatus: prevent following locked accounts, bypassing the approval process.
    • Mastodon API: respect post privacy in /api/v1/statuses/:id/{favourited,reblogged}_by

    Removed

    • Breaking: GNU Social API with Qvitter extensions support
    • Breaking: ActivityPub: The accept_blocks configuration setting.
    • Emoji: Remove longfox emojis.
    • Remove Reply-To header from report emails for admins.

    Changed

    • Breaking: Configuration: A setting to explicitly disable the mailer was added, defaulting to true, if you are using a mailer add config :pleroma, Pleroma.Emails.Mailer, enabled: true to your config
    • Breaking: Configuration: /media/ is now removed when base_url is configured, append /media/ to your base_url config to keep the old behaviour if desired
    • Breaking: /api/pleroma/notifications/read is moved to /api/v1/pleroma/notifications/read and now supports max_id and responds with Mastodon API entities.
    • Configuration: OpenGraph and TwitterCard providers enabled by default
    • Configuration: Filter.AnonymizeFilename added ability to retain file extension with custom text
    • Configuration: added config/description.exs, from which docs/config.md is generated
    • Federation: Return 403 errors when trying to request pages from a user's follower/following collections if they have hide_followers/hide_follows set
    • NodeInfo: Return skipThreadContainment in metadata for the skip_thread_containment option
    • NodeInfo: Return mailerEnabled in metadata
    • Mastodon API: Unsubscribe followers when they unfollow a user
    • Mastodon API: pleroma.thread_muted key in the Status entity
    • AdminAPI: Add "godmode" while fetching user statuses (i.e. admin can see private statuses)
    • Improve digest email template – Pagination: (optional) return total alongside with items when paginating
    • ActivityPub: The first page in inboxes/outboxes is no longer embedded.

    Fixed

    • Following from Osada
    • Not being able to pin unlisted posts
    • Objects being re-embedded to activities after being updated (e.g faved/reposted). Running 'mix pleroma.database prune_objects' again is advised.
    • Favorites timeline doing database-intensive queries
    • Metadata rendering errors resulting in the entire page being inaccessible
    • federation_incoming_replies_max_depth option being ignored in certain cases
    • Federation/MediaProxy not working with instances that have wrong certificate order
    • 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: follower/following counters not being nullified, when hide_follows/hide_followers is set
    • Mastodon API: muted in the Status entity, using author's account to determine if the tread was muted
    • 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
    • ActivityPub C2S: follower/following collection pages being inaccessible even when authentifucated if hide_followers/ hide_follows was set
    • Existing user id not being preserved on insert conflict
    • 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 S2S: remote user deletions now work the same as local user deletions.
    • ActivityPub S2S: POST requests are now signed with (request-target) pseudo-header.
    • Not being able to access the Mastodon FE login page on private instances
    • Invalid SemVer version generation, when the current branch does not have commits ahead of tag/checked out on a tag
    • 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
    • MRF: ensure that subdomain_match calls are case-insensitive
    • Reverse Proxy limiting max_body_length was incorrectly defined and only checked Content-Length headers which may not be sufficient in some circumstances
    • MRF: fix use of unserializable keyword lists in describe() implementations
    • 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

    Added

    • 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.
    • Breaking: MRF describe API, which adds support for exposing configuration information about MRF policies to NodeInfo. Custom modules will need to be updated by adding, at the very least, def describe, do: {:ok, %{}} to the MRF policy modules.
    • 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)
    • MRF: Support for filtering posts based on ActivityStreams vocabulary (Pleroma.Web.ActivityPub.MRF.VocabularyPolicy)
    • MRF (Simple Policy): Support for wildcard domains.
    • Support for wildcard domains in user domain blocks setting.
    • Configuration: quarantined_instances support wildcard domains.
    • Configuration: federation_incoming_replies_max_depth option
    • Mastodon API: Support for the tagged filter in GET /api/v1/accounts/:id/statuses
    • Mastodon API, streaming: Add support for passing the token in the Sec-WebSocket-Protocol header
    • Mastodon API, extension: Ability to reset avatar, profile banner, and background
    • Mastodon API: Add support for categories for custom emojis by reusing the group feature. https://github.com/tootsuite/mastodon/pull/11196
    • Mastodon API: Add support for muting/unmuting notifications
    • Mastodon API: Add support for the blocked_by attribute in the relationship API (GET /api/v1/accounts/relationships). https://github.com/tootsuite/mastodon/pull/10373
    • Mastodon API: Add support for the domain_blocking attribute in the relationship API (GET /api/v1/accounts/relationships).
    • Mastodon API: Add pleroma.deactivated to the Account entity
    • Mastodon API: added /auth/password endpoint for password reset with rate limit.
    • Mastodon API: /api/v1/accounts/:id/statuses now supports nicknames or user id
    • Mastodon API: Improve support for the user profile custom fields
    • Admin API: Return users' tags when querying reports
    • Admin API: Return avatar and display name when querying users
    • Admin API: Allow querying user by ID
    • Admin API: Added support for tuples.
    • Admin API: Added endpoints to run mix tasks pleroma.config migrate_to_db & pleroma.config migrate_from_db
    • Added synchronization of following/followers counters for external users
    • Configuration: enabled option for Pleroma.Emails.Mailer, defaulting to false.
    • Configuration: Pleroma.Plugs.RateLimiter bucket_name, params options.
    • Configuration: user_bio_length and user_name_length options.
    • Addressable lists
    • Twitter API: added rate limit for /api/account/password_reset endpoint.
    • ActivityPub: Add an internal service actor for fetching ActivityPub objects.
    • ActivityPub: Optional signing of ActivityPub object fetches.
    • Admin API: Endpoint for fetching latest user's statuses
    • Pleroma API: Add /api/v1/pleroma/accounts/confirmation_resend?email=<email> for resending account confirmation.
    • Pleroma API: Email change endpoint.
    • Relays: Added a task to list relay subscriptions.
    • Mix Tasks: mix pleroma.database fix_likes_collections
    • Federation: Remove likes from objects.
    • Admin API: Added moderation log
    • Web response cache (currently, enabled for ActivityPub)
    • Mastodon API: Added an endpoint to get multiple statuses by IDs (GET /api/v1/statuses/?ids[]=1&ids[]=2)

    Changed

    • Configuration: Filter.AnonymizeFilename added ability to retain file extension with custom text
    • Admin API: changed json structure for saving config settings.
    • RichMedia: parsers and their order are configured in rich_media config.
    • RichMedia: add the rich media ttl based on image expiration time.
  • v1.0.7
    Release v1.0.7

    [1.0.7] - 2019-09-26

    Fixed

    • Broken federation on Erlang 22 (previous versions of hackney http client were using an option that got deprecated)

    Changed

    • ActivityPub: The first page in inboxes/outboxes is no longer embedded.
  • v1.0.6
    Release v1.0.6

    [1.0.6] - 2019-08-14

    Fixed

    • MRF: fix use of unserializable keyword lists in describe() implementations
    • ActivityPub S2S: POST requests are now signed with (request-target) pseudo-header.
  • v1.0.5
    Release v1.0.5

    [1.0.5] - 2019-08-13

    Fixed

    • Mastodon API: follower/following counters not being nullified, when hide_follows/hide_followers is set
    • Mastodon API: muted in the Status entity, using author's account to determine if the thread was muted
    • Mastodon API: return the actual profile URL in the Account entity's url property when appropriate
    • Templates: properly style anchor tags
    • Objects being re-embedded to activities after being updated (e.g faved/reposted). Running 'mix pleroma.database prune_objects' again is advised.
    • Not being able to access the Mastodon FE login page on private instances
    • MRF: ensure that subdomain_match calls are case-insensitive
    • Fix internal server error when using the healthcheck API.

    Added

    • Breaking: MRF describe API, which adds support for exposing configuration information about MRF policies to NodeInfo. Custom modules will need to be updated by adding, at the very least, def describe, do: {:ok, %{}} to the MRF policy modules.
    • Relays: Added a task to list relay subscriptions.
    • MRF: Support for filtering posts based on ActivityStreams vocabulary (Pleroma.Web.ActivityPub.MRF.VocabularyPolicy)
    • MRF (Simple Policy): Support for wildcard domains.
    • Support for wildcard domains in user domain blocks setting.
    • Configuration: quarantined_instances support wildcard domains.
    • Mix Tasks: mix pleroma.database fix_likes_collections
    • Configuration: federation_incoming_replies_max_depth option

    Removed

    • Federation: Remove likes from objects.
    • ActivityPub: The accept_blocks configuration setting.
  • v1.0.4
    Release v1.0.4

    [1.0.4] - 2019-08-01

    Fixed

    • Invalid SemVer version generation, when the current branch does not have commits ahead of tag/checked out on a tag
  • v1.0.3
    Release v1.0.3

    [1.0.3] - 2019-07-31

    Security

    • OStatus: eliminate the possibility of a protocol downgrade attack.
    • OStatus: prevent following locked accounts, bypassing the approval process.
    • TwitterAPI: use CommonAPI to handle remote follows instead of OStatus.

    Fixed

    • pleroma_ctl not detecting the master branch properly. If you get "Releases are built only for master and develop branches" error when updating, please add - to the end of the line in releases/start_erl.data
  • v1.0.2
    Release v1.0.2

    [1.0.2] - 2019-07-28

    Fixed

    • Not being able to pin unlisted posts
    • Mastodon API: represent poll IDs as strings
    • MediaProxy: fix matching filenames
    • MediaProxy: fix filename encoding
    • Migrations: fix a sporadic migration failure
    • Metadata rendering errors resulting in the entire page being inaccessible
    • Federation/MediaProxy not working with instances that have wrong certificate order
    • ActivityPub S2S: remote user deletions now work the same as local user deletions.

    Changed

    • Configuration: OpenGraph and TwitterCard providers enabled by default
    • Configuration: Filter.AnonymizeFilename added ability to retain file extension with custom text
  • v1.0.1
    Release v1.0.1

    [1.0.1] - 2019-07-14

    Security

    • OStatus: fix an object spoofing vulnerability.

    Added

    • MRF: Support for excluding specific domains from Transparency.
  • v1.0.0
    Release v1.0.0

    [1.0.0] - 2019-06-29

    Security

    • Mastodon API: Fix display names not being sanitized
    • Rich media: Do not crawl private IP ranges

    Added

    • Scheduled statuses
    • Polls
    • Add a generic settings store for frontends / clients to use.
    • Explicit addressing option for posting.
    • Optional SSH access mode. (Needs erlang-ssh package on some distributions).
    • MongooseIM http authentication support.
    • LDAP authentication
    • External OAuth provider authentication
    • Support for building a release using mix release
    • A job queue for federation, emails, web push, etc.
    • Prometheus metrics
    • Support for Mastodon's remote interaction
    • Mix Tasks: mix pleroma.database bump_all_conversations
    • Mix Tasks: mix pleroma.database remove_embedded_objects
    • Mix Tasks: mix pleroma.database update_users_following_followers_counts
    • Mix Tasks: mix pleroma.user toggle_confirmed
    • Mix Tasks: mix pleroma.config migrate_to_db
    • Mix Tasks: mix pleroma.config migrate_from_db
    • Support for reports
    • Configuration: poll_limits option
    • Configuration: pack_extensions option
    • Configuration: safe_dm_mentions option
    • Configuration: link_name option
    • Configuration: fetch_initial_posts option
    • Configuration: notify_email option
    • Configuration: Media proxy whitelist option
    • Configuration: report_uri option
    • Configuration: limit_to_local_content option
    • AdminFE: initial release with basic user/report management accessible at /pleroma/admin/
    • Metadata: RelMe provider
    • OAuth: added support for refresh tokens
    • Emoji packs and emoji pack manager
    • Object pruning (mix pleroma.database prune_objects)
    • OAuth: added job to clean expired access tokens
    • MRF: Support for rejecting reports from specific instances (mrf_simple)
    • MRF: Support for stripping avatars and banner images from specific instances (mrf_simple)
    • MRF: Support for running subchains.
    • Configuration: skip_thread_containment option
    • Configuration: rate_limit option. See Pleroma.Plugs.RateLimiter documentation for details.
    • MRF: Support for filtering out likely spam messages by rejecting posts from new users that contain links.
    • Configuration: ignore_hosts option
    • Configuration: ignore_tld option
    • Configuration: default syslog tag "Pleroma" is now lowercased to "pleroma"

    Changed

    • Breaking: bind to 127.0.0.1 instead of 0.0.0.0 by default
    • Breaking: Configuration: move from Pleroma.Mailer to Pleroma.Emails.Mailer
    • Thread containment / test for complete visibility will be skipped by default.
    • Enforcement of OAuth scopes
    • Add multiple use/time expiring invite token
    • Restyled OAuth pages to fit with Pleroma's default theme
    • Link/mention/hashtag detection is now handled by auto_linker
    • Configuration: Dedupe enabled by default
    • Configuration: Default log level in prod environment is now set to warn
    • Configuration: Added extra_cookie_attrs for setting non-standard cookie attributes. Defaults to ["SameSite=Lax"] so that remote follows work.
    • Timelines: Messages involving people you have blocked will be excluded from the timeline in all cases instead of just repeats.
    • Don't ship finmoji by default, they can be installed as an emoji pack
    • Hide deactivated users and their statuses
    • Posts which are marked sensitive or tagged nsfw no longer have link previews.
    • HTTP connection timeout is now set to 10 seconds.
    • Rich Media: crawl only https URLs.

    Fixed

    • Follow requests don't get 'stuck' anymore.
    • Added an FTS index on objects. Running vacuum analyze and setting a larger work_mem is recommended.
    • Followers counter not being updated when a follower is blocked
    • Deactivated users being able to request an access token
    • Limit on request body in rich media/relme parsers being ignored resulting in a possible memory leak
    • Proper Twitter Card generation instead of a dummy
    • Deletions failing for users with a large number of posts
    • NodeInfo: Include admins in staffAccounts
    • ActivityPub: Crashing when requesting empty local user's outbox
    • Federation: Handling of objects without summary property
    • Federation: Add a language tag to activities as required by ActivityStreams 2.0
    • Federation: Do not federate avatar/banner if set to default allowing other servers/clients to use their defaults
    • Federation: Cope with missing or explicitly nulled address lists
    • Federation: Explicitly ensure activities addressed to as:Public become addressed to the followers collection
    • Federation: Better cope with actors which do not declare a followers collection and use as:Public with these semantics
    • Federation: Follow requests from remote users who have been blocked will be automatically rejected if appropriate
    • MediaProxy: Parse name from content disposition headers even for non-whitelisted types
    • MediaProxy: S3 link encoding
    • Rich Media: Reject any data which cannot be explicitly encoded into JSON
    • Importing follows from Mastodon 2.8+
    • User-Agent is now sent correctly for all HTTP requests.
    • MRF: Simple policy now properly delists imported or relayed statuses

    Removed

    • Configuration: config :pleroma, :fe in favor of the more flexible config :pleroma, :frontend_configurations

    For more API/federation changes refer to the the changelog

  • v0.9.99999   v.0.99999

    [0.9.99999] - 2019-05-31

    Security

    • Mastodon API: Fix lists leaking private posts
    • HTML escaping: Lock down allowed class attributes to only those related to microformats
  • v0.9.9999
    3591b7c1 · Update versions. ·

    Security fixes.

  • v0.9.999   The 0.9.999 release.

    Frontend changes only.

    Changes:

    • Fix . activating when typing a message
    • Fix gaps when scrolling down on a timeline after showing new
    • Added floating action button for posting status on mobile
    • Changed user-settings icon to a pencil
  • v0.9.99   0.9.99 bugfix release.

    Changelog

    [0.9.99] - 2019-03-08

    Changed

    • Update the frontend to the 0.9.99 tag
    • Sign the date header in federation to fix Mastodon federation.