72d4d1b392
TwitterCard meta tags are supposed to use the attributes "name" and "content". OpenGraph tags use the attributes "property" and "content". Twitter itself is smart enough to detect broken meta tags and discover the TwitterCard using "property" and "content", but other platforms that only implement parsing of TwitterCards and not OpenGraph may fail to correctly detect the tags as they're under the wrong attributes. > "Open Graph protocol also specifies the use of property and content attributes for markup while > Twitter cards use name and content. Twitter’s parser will fall back to using property and content, > so there is no need to modify existing Open Graph protocol markup if it already exists." [0] [0] https://developer.twitter.com/en/docs/twitter-for-websites/cards/guides/getting-started
1277 lines
72 KiB
Markdown
1277 lines
72 KiB
Markdown
# Changelog
|
||
|
||
All notable changes to this project will be documented in this file.
|
||
|
||
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
|
||
|
||
## Unreleased
|
||
|
||
### Removed
|
||
|
||
- MastoFE
|
||
|
||
### Changed
|
||
- **Breaking:** Elixir >=1.10 is now required (was >= 1.9)
|
||
- Allow users to remove their emails if instance does not need email to register
|
||
- Uploadfilter `Pleroma.Upload.Filter.Exiftool` has been renamed to `Pleroma.Upload.Filter.Exiftool.StripLocation`
|
||
- **Breaking**: `/api/v1/pleroma/backups` endpoints now requires `read:backups` scope instead of `read:accounts`
|
||
- Updated the recommended pleroma.vcl configuration for Varnish to target Varnish 7.0+
|
||
- Set timeout values for Oban queues. The default is infinity and some operations may not time out on their own.
|
||
- Delete activities are federated at lowest priority
|
||
- CSP now includes wasm-unsafe-eval
|
||
|
||
### Added
|
||
- `activeMonth` and `activeHalfyear` fields in NodeInfo usage.users object
|
||
- Experimental support for Finch. Put `config :tesla, :adapter, {Tesla.Adapter.Finch, name: MyFinch}` in your secrets file to use it. Reverse Proxy will still use Hackney.
|
||
- `ForceMentionsInPostContent` MRF policy
|
||
- AdminAPI: allow moderators to manage reports, users, invites, and custom emojis
|
||
- AdminAPI: restrict moderators to access sensitive data: change user credentials, get password reset token, read private statuses and chats, etc
|
||
- PleromaAPI: Add remote follow API endpoint at `POST /api/v1/pleroma/remote_interaction`
|
||
- MastoAPI: Add `GET /api/v1/accounts/lookup`
|
||
- MastoAPI: Profile Directory support
|
||
- MastoAPI: Support v2 Suggestions (handpicked accounts only)
|
||
- Ability to log slow Ecto queries by configuring `:pleroma, :telemetry, :slow_queries_logging`
|
||
- Added Phoenix LiveDashboard at `/phoenix/live_dashboard`
|
||
- Added `/manifest.json` for progressive web apps.
|
||
- MastoAPI: Support for `birthday` and `show_birthday` field in `/api/v1/accounts/update_credentials`.
|
||
- Configuration: Add `birthday_required` and `birthday_min_age` settings to provide a way to require users to enter their birth date.
|
||
- PleromaAPI: Add `GET /api/v1/pleroma/birthdays` API endpoint
|
||
- Make backend-rendered pages translatable. This includes emails. Pages returned as a HTTP response are translated using the language specified in the `userLanguage` cookie, or the `Accept-Language` header. Emails are translated using the `language` field when registering. This language can be changed by `PATCH /api/v1/accounts/update_credentials` with the `language` field.
|
||
- Uploadfilter `Pleroma.Upload.Filter.Exiftool.ReadDescription` returns description values to the FE so they can pre fill the image description field
|
||
- Added move account API
|
||
- Enable remote users to interact with posts
|
||
- Possibility to discover users like `user@example.org`, while Pleroma is working on `pleroma.example.org`. Additional configuration required.
|
||
|
||
### Fixed
|
||
- Subscription(Bell) Notifications: Don't create from Pipeline Ingested replies
|
||
- Handle Reject for already-accepted Follows properly
|
||
- Display OpenGraph data on alternative notice routes.
|
||
- Fix replies count for remote replies
|
||
- Fixed hashtags disappearing from the end of lines when Markdown is enabled
|
||
- ChatAPI: Add link headers
|
||
- Limited number of search results to 40 to prevent DoS attacks
|
||
- ActivityPub: fixed federation of attachment dimensions
|
||
- Fixed benchmarks
|
||
- Elixir 1.13 support
|
||
- Fixed crash when pinned_objects is nil
|
||
- Fixed slow timelines when there are a lot of deactivated users
|
||
- Fixed account deletion API
|
||
- Fixed lowercase HTTP HEAD method in the Media Proxy Preview code
|
||
- Removed useless notification call on Delete activities
|
||
- Improved performance for filtering out deactivated and invisible users
|
||
- TwitterCard meta tags conformance
|
||
|
||
### Removed
|
||
- Quack, the logging backend that pushes to Slack channels
|
||
|
||
## 2.4.5 - 2022-08-27
|
||
|
||
## Fixed
|
||
- Image `class` attributes not being scrubbed, allowing to exploit frontend special classes [!3792](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3792)
|
||
- Delete report notifs when demoting from superuser [!3642](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3642)
|
||
- Validate `mediaType` only by it's format rather than using a list [!3597](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3597)
|
||
- Pagination: Make mutes and blocks lists behave the same as other lists [!3693](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3693)
|
||
- Compatibility with Elixir 1.14 [!3740](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3740)
|
||
- Frontend installer: FediFE build URL [!3736](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3736)
|
||
- Streaming: Don't stream ChatMessage into the home timeline [!3738](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3738)
|
||
- Streaming: Stream local-only posts in the local timeline [!3738](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3738)
|
||
- Signatures: Fix `keyId` lookup for GoToSocial [!3725](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3725)
|
||
- Validator: Fix `replies` handling for GoToSocial [!3725](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3725)
|
||
|
||
## 2.4.4 - 2022-08-19
|
||
|
||
### Security
|
||
- Streaming API sessions will now properly disconnect if the corresponding token is revoked
|
||
|
||
## 2.4.3 - 2022-05-06
|
||
|
||
### Security
|
||
- Private `/objects/` and `/activities/` leaking if cached by authenticated user
|
||
- SweetXML library DTD bomb
|
||
|
||
## 2.4.2 - 2022-01-10
|
||
|
||
### Fixed
|
||
- Federation issues caused by HTTP pool checkout timeouts
|
||
- Compatibility with Elixir 1.13
|
||
|
||
### Upgrade notes
|
||
|
||
1. Restart Pleroma
|
||
|
||
## 2.4.1 - 2021-08-29
|
||
|
||
### Changed
|
||
- Make `mix pleroma.database set_text_search_config` run concurrently and indefinitely
|
||
|
||
### Added
|
||
- AdminAPI: Missing configuration description for StealEmojiPolicy
|
||
|
||
### Fixed
|
||
- MastodonAPI: Stream out Create activities
|
||
- MRF ObjectAgePolicy: Fix pattern matching on "published"
|
||
- TwitterAPI: Make `change_password` and `change_email` require params on body instead of query
|
||
- Subscription(Bell) Notifications: Don't create from Pipeline Ingested replies
|
||
- AdminAPI: Fix rendering reports containing a `nil` object
|
||
- Mastodon API: Activity Search fallbacks on status fetching after a DB Timeout/Error
|
||
- Mastodon API: Fix crash in Streamer related to reblogging
|
||
- AdminAPI: List available frontends when `static/frontends` folder is missing
|
||
- Make activity search properly use language-aware GIN indexes
|
||
- AdminAPI: Fix suggestions for MRF Policies
|
||
|
||
## 2.4.0 - 2021-08-08
|
||
|
||
### Changed
|
||
|
||
- **Breaking:** Configuration: `:chat, enabled` moved to `:shout, enabled` and `:instance, chat_limit` moved to `:shout, limit`
|
||
- **Breaking** Entries for simple_policy, transparency_exclusions and quarantined_instances now list both the instance and a reason.
|
||
- Support for Erlang/OTP 24
|
||
- The `application` metadata returned with statuses is no longer hardcoded. Apps that want to display these details will now have valid data for new posts after this change.
|
||
- HTTPSecurityPlug now sends a response header to opt out of Google's FLoC (Federated Learning of Cohorts) targeted advertising.
|
||
- Email address is now returned if requesting user is the owner of the user account so it can be exposed in client and FE user settings UIs.
|
||
- Improved Twittercard and OpenGraph meta tag generation including thumbnails and image dimension metadata when available.
|
||
- AdminAPI: sort users so the newest are at the top.
|
||
- ActivityPub Client-to-Server(C2S): Limitation on the type of Activity/Object are lifted as they are now passed through ObjectValidators
|
||
- MRF (`AntiFollowbotPolicy`): Bot accounts are now also considered followbots. Users can still allow bots to follow them by first following the bot.
|
||
|
||
### Added
|
||
|
||
- MRF (`FollowBotPolicy`): New MRF Policy which makes a designated local Bot account attempt to follow all users in public Notes received by your instance. Users who require approving follower requests or have #nobot in their profile are excluded.
|
||
- Return OAuth token `id` (primary key) in POST `/oauth/token`.
|
||
- AdminAPI: return `created_at` date with users.
|
||
- AdminAPI: add DELETE `/api/v1/pleroma/admin/instances/:instance` to delete all content from a remote instance.
|
||
- `AnalyzeMetadata` upload filter for extracting image/video attachment dimensions and generating blurhashes for images. Blurhashes for videos are not generated at this time.
|
||
- Attachment dimensions and blurhashes are federated when available.
|
||
- Mastodon API: support `poll` notification.
|
||
- Pinned posts federation
|
||
|
||
### Fixed
|
||
- Don't crash so hard when email settings are invalid.
|
||
- Checking activated Upload Filters for required commands.
|
||
- Remote users can no longer reappear after being deleted.
|
||
- Deactivated users may now be deleted.
|
||
- Deleting an activity with a lot of likes/boosts no longer causes a database timeout.
|
||
- Mix task `pleroma.database prune_objects`
|
||
- Fixed rendering of JSON errors on ActivityPub endpoints.
|
||
- Linkify: Parsing crash with URLs ending in unbalanced closed paren, no path separator, and no query parameters
|
||
- Try to save exported ConfigDB settings (migrate_from_db) in the system temp directory if default location is not writable.
|
||
- Uploading custom instance thumbnail via AdminAPI/AdminFE generated invalid URL to the image
|
||
- Applying ConcurrentLimiter settings via AdminAPI
|
||
- User login failures if their `notification_settings` were in a NULL state.
|
||
- Mix task `pleroma.user delete_activities` query transaction timeout is now :infinity
|
||
- MRF (`SimplePolicy`): Embedded objects are now checked. If any embedded object would be rejected, its parent is rejected. This fixes Announces leaking posts from blocked domains.
|
||
- Fixed some Markdown issues, including trailing slash in links.
|
||
|
||
### Removed
|
||
- **Breaking**: Remove deprecated `/api/qvitter/statuses/notifications/read` (replaced by `/api/v1/pleroma/notifications/read`)
|
||
|
||
## [2.3.0] - 2021-03-01
|
||
|
||
### Security
|
||
|
||
- Fixed client user agent leaking through MediaProxy
|
||
|
||
### Removed
|
||
|
||
- `:auth, :enforce_oauth_admin_scope_usage` configuration option.
|
||
|
||
### Changed
|
||
|
||
- **Breaking**: Changed `mix pleroma.user toggle_confirmed` to `mix pleroma.user confirm`
|
||
- **Breaking**: Changed `mix pleroma.user toggle_activated` to `mix pleroma.user activate/deactivate`
|
||
- **Breaking:** NSFW hashtag is no longer added on sensitive posts
|
||
- Polls now always return a `voters_count`, even if they are single-choice.
|
||
- Admin Emails: The ap id is used as the user link in emails now.
|
||
- Improved registration workflow for email confirmation and account approval modes.
|
||
- Search: When using Postgres 11+, Pleroma will use the `websearch_to_tsvector` function to parse search queries.
|
||
- Emoji: Support the full Unicode 13.1 set of Emoji for reactions, plus regional indicators.
|
||
- Deprecated `Pleroma.Uploaders.S3, :public_endpoint`. Now `Pleroma.Upload, :base_url` is the standard configuration key for all uploaders.
|
||
- Improved Apache webserver support: updated sample configuration, MediaProxy cache invalidation verified with the included sample script
|
||
- Improve OAuth 2.0 provider support. A missing `fqn` field was added to the response, but does not expose the user's email address.
|
||
- Provide redirect of external posts from `/notice/:id` to their original URL
|
||
- Admins no longer receive notifications for reports if they are the actor making the report.
|
||
- Improved Mailer configuration setting descriptions for AdminFE.
|
||
- Updated default avatar to look nicer.
|
||
|
||
<details>
|
||
<summary>API Changes</summary>
|
||
|
||
- **Breaking:** AdminAPI changed User field `confirmation_pending` to `is_confirmed`
|
||
- **Breaking:** AdminAPI changed User field `approval_pending` to `is_approved`
|
||
- **Breaking**: AdminAPI changed User field `deactivated` to `is_active`
|
||
- **Breaking:** AdminAPI `GET /api/pleroma/admin/users/:nickname_or_id/statuses` changed response format and added the number of total users posts.
|
||
- **Breaking:** AdminAPI `GET /api/pleroma/admin/instances/:instance/statuses` changed response format and added the number of total users posts.
|
||
- Admin API: Reports now ordered by newest
|
||
- Pleroma API: `GET /api/v1/pleroma/chats` is deprecated in favor of `GET /api/v2/pleroma/chats`.
|
||
- Pleroma API: Reroute `/api/pleroma/*` to `/api/v1/pleroma/*`
|
||
|
||
</details>
|
||
- Improved hashtag timeline performance (requires a background migration).
|
||
|
||
### Added
|
||
|
||
- Reports now generate notifications for admins and mods.
|
||
- Support for local-only statuses.
|
||
- Support pagination of blocks and mutes.
|
||
- Account backup.
|
||
- Configuration: Add `:instance, autofollowing_nicknames` setting to provide a way to make accounts automatically follow new users that register on the local Pleroma instance.
|
||
- `[:activitypub, :blockers_visible]` config to control visibility of blockers.
|
||
- Ability to view remote timelines, with ex. `/api/v1/timelines/public?instance=lain.com` and streams `public:remote` and `public:remote:media`.
|
||
- The site title is now injected as a `title` tag like preloads or metadata.
|
||
- Password reset tokens now are not accepted after a certain age.
|
||
- Mix tasks to help with displaying and removing ConfigDB entries. See `mix pleroma.config`.
|
||
- OAuth form improvements: users are remembered by their cookie, the CSS is overridable by the admin, and the style has been improved.
|
||
- OAuth improvements and fixes: more secure session-based authentication (by token that could be revoked anytime), ability to revoke belonging OAuth token from any client etc.
|
||
- Ability to set ActivityPub aliases for follower migration.
|
||
- Configurable background job limits for RichMedia (link previews) and MediaProxyWarmingPolicy
|
||
- Ability to define custom HTTP headers per each frontend
|
||
- MRF (`NoEmptyPolicy`): New MRF Policy which will deny empty statuses or statuses of only mentions from being created by local users
|
||
- New users will receive a simple email confirming their registration if no other emails will be dispatched. (e.g., Welcome, Confirmation, or Approval Required)
|
||
|
||
<details>
|
||
<summary>API Changes</summary>
|
||
- Admin API: (`GET /api/pleroma/admin/users`) filter users by `unconfirmed` status and `actor_type`.
|
||
- Admin API: OpenAPI spec for the user-related operations
|
||
- Pleroma API: `GET /api/v2/pleroma/chats` added. It is exactly like `GET /api/v1/pleroma/chats` except supports pagination.
|
||
- Pleroma API: Add `idempotency_key` to the chat message entity that can be used for optimistic message sending.
|
||
- Pleroma API: (`GET /api/v1/pleroma/federation_status`) Add a way to get a list of unreachable instances.
|
||
- Mastodon API: User and conversation mutes can now auto-expire if `expires_in` parameter was given while adding the mute.
|
||
- Admin API: An endpoint to manage frontends.
|
||
- Streaming API: Add follow relationships updates.
|
||
- WebPush: Introduce `pleroma:chat_mention` and `pleroma:emoji_reaction` notification types.
|
||
- Mastodon API: Add monthly active users to `/api/v1/instance` (`pleroma.stats.mau`).
|
||
- Mastodon API: Home, public, hashtag & list timelines accept `only_media`, `remote` & `local` parameters for filtration.
|
||
- Mastodon API: `/api/v1/accounts/:id` & `/api/v1/mutes` endpoints accept `with_relationships` parameter and return filled `pleroma.relationship` field.
|
||
- Mastodon API: Endpoint to remove a conversation (`DELETE /api/v1/conversations/:id`).
|
||
- Mastodon API: `expires_in` in the scheduled post `params` field on `/api/v1/statuses` and `/api/v1/scheduled_statuses/:id` endpoints.
|
||
</details>
|
||
|
||
### Fixed
|
||
|
||
- Users with `is_discoverable` field set to false (default value) will appear in in-service search results but be hidden from external services (search bots etc.).
|
||
- Streaming API: Posts and notifications are not dropped, when CLI task is executing.
|
||
- Creating incorrect IPv4 address-style HTTP links when encountering certain numbers.
|
||
- Reblog API Endpoint: Do not set visibility parameter to public by default and let CommonAPI to infer it from status, so a user can reblog their private status without explicitly setting reblog visibility to private.
|
||
- Tag URLs in statuses are now absolute
|
||
- Removed duplicate jobs to purge expired activities
|
||
- File extensions of some attachments were incorrectly changed. This feature has been disabled for now.
|
||
- Mix task pleroma.instance creates missing parent directories if the configuration or SQL output paths are changed.
|
||
|
||
<details>
|
||
<summary>API Changes</summary>
|
||
- Mastodon API: Current user is now included in conversation if it's the only participant.
|
||
- Mastodon API: Fixed last_status.account being not filled with account data.
|
||
- Mastodon API: Fix not being able to add or remove multiple users at once in lists.
|
||
- Mastodon API: Fixed own_votes being not returned with poll data.
|
||
- Mastodon API: Fixed creation of scheduled posts with polls.
|
||
- Mastodon API: Support for expires_in/expires_at in the Filters.
|
||
</details>
|
||
|
||
## [2.2.2] - 2021-01-18
|
||
|
||
### Fixed
|
||
|
||
- StealEmojiPolicy creates dir for emojis, if it doesn't exist.
|
||
- Updated `elixir_make` to a non-retired version
|
||
|
||
### Upgrade notes
|
||
|
||
1. Restart Pleroma
|
||
|
||
## [2.2.1] - 2020-12-22
|
||
|
||
### Changed
|
||
- Updated Pleroma FE
|
||
|
||
### Fixed
|
||
|
||
- Config generation: rename `Pleroma.Upload.Filter.ExifTool` to `Pleroma.Upload.Filter.Exiftool`.
|
||
- S3 Uploads with Elixir 1.11.
|
||
- Mix task pleroma.user delete_activities for source installations.
|
||
- Search: RUM index search speed has been fixed.
|
||
- Rich Media Previews sometimes showed the wrong preview due to a bug following redirects.
|
||
- Fixes for the autolinker.
|
||
- Forwarded reports duplication from Pleroma instances.
|
||
- Emoji Reaction activity filtering from blocked and muted accounts.
|
||
|
||
- <details>
|
||
<summary>API</summary>
|
||
- Statuses were not displayed for Mastodon forwarded reports.
|
||
</details>
|
||
|
||
### Upgrade notes
|
||
|
||
1. Restart Pleroma
|
||
|
||
## [2.2.0] - 2020-11-12
|
||
|
||
### Security
|
||
|
||
- Fixed the possibility of using file uploads to spoof posts.
|
||
|
||
### Changed
|
||
|
||
- **Breaking** Requires `libmagic` (or `file`) to guess file types.
|
||
- **Breaking:** App metrics endpoint (`/api/pleroma/app_metrics`) is disabled by default, check `docs/API/prometheus.md` on enabling and configuring.
|
||
- **Breaking:** Pleroma Admin API: emoji packs and files routes changed.
|
||
- **Breaking:** Sensitive/NSFW statuses no longer disable link previews.
|
||
- Search: Users are now findable by their urls.
|
||
- Renamed `:await_up_timeout` in `:connections_pool` namespace to `:connect_timeout`, old name is deprecated.
|
||
- Renamed `:timeout` in `pools` namespace to `:recv_timeout`, old name is deprecated.
|
||
- The `discoverable` field in the `User` struct will now add a NOINDEX metatag to profile pages when false.
|
||
- Users with the `is_discoverable` field set to false will not show up in searches ([bug](https://git.pleroma.social/pleroma/pleroma/-/issues/2301)).
|
||
- Minimum lifetime for ephmeral activities changed to 10 minutes and made configurable (`:min_lifetime` option).
|
||
- Introduced optional dependencies on `ffmpeg`, `ImageMagick`, `exiftool` software packages. Please refer to `docs/installation/optional/media_graphics_packages.md`.
|
||
- <details>
|
||
<summary>API Changes</summary>
|
||
- API: Empty parameter values for integer parameters are now ignored in non-strict validaton mode.
|
||
</details>
|
||
|
||
### Removed
|
||
|
||
- **Breaking:** `Pleroma.Workers.Cron.StatsWorker` setting from Oban `:crontab` (moved to a simpler implementation).
|
||
- **Breaking:** `Pleroma.Workers.Cron.ClearOauthTokenWorker` setting from Oban `:crontab` (moved to scheduled jobs).
|
||
- **Breaking:** `Pleroma.Workers.Cron.PurgeExpiredActivitiesWorker` setting from Oban `:crontab` (moved to scheduled jobs).
|
||
- Removed `:managed_config` option. In practice, it was accidentally removed with 2.0.0 release when frontends were
|
||
switched to a new configuration mechanism, however it was not officially removed until now.
|
||
|
||
### Added
|
||
|
||
- Media preview proxy (requires `ffmpeg` and `ImageMagick` to be installed and media proxy to be enabled; see `:media_preview_proxy` config for more details).
|
||
- Mix tasks for controlling user account confirmation status in bulk (`mix pleroma.user confirm_all` and `mix pleroma.user unconfirm_all`)
|
||
- Mix task for sending confirmation emails to all unconfirmed users (`mix pleroma.email resend_confirmation_emails`)
|
||
- Mix task option for force-unfollowing relays
|
||
- App metrics: ability to restrict access to specified IP whitelist.
|
||
|
||
<details>
|
||
<summary>API Changes</summary>
|
||
|
||
- Admin API: Importing emoji from a zip file
|
||
- Pleroma API: Importing the mutes users from CSV files.
|
||
- Pleroma API: Pagination for remote/local packs and emoji.
|
||
|
||
</details>
|
||
|
||
### Fixed
|
||
|
||
- Add documented-but-missing chat pagination.
|
||
- Allow sending out emails again.
|
||
- Allow sending chat messages to yourself
|
||
- OStatus / static FE endpoints: fixed inaccessibility for anonymous users on non-federating instances, switched to handling per `:restrict_unauthenticated` setting.
|
||
- Fix remote users with a whitespace name.
|
||
|
||
### Upgrade notes
|
||
|
||
1. Install libmagic and development headers (`libmagic-dev` on Ubuntu/Debian, `file-dev` on Alpine Linux)
|
||
2. Run database migrations (inside Pleroma directory):
|
||
- OTP: `./bin/pleroma_ctl migrate`
|
||
- From Source: `mix ecto.migrate`
|
||
3. Restart Pleroma
|
||
|
||
## [2.1.2] - 2020-09-17
|
||
|
||
### Security
|
||
|
||
- Fix most MRF rules either crashing or not being applied to objects passed into the Common Pipeline (ChatMessage, Question, Answer, Audio, Event).
|
||
|
||
### Fixed
|
||
|
||
- Welcome Chat messages preventing user registration with MRF Simple Policy applied to the local instance.
|
||
- Mastodon API: the public timeline returning an error when the `reply_visibility` parameter is set to `self` for an unauthenticated user.
|
||
- Mastodon Streaming API: Handler crashes on authentication failures, resulting in error logs.
|
||
- Mastodon Streaming API: Error logs on client pings.
|
||
- Rich media: Log spam on failures. Now the error is only logged once per attempt.
|
||
|
||
### Changed
|
||
|
||
- Rich Media: A HEAD request is now done to the url, to ensure it has the appropriate content type and size before proceeding with a GET.
|
||
|
||
### Upgrade notes
|
||
|
||
1. Restart Pleroma
|
||
|
||
## [2.1.1] - 2020-09-08
|
||
|
||
### Security
|
||
- Fix possible DoS in Mastodon API user search due to an error in match clauses, leading to an infinite recursion and subsequent OOM with certain inputs.
|
||
- Fix metadata leak for accounts and statuses on private instances.
|
||
- Fix possible DoS in Admin API search using an atom leak vulnerability. Authentication with admin rights was required to exploit.
|
||
|
||
### Changed
|
||
|
||
- **Breaking:** The metadata providers RelMe and Feed are no longer configurable. RelMe should always be activated and Feed only provides a <link> header tag for the actual RSS/Atom feed when the instance is public.
|
||
- Improved error message when cmake is not available at build stage.
|
||
|
||
### Added
|
||
- Rich media failure tracking (along with `:failure_backoff` option).
|
||
|
||
<details>
|
||
<summary>Admin API Changes</summary>
|
||
|
||
- Add `PATCH /api/pleroma/admin/instance_document/:document_name` to modify the Terms of Service and Instance Panel HTML pages via Admin API
|
||
</details>
|
||
|
||
### Fixed
|
||
- Default HTTP adapter not respecting pool setting, leading to possible OOM.
|
||
- Fixed uploading webp images when the Exiftool Upload Filter is enabled by skipping them
|
||
- Mastodon API: Search parameter `following` now correctly returns the followings rather than the followers
|
||
- Mastodon API: Timelines hanging for (`number of posts with links * rich media timeout`) in the worst case.
|
||
Reduced to just rich media timeout.
|
||
- Mastodon API: Cards being wrong for preview statuses due to cache key collision.
|
||
- Password resets no longer processed for deactivated accounts.
|
||
- Favicon scraper raising exceptions on URLs longer than 255 characters.
|
||
|
||
## [2.1.0] - 2020-08-28
|
||
|
||
### Changed
|
||
|
||
- **Breaking:** The default descriptions on uploads are now empty. The old behavior (filename as default) can be configured, see the cheat sheet.
|
||
- **Breaking:** Added the ObjectAgePolicy to the default set of MRFs. This will delist and strip the follower collection of any message received that is older than 7 days. This will stop users from seeing very old messages in the timelines. The messages can still be viewed on the user's page and in conversations. They also still trigger notifications.
|
||
- **Breaking:** Elixir >=1.9 is now required (was >= 1.8)
|
||
- **Breaking:** Configuration: `:auto_linker, :opts` moved to `:pleroma, Pleroma.Formatter`. Old config namespace is deprecated.
|
||
- **Breaking:** Configuration: `:instance, welcome_user_nickname` moved to `:welcome, :direct_message, :sender_nickname`, `:instance, :welcome_message` moved to `:welcome, :direct_message, :message`. Old config namespace is deprecated.
|
||
- **Breaking:** LDAP: Fallback to local database authentication has been removed for security reasons and lack of a mechanism to ensure the passwords are synchronized when LDAP passwords are updated.
|
||
- **Breaking** Changed defaults for `:restrict_unauthenticated` so that when `:instance, :public` is set to `false` then all `:restrict_unauthenticated` items be effectively set to `true`. If you'd like to allow unauthenticated access to specific API endpoints on a private instance, please explicitly set `:restrict_unauthenticated` to non-default value in `config/prod.secret.exs`.
|
||
- In Conversations, return only direct messages as `last_status`
|
||
- Using the `only_media` filter on timelines will now exclude reblog media
|
||
- MFR policy to set global expiration for all local Create activities
|
||
- OGP rich media parser merged with TwitterCard
|
||
- Configuration: `:instance, rewrite_policy` moved to `:mrf, policies`, `:instance, :mrf_transparency` moved to `:mrf, :transparency`, `:instance, :mrf_transparency_exclusions` moved to `:mrf, :transparency_exclusions`. Old config namespace is deprecated.
|
||
- Configuration: `:media_proxy, whitelist` format changed to host with scheme (e.g. `http://example.com` instead of `example.com`). Domain format is deprecated.
|
||
|
||
<details>
|
||
<summary>API Changes</summary>
|
||
|
||
- **Breaking:** Pleroma API: The routes to update avatar, banner and background have been removed.
|
||
- **Breaking:** Image description length is limited now.
|
||
- **Breaking:** Emoji API: changed methods and renamed routes.
|
||
- **Breaking:** Notification Settings API for suppressing notifications has been simplified down to `block_from_strangers`.
|
||
- **Breaking:** Notification Settings API option for hiding push notification contents has been renamed to `hide_notification_contents`.
|
||
- MastodonAPI: Allow removal of avatar, banner and background.
|
||
- Streaming: Repeats of a user's posts will no longer be pushed to the user's stream.
|
||
- Mastodon API: Added `pleroma.metadata.fields_limits` to /api/v1/instance
|
||
- Mastodon API: On deletion, returns the original post text.
|
||
- Mastodon API: Add `pleroma.unread_count` to the Marker entity.
|
||
- Mastodon API: Added `pleroma.metadata.post_formats` to /api/v1/instance
|
||
- Mastodon API (legacy): Allow query parameters for `/api/v1/domain_blocks`, e.g. `/api/v1/domain_blocks?domain=badposters.zone`
|
||
- Mastodon API: Make notifications about statuses from muted users and threads read automatically
|
||
- Pleroma API: `/api/pleroma/captcha` responses now include `seconds_valid` with an integer value.
|
||
|
||
</details>
|
||
|
||
<details>
|
||
<summary>Admin API Changes</summary>
|
||
|
||
- **Breaking** Changed relay `/api/pleroma/admin/relay` endpoints response format.
|
||
- Status visibility stats: now can return stats per instance.
|
||
- Mix task to refresh counter cache (`mix pleroma.refresh_counter_cache`)
|
||
|
||
</details>
|
||
|
||
### Removed
|
||
|
||
- **Breaking:** removed `with_move` parameter from notifications timeline.
|
||
|
||
### Added
|
||
|
||
- Frontends: Add mix task to install frontends.
|
||
- Frontends: Add configurable frontends for primary and admin fe.
|
||
- Configuration: Added a blacklist for email servers.
|
||
- Chats: Added `accepts_chat_messages` field to user, exposed in APIs and federation.
|
||
- Chats: Added support for federated chats. For details, see the docs.
|
||
- ActivityPub: Added support for existing AP ids for instances migrated from Mastodon.
|
||
- Instance: Add `background_image` to configuration and `/api/v1/instance`
|
||
- Instance: Extend `/api/v1/instance` with Pleroma-specific information.
|
||
- NodeInfo: `pleroma:api/v1/notifications:include_types_filter` to the `features` list.
|
||
- NodeInfo: `pleroma_emoji_reactions` to the `features` list.
|
||
- Configuration: `:restrict_unauthenticated` setting, restrict access for unauthenticated users to timelines (public and federate), user profiles and statuses.
|
||
- Configuration: Add `:database_config_whitelist` setting to whitelist settings which can be configured from AdminFE.
|
||
- Configuration: `filename_display_max_length` option to set filename truncate limit, if filename display enabled (0 = no limit).
|
||
- New HTTP adapter [gun](https://github.com/ninenines/gun). Gun adapter requires minimum OTP version of 22.2 otherwise Pleroma won’t start. For hackney OTP update is not required.
|
||
- Mix task to create trusted OAuth App.
|
||
- Mix task to reset MFA for user accounts
|
||
- Notifications: Added `follow_request` notification type.
|
||
- Added `:reject_deletes` group to SimplePolicy
|
||
- MRF (`EmojiStealPolicy`): New MRF Policy which allows to automatically download emojis from remote instances
|
||
- Support pagination in emoji packs API (for packs and for files in pack)
|
||
- Support for viewing instances favicons next to posts and accounts
|
||
- Added Pleroma.Upload.Filter.Exiftool as an alternate EXIF stripping mechanism targeting GPS/location metadata.
|
||
- "By approval" registrations mode.
|
||
- Configuration: Added `:welcome` settings for the welcome message to newly registered users. You can send a welcome message as a direct message, chat or email.
|
||
- Ability to hide favourites and emoji reactions in the API with `[:instance, :show_reactions]` config.
|
||
|
||
<details>
|
||
<summary>API Changes</summary>
|
||
|
||
- Mastodon API: Add pleroma.parent_visible field to statuses.
|
||
- Mastodon API: Extended `/api/v1/instance`.
|
||
- Mastodon API: Support for `include_types` in `/api/v1/notifications`.
|
||
- Mastodon API: Added `/api/v1/notifications/:id/dismiss` endpoint.
|
||
- Mastodon API: Add support for filtering replies in public and home timelines.
|
||
- Mastodon API: Support for `bot` field in `/api/v1/accounts/update_credentials`.
|
||
- Mastodon API: Support irreversible property for filters.
|
||
- Mastodon API: Add pleroma.favicon field to accounts.
|
||
- Admin API: endpoints for create/update/delete OAuth Apps.
|
||
- Admin API: endpoint for status view.
|
||
- OTP: Add command to reload emoji packs
|
||
</details>
|
||
|
||
### Fixed
|
||
- Fix list pagination and other list issues.
|
||
- Support pagination in conversations API
|
||
- **Breaking**: SimplePolicy `:reject` and `:accept` allow deletions again
|
||
- Fix follower/blocks import when nicknames starts with @
|
||
- Filtering of push notifications on activities from blocked domains
|
||
- Resolving Peertube accounts with Webfinger
|
||
- `blob:` urls not being allowed by connect-src CSP
|
||
- Mastodon API: fix `GET /api/v1/notifications` not returning the full result set
|
||
- Rich Media Previews for Twitter links
|
||
- Admin API: fix `GET /api/pleroma/admin/users/:nickname/credentials` returning 404 when getting the credentials of a remote user while `:instance, :limit_to_local_content` is set to `:unauthenticated`
|
||
- Fix CSP policy generation to include remote Captcha services
|
||
- Fix edge case where MediaProxy truncates media, usually caused when Caddy is serving content for the other Federated instance.
|
||
- Emoji Packs could not be listed when instance was set to `public: false`
|
||
- Fix whole_word always returning false on filter get requests
|
||
- Migrations not working on OTP releases if the database was connected over ssl
|
||
- Fix relay following
|
||
|
||
## [2.0.7] - 2020-06-13
|
||
|
||
### Security
|
||
- Fix potential DoSes exploiting atom leaks in rich media parser and the `UserAllowListPolicy` MRF policy
|
||
|
||
### Fixed
|
||
- CSP: not allowing images/media from every host when mediaproxy is disabled
|
||
- CSP: not adding mediaproxy base url to image/media hosts
|
||
- StaticFE missing the CSS file
|
||
|
||
### Upgrade notes
|
||
|
||
1. Restart Pleroma
|
||
|
||
## [2.0.6] - 2020-06-09
|
||
|
||
### Security
|
||
- CSP: harden `image-src` and `media-src` when MediaProxy is used
|
||
|
||
### Fixed
|
||
- AP C2S: Fix pagination in inbox/outbox
|
||
- Various compilation errors on OTP 23
|
||
- Mastodon API streaming: Repeats from muted threads not being filtered
|
||
|
||
### Changed
|
||
- Various database performance improvements
|
||
|
||
### Upgrade notes
|
||
1. Run database migrations (inside Pleroma directory):
|
||
- OTP: `./bin/pleroma_ctl migrate`
|
||
- From Source: `mix ecto.migrate`
|
||
2. Restart Pleroma
|
||
|
||
## [2.0.5] - 2020-05-13
|
||
|
||
### Security
|
||
- Fix possible private status leaks in Mastodon Streaming API
|
||
|
||
### Fixed
|
||
- Crashes when trying to block a user if block federation is disabled
|
||
- Not being able to start the instance without `erlang-eldap` installed
|
||
- Users with bios over the limit getting rejected
|
||
- Follower counters not being updated on incoming follow accepts
|
||
|
||
### Upgrade notes
|
||
|
||
1. Restart Pleroma
|
||
|
||
## [2.0.4] - 2020-05-10
|
||
|
||
### Security
|
||
- AP C2S: Fix a potential DoS by creating nonsensical objects that break timelines
|
||
|
||
### Fixed
|
||
- Peertube user lookups not working
|
||
- `InsertSkeletonsForDeletedUsers` migration failing on some instances
|
||
- Healthcheck reporting the number of memory currently used, rather than allocated in total
|
||
- LDAP not being usable in OTP releases
|
||
- Default apache configuration having tls chain issues
|
||
|
||
### Upgrade notes
|
||
|
||
#### Apache only
|
||
|
||
1. Remove the following line from your config:
|
||
```
|
||
SSLCertificateFile /etc/letsencrypt/live/${servername}/cert.pem
|
||
```
|
||
|
||
#### Everyone
|
||
|
||
1. Restart Pleroma
|
||
|
||
## [2.0.3] - 2020-05-02
|
||
|
||
### Security
|
||
- Disallow re-registration of previously deleted users, which allowed viewing direct messages addressed to them
|
||
- Mastodon API: Fix `POST /api/v1/follow_requests/:id/authorize` allowing to force a follow from a local user even if they didn't request to follow
|
||
- CSP: Sandbox uploads
|
||
|
||
### Fixed
|
||
- Notifications from blocked domains
|
||
- Potential federation issues with Mastodon versions before 3.0.0
|
||
- HTTP Basic Authentication permissions issue
|
||
- Follow/Block imports not being able to find the user if the nickname started with an `@`
|
||
- Instance stats counting internal users
|
||
- Inability to run a From Source release without git
|
||
- ObjectAgePolicy didn't filter out old messages
|
||
- `blob:` urls not being allowed by CSP
|
||
|
||
### Added
|
||
- NodeInfo: ObjectAgePolicy settings to the `federation` list.
|
||
- Follow request notifications
|
||
<details>
|
||
<summary>API Changes</summary>
|
||
- Admin API: `GET /api/pleroma/admin/need_reboot`.
|
||
</details>
|
||
|
||
### Upgrade notes
|
||
|
||
1. Restart Pleroma
|
||
2. Run database migrations (inside Pleroma directory):
|
||
- OTP: `./bin/pleroma_ctl migrate`
|
||
- From Source: `mix ecto.migrate`
|
||
3. Reset status visibility counters (inside Pleroma directory):
|
||
- OTP: `./bin/pleroma_ctl refresh_counter_cache`
|
||
- From Source: `mix pleroma.refresh_counter_cache`
|
||
|
||
|
||
## [2.0.2] - 2020-04-08
|
||
### Added
|
||
- Support for Funkwhale's `Audio` activity
|
||
- Admin API: `PATCH /api/pleroma/admin/users/:nickname/update_credentials`
|
||
|
||
### Fixed
|
||
- Blocked/muted users still generating push notifications
|
||
- Input textbox for bio ignoring newlines
|
||
- OTP: Inability to use PostgreSQL databases with SSL
|
||
- `user delete_activities` breaking when trying to delete already deleted posts
|
||
- Incorrect URL for Funkwhale channels
|
||
|
||
### Upgrade notes
|
||
1. Restart Pleroma
|
||
|
||
## [2.0.1] - 2020-03-15
|
||
### Security
|
||
- Static-FE: Fix remote posts not being sanitized
|
||
|
||
### Fixed
|
||
- Rate limiter crashes when there is no explicitly specified ip in the config
|
||
- 500 errors when no `Accept` header is present if Static-FE is enabled
|
||
- Instance panel not being updated immediately due to wrong `Cache-Control` headers
|
||
- Statuses posted with BBCode/Markdown having unncessary newlines in Pleroma-FE
|
||
- OTP: Fix some settings not being migrated to in-database config properly
|
||
- No `Cache-Control` headers on attachment/media proxy requests
|
||
- Character limit enforcement being off by 1
|
||
- Mastodon Streaming API: hashtag timelines not working
|
||
|
||
### Changed
|
||
- BBCode and Markdown formatters will no longer return any `\n` and only use `<br/>` for newlines
|
||
- Mastodon API: Allow registration without email if email verification is not enabled
|
||
|
||
### Upgrade notes
|
||
#### Nginx only
|
||
1. Remove `proxy_ignore_headers Cache-Control;` and `proxy_hide_header Cache-Control;` from your config.
|
||
|
||
#### Everyone
|
||
1. Run database migrations (inside Pleroma directory):
|
||
- OTP: `./bin/pleroma_ctl migrate`
|
||
- From Source: `mix ecto.migrate`
|
||
2. Restart Pleroma
|
||
|
||
## [2.0.0] - 2019-03-08
|
||
### Security
|
||
- Mastodon API: Fix being able to request enormous amount of statuses in timelines leading to DoS. Now limited to 40 per request.
|
||
|
||
### Removed
|
||
- **Breaking**: Removed 1.0+ deprecated configurations `Pleroma.Upload, :strip_exif` and `:instance, :dedupe_media`
|
||
- **Breaking**: OStatus protocol support
|
||
- **Breaking**: MDII uploader
|
||
- **Breaking**: Using third party engines for user recommendation
|
||
<details>
|
||
<summary>API Changes</summary>
|
||
|
||
- **Breaking**: AdminAPI: migrate_from_db endpoint
|
||
</details>
|
||
|
||
### Changed
|
||
- **Breaking:** Pleroma won't start if it detects unapplied migrations
|
||
- **Breaking:** Elixir >=1.8 is now required (was >= 1.7)
|
||
- **Breaking:** `Pleroma.Plugs.RemoteIp` and `:rate_limiter` enabled by default. Please ensure your reverse proxy forwards the real IP!
|
||
- **Breaking:** attachment links (`config :pleroma, :instance, no_attachment_links` and `config :pleroma, Pleroma.Upload, link_name`) disabled by default
|
||
- **Breaking:** OAuth: defaulted `[:auth, :enforce_oauth_admin_scope_usage]` setting to `true` which demands `admin` OAuth scope to perform admin actions (in addition to `is_admin` flag on User); make sure to use bundled or newer versions of AdminFE & PleromaFE to access admin / moderator features.
|
||
- **Breaking:** Dynamic configuration has been rearchitected. The `:pleroma, :instance, dynamic_configuration` setting has been replaced with `config :pleroma, configurable_from_database`. Please backup your configuration to a file and run the migration task to ensure consistency with the new schema.
|
||
- **Breaking:** `:instance, no_attachment_links` has been replaced with `:instance, attachment_links` which still takes a boolean value but doesn't use double negative language.
|
||
- Replaced [pleroma_job_queue](https://git.pleroma.social/pleroma/pleroma_job_queue) and `Pleroma.Web.Federator.RetryQueue` with [Oban](https://github.com/sorentwo/oban) (see [`docs/config.md`](docs/config.md) on migrating customized worker / retry settings)
|
||
- Introduced [quantum](https://github.com/quantum-elixir/quantum-core) job scheduler
|
||
- Enabled `:instance, extended_nickname_format` in the default config
|
||
- Add `rel="ugc"` to all links in statuses, to prevent SEO spam
|
||
- Extract RSS functionality from OStatus
|
||
- MRF (Simple Policy): Also use `:accept`/`:reject` on the actors rather than only their activities
|
||
- OStatus: Extract RSS functionality
|
||
- Deprecated `User.Info` embedded schema (fields moved to `User`)
|
||
- Store status data inside Flag activity
|
||
- Deprecated (reorganized as `UserRelationship` entity) User fields with user AP IDs (`blocks`, `mutes`, `muted_reblogs`, `muted_notifications`, `subscribers`).
|
||
- Rate limiter is now disabled for localhost/socket (unless remoteip plug is enabled)
|
||
- Logger: default log level changed from `warn` to `info`.
|
||
- Config mix task `migrate_to_db` truncates `config` table before migrating the config file.
|
||
- Allow account registration without an email
|
||
- Default to `prepare: :unnamed` in the database configuration.
|
||
- Instance stats are now loaded on startup instead of being empty until next hourly job.
|
||
<details>
|
||
<summary>API Changes</summary>
|
||
|
||
- **Breaking** EmojiReactions: Change endpoints and responses to align with Mastodon
|
||
- **Breaking** Admin API: `PATCH /api/pleroma/admin/users/:nickname/force_password_reset` is now `PATCH /api/pleroma/admin/users/force_password_reset` (accepts `nicknames` array in the request body)
|
||
- **Breaking:** Admin API: Return link alongside with token on password reset
|
||
- **Breaking:** Admin API: `PUT /api/pleroma/admin/reports/:id` is now `PATCH /api/pleroma/admin/reports`, see admin_api.md for details
|
||
- **Breaking:** `/api/pleroma/admin/users/invite_token` now uses `POST`, changed accepted params and returns full invite in json instead of only token string.
|
||
- **Breaking** replying to reports is now "report notes", endpoint changed from `POST /api/pleroma/admin/reports/:id/respond` to `POST /api/pleroma/admin/reports/:id/notes`
|
||
- Mastodon API: stopped sanitizing display names, field names and subject fields since they are supposed to be treated as plaintext
|
||
- Admin API: Return `total` when querying for reports
|
||
- Mastodon API: Return `pleroma.direct_conversation_id` when creating a direct message (`POST /api/v1/statuses`)
|
||
- Admin API: Return link alongside with token on password reset
|
||
- Admin API: Support authentication via `x-admin-token` HTTP header
|
||
- Mastodon API: Add `pleroma.direct_conversation_id` to the status endpoint (`GET /api/v1/statuses/:id`)
|
||
- Mastodon API: `pleroma.thread_muted` to the Status entity
|
||
- Mastodon API: Mark the direct conversation as read for the author when they send a new direct message
|
||
- Mastodon API, streaming: Add `pleroma.direct_conversation_id` to the `conversation` stream event payload.
|
||
- Admin API: Render whole status in grouped reports
|
||
- Mastodon API: User timelines will now respect blocks, unless you are getting the user timeline of somebody you blocked (which would be empty otherwise).
|
||
- Mastodon API: Favoriting / Repeating a post multiple times will now return the identical response every time. Before, executing that action twice would return an error ("already favorited") on the second try.
|
||
- Mastodon API: Limit timeline requests to 3 per timeline per 500ms per user/ip by default.
|
||
- Admin API: `PATCH /api/pleroma/admin/users/:nickname/credentials` and `GET /api/pleroma/admin/users/:nickname/credentials`
|
||
</details>
|
||
|
||
### Added
|
||
- `:chat_limit` option to limit chat characters.
|
||
- `cleanup_attachments` option to remove attachments along with statuses. Does not affect duplicate files and attachments without status. Enabling this will increase load to database when deleting statuses on larger instances.
|
||
- Refreshing poll results for remote polls
|
||
- Authentication: Added rate limit for password-authorized actions / login existence checks
|
||
- Static Frontend: Add the ability to render user profiles and notices server-side without requiring JS app.
|
||
- Mix task to re-count statuses for all users (`mix pleroma.count_statuses`)
|
||
- Mix task to list all users (`mix pleroma.user list`)
|
||
- Mix task to send a test email (`mix pleroma.email test`)
|
||
- Support for `X-Forwarded-For` and similar HTTP headers which used by reverse proxies to pass a real user IP address to the backend. Must not be enabled unless your instance is behind at least one reverse proxy (such as Nginx, Apache HTTPD or Varnish Cache).
|
||
- MRF: New module which handles incoming posts based on their age. By default, all incoming posts that are older than 2 days will be unlisted and not shown to their followers.
|
||
- User notification settings: Add `privacy_option` option.
|
||
- Support for custom Elixir modules (such as MRF policies)
|
||
- User settings: Add _This account is a_ option.
|
||
- A new users admin digest email
|
||
- OAuth: admin scopes support (relevant setting: `[:auth, :enforce_oauth_admin_scope_usage]`).
|
||
- Add an option `authorized_fetch_mode` to require HTTP signatures for AP fetches.
|
||
- ActivityPub: support for `replies` collection (output for outgoing federation & fetching on incoming federation).
|
||
- Mix task to refresh counter cache (`mix pleroma.refresh_counter_cache`)
|
||
<details>
|
||
<summary>API Changes</summary>
|
||
|
||
- Job queue stats to the healthcheck page
|
||
- Admin API: Add ability to fetch reports, grouped by status `GET /api/pleroma/admin/grouped_reports`
|
||
- Admin API: Add ability to require password reset
|
||
- Mastodon API: Account entities now include `follow_requests_count` (planned Mastodon 3.x addition)
|
||
- Pleroma API: `GET /api/v1/pleroma/accounts/:id/scrobbles` to get a list of recently scrobbled items
|
||
- Pleroma API: `POST /api/v1/pleroma/scrobble` to scrobble a media item
|
||
- Mastodon API: Add `upload_limit`, `avatar_upload_limit`, `background_upload_limit`, and `banner_upload_limit` to `/api/v1/instance`
|
||
- Mastodon API: Add `pleroma.unread_conversation_count` to the Account entity
|
||
- OAuth: support for hierarchical permissions / [Mastodon 2.4.3 OAuth permissions](https://docs.joinmastodon.org/api/permissions/)
|
||
- Metadata Link: Atom syndication Feed
|
||
- Mix task to re-count statuses for all users (`mix pleroma.count_statuses`)
|
||
- Mastodon API: Add `exclude_visibilities` parameter to the timeline and notification endpoints
|
||
- Admin API: `/users/:nickname/toggle_activation` endpoint is now deprecated in favor of: `/users/activate`, `/users/deactivate`, both accept `nicknames` array
|
||
- Admin API: Multiple endpoints now require `nicknames` array, instead of singe `nickname`:
|
||
- `POST/DELETE /api/pleroma/admin/users/:nickname/permission_group/:permission_group` are deprecated in favor of: `POST/DELETE /api/pleroma/admin/users/permission_group/:permission_group`
|
||
- `DELETE /api/pleroma/admin/users` (`nickname` query param or `nickname` sent in JSON body) is deprecated in favor of: `DELETE /api/pleroma/admin/users` (`nicknames` query array param or `nicknames` sent in JSON body)
|
||
- Admin API: Add `GET /api/pleroma/admin/relay` endpoint - lists all followed relays
|
||
- Pleroma API: `POST /api/v1/pleroma/conversations/read` to mark all conversations as read
|
||
- ActivityPub: Support `Move` activities
|
||
- Mastodon API: Add `/api/v1/markers` for managing timeline read markers
|
||
- Mastodon API: Add the `recipients` parameter to `GET /api/v1/conversations`
|
||
- Configuration: `feed` option for user atom feed.
|
||
- Pleroma API: Add Emoji reactions
|
||
- Admin API: Add `/api/pleroma/admin/instances/:instance/statuses` - lists all statuses from a given instance
|
||
- Admin API: Add `/api/pleroma/admin/users/:nickname/statuses` - lists all statuses from a given user
|
||
- Admin API: `PATCH /api/pleroma/users/confirm_email` to confirm email for multiple users, `PATCH /api/pleroma/users/resend_confirmation_email` to resend confirmation email for multiple users
|
||
- ActivityPub: Configurable `type` field of the actors.
|
||
- Mastodon API: `/api/v1/accounts/:id` has `source/pleroma/actor_type` field.
|
||
- Mastodon API: `/api/v1/update_credentials` accepts `actor_type` field.
|
||
- Captcha: Support native provider
|
||
- Captcha: Enable by default
|
||
- Mastodon API: Add support for `account_id` param to filter notifications by the account
|
||
- Mastodon API: Add `emoji_reactions` property to Statuses
|
||
- Mastodon API: Change emoji reaction reply format
|
||
- Notifications: Added `pleroma:emoji_reaction` notification type
|
||
- Mastodon API: Change emoji reaction reply format once more
|
||
- Configuration: `feed.logo` option for tag feed.
|
||
- Tag feed: `/tags/:tag.rss` - list public statuses by hashtag.
|
||
- Mastodon API: Add `reacted` property to `emoji_reactions`
|
||
- Pleroma API: Add reactions for a single emoji.
|
||
- ActivityPub: `[:activitypub, :note_replies_output_limit]` setting sets the number of note self-replies to output on outgoing federation.
|
||
- Admin API: `GET /api/pleroma/admin/stats` to get status count by visibility scope
|
||
- Admin API: `GET /api/pleroma/admin/statuses` - list all statuses (accepts `godmode` and `local_only`)
|
||
</details>
|
||
|
||
### Fixed
|
||
- Report emails now include functional links to profiles of remote user accounts
|
||
- Not being able to log in to some third-party apps when logged in to MastoFE
|
||
- MRF: `Delete` activities being exempt from MRF policies
|
||
- OTP releases: Not being able to configure OAuth expired token cleanup interval
|
||
- OTP releases: Not being able to configure HTML sanitization policy
|
||
- OTP releases: Not being able to change upload limit (again)
|
||
- Favorites timeline now ordered by favorite date instead of post date
|
||
- Support for cancellation of a follow request
|
||
<details>
|
||
<summary>API Changes</summary>
|
||
|
||
- 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: Inability to get some local users by nickname in `/api/v1/accounts/:id_or_nickname`
|
||
- AdminAPI: If some status received reports both in the "new" format and "old" format it was considered reports on two different statuses (in the context of grouped reports)
|
||
- Admin API: Error when trying to update reports in the "old" format
|
||
- Mastodon API: Marking a conversation as read (`POST /api/v1/conversations/:id/read`) now no longer brings it to the top in the user's direct conversation list
|
||
</details>
|
||
|
||
## [1.1.9] - 2020-02-10
|
||
### Fixed
|
||
- OTP: Inability to set the upload limit (again)
|
||
- Not being able to pin polls
|
||
- Streaming API: incorrect handling of reblog mutes
|
||
- Rejecting the user when field length limit is exceeded
|
||
- OpenGraph provider: html entities in descriptions
|
||
|
||
## [1.1.8] - 2020-01-10
|
||
### Fixed
|
||
- Captcha generation issues
|
||
- Returned Kocaptcha endpoint to configuration
|
||
- Captcha validity is now 5 minutes
|
||
|
||
## [1.1.7] - 2019-12-13
|
||
### Fixed
|
||
- OTP: Inability to set the upload limit
|
||
- OTP: Inability to override node name/distribution type to run 2 Pleroma instances on the same machine
|
||
|
||
### Added
|
||
- Integrated captcha provider
|
||
|
||
### Changed
|
||
- Captcha enabled by default
|
||
- Default Captcha provider changed from `Pleroma.Captcha.Kocaptcha` to `Pleroma.Captcha.Native`
|
||
- Better `Cache-Control` header for static content
|
||
|
||
### Bundled Pleroma-FE Changes
|
||
#### Added
|
||
- Icons in the navigation panel
|
||
|
||
#### Fixed
|
||
- Improved support unauthenticated view of private instances
|
||
|
||
#### Removed
|
||
- Whitespace hack on empty post content
|
||
|
||
## [1.1.6] - 2019-11-19
|
||
### Fixed
|
||
- Not being able to log into to third party apps when the browser is logged into mastofe
|
||
- Email confirmation not being required even when enabled
|
||
- Mastodon API: conversations API crashing when one status is malformed
|
||
|
||
### Bundled Pleroma-FE Changes
|
||
#### Added
|
||
- About page
|
||
- Meme arrows
|
||
|
||
#### Fixed
|
||
- Image modal not closing unless clicked outside of image
|
||
- Attachment upload spinner not being centered
|
||
- Showing follow counters being 0 when they are actually hidden
|
||
|
||
## [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
|
||
- Frontend bundle updated to [044c9ad0](https://git.pleroma.social/pleroma/pleroma-fe/commit/044c9ad0562af059dd961d50961a3880fca9c642)
|
||
|
||
## [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
|
||
|
||
## [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
|
||
|
||
## [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.
|
||
|
||
## [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
|
||
|
||
## [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](https://github.com/tootsuite/mastodon/pull/9755) in [`GET /api/v1/accounts/:id/statuses`](https://docs.joinmastodon.org/api/rest/accounts/#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.
|
||
|
||
## [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.
|
||
|
||
## [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.
|
||
|
||
## [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.
|
||
- **Breaking:** ActivityPub: The `accept_blocks` configuration setting.
|
||
|
||
## [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
|
||
|
||
## [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.
|
||
|
||
## [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
|
||
|
||
## [1.0.1] - 2019-07-14
|
||
### Security
|
||
- OStatus: fix an object spoofing vulnerability.
|
||
|
||
## [1.0.0] - 2019-06-29
|
||
### Security
|
||
- Mastodon API: Fix display names not being sanitized
|
||
- Rich media: Do not crawl private IP ranges
|
||
|
||
### Added
|
||
- Digest email for inactive users
|
||
- 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](https://github.com/esl/MongooseIM) http authentication support.
|
||
- LDAP authentication
|
||
- External OAuth provider authentication
|
||
- Support for building a release using [`mix release`](https://hexdocs.pm/mix/master/Mix.Tasks.Release.html)
|
||
- A [job queue](https://git.pleroma.social/pleroma/pleroma_job_queue) for federation, emails, web push, etc.
|
||
- [Prometheus](https://prometheus.io/) 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`
|
||
- Federation: Support for `Question` and `Answer` objects
|
||
- Federation: 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: `email_notifications` option
|
||
- Configuration: `limit_to_local_content` option
|
||
- Pleroma API: User subscriptions
|
||
- Pleroma API: Healthcheck endpoint
|
||
- Pleroma API: `/api/v1/pleroma/mascot` per-user frontend mascot configuration endpoints
|
||
- Admin API: Endpoints for listing/revoking invite tokens
|
||
- Admin API: Endpoints for making users follow/unfollow each other
|
||
- Admin API: added filters (role, tags, email, name) for users endpoint
|
||
- Admin API: Endpoints for managing reports
|
||
- Admin API: Endpoints for deleting and changing the scope of individual reported statuses
|
||
- Admin API: Endpoints to view and change config settings.
|
||
- AdminFE: initial release with basic user management accessible at /pleroma/admin/
|
||
- Mastodon API: Add chat token to `verify_credentials` response
|
||
- Mastodon API: Add background image setting to `update_credentials`
|
||
- Mastodon API: [Scheduled statuses](https://docs.joinmastodon.org/api/rest/scheduled-statuses/)
|
||
- Mastodon API: `/api/v1/notifications/destroy_multiple` (glitch-soc extension)
|
||
- Mastodon API: `/api/v1/pleroma/accounts/:id/favourites` (API extension)
|
||
- Mastodon API: [Reports](https://docs.joinmastodon.org/api/rest/reports/)
|
||
- Mastodon API: `POST /api/v1/accounts` (account creation API)
|
||
- Mastodon API: [Polls](https://docs.joinmastodon.org/api/rest/polls/)
|
||
- ActivityPub C2S: OAuth endpoints
|
||
- 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](https://git.pleroma.social/pleroma/auto_linker)
|
||
- NodeInfo: Return `safe_dm_mentions` feature flag
|
||
- Federation: Expand the audience of delete activities to all recipients of the deleted object
|
||
- Federation: Removed `inReplyToStatusId` from objects
|
||
- 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.
|
||
- Admin API: Move the user related API to `api/pleroma/admin/users`
|
||
- Admin API: `POST /api/pleroma/admin/users` will take list of users
|
||
- Pleroma API: Support for emoji tags in `/api/pleroma/emoji` resulting in a breaking API change
|
||
- Mastodon API: Support for `exclude_types`, `limit` and `min_id` in `/api/v1/notifications`
|
||
- Mastodon API: Add `languages` and `registrations` to `/api/v1/instance`
|
||
- Mastodon API: Provide plaintext versions of cw/content in the Status entity
|
||
- Mastodon API: Add `pleroma.conversation_id`, `pleroma.in_reply_to_account_acct` fields to the Status entity
|
||
- Mastodon API: Add `pleroma.tags`, `pleroma.relationship{}`, `pleroma.is_moderator`, `pleroma.is_admin`, `pleroma.confirmation_pending`, `pleroma.hide_followers`, `pleroma.hide_follows`, `pleroma.hide_favorites` fields to the User entity
|
||
- Mastodon API: Add `pleroma.show_role`, `pleroma.no_rich_text` fields to the Source subentity
|
||
- Mastodon API: Add support for updating `no_rich_text`, `hide_followers`, `hide_follows`, `hide_favorites`, `show_role` in `PATCH /api/v1/update_credentials`
|
||
- Mastodon API: Add `pleroma.is_seen` to the Notification entity
|
||
- Mastodon API: Add `pleroma.local` to the Status entity
|
||
- Mastodon API: Add `preview` parameter to `POST /api/v1/statuses`
|
||
- Mastodon API: Add `with_muted` parameter to timeline endpoints
|
||
- Mastodon API: Actual reblog hiding instead of a dummy
|
||
- Mastodon API: Remove attachment limit in the Status entity
|
||
- Mastodon API: Added support max_id & since_id for bookmark timeline endpoints.
|
||
- Deps: Updated Cowboy to 2.6
|
||
- Deps: Updated Ecto to 3.0.7
|
||
- 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.
|
||
- Respond with a 404 Not implemented JSON error message when requested API is not implemented
|
||
- 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
|
||
- Pleroma API: Importing follows from Mastodon 2.8+
|
||
- Twitter API: Exposing default scope, `no_rich_text` of the user to anyone
|
||
- Twitter API: Returning the `role` object in user entity despite `show_role = false`
|
||
- Mastodon API: `/api/v1/favourites` serving only public activities
|
||
- Mastodon API: Reblogs having `in_reply_to_id` - `null` even when they are replies
|
||
- Mastodon API: Streaming API broadcasting wrong activity id
|
||
- Mastodon API: 500 errors when requesting a card for a private conversation
|
||
- Mastodon API: Handling of `reblogs` in `/api/v1/accounts/:id/follow`
|
||
- Mastodon API: Correct `reblogged`, `favourited`, and `bookmarked` values in the reblog status JSON
|
||
- Mastodon API: Exposing default scope of the user to anyone
|
||
- Mastodon API: Make `irreversible` field default to `false` [`POST /api/v1/filters`]
|
||
- Mastodon API: Replace missing non-nullable Card attributes with empty strings
|
||
- 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`
|
||
|
||
## [0.9.99999] - 2019-05-31
|
||
### Security
|
||
- Mastodon API: Fix lists leaking private posts
|
||
|
||
## [0.9.9999] - 2019-04-05
|
||
### Security
|
||
- Mastodon API: Fix content warnings skipping HTML sanitization
|
||
|
||
## [0.9.999] - 2019-03-13
|
||
Frontend changes only.
|
||
### Added
|
||
- Added floating action button for posting status on mobile
|
||
### Changed
|
||
- Changed user-settings icon to a pencil
|
||
### Fixed
|
||
- Keyboard shortcuts activating when typing a message
|
||
- Gaps when scrolling down on a timeline after showing new
|
||
|
||
## [0.9.99] - 2019-03-08
|
||
### Changed
|
||
- Update the frontend to the 0.9.99 tag
|
||
### Fixed
|
||
- Sign the date header in federation to fix Mastodon federation.
|
||
|
||
## [0.9.9] - 2019-02-22
|
||
This is our first stable release.
|