Merge branch 'revert-bca1512d' into 'develop'
[akkoma] / CHANGELOG.md
1 # Changelog
2 All notable changes to this project will be documented in this file.
3
4 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
5
6 ## [Unreleased]
7 ### Removed
8 - **Breaking**: Removed 1.0+ deprecated configurations `Pleroma.Upload, :strip_exif` and `:instance, :dedupe_media`
9 - **Breaking**: OStatus protocol support
10
11 ### Changed
12 - **Breaking:** Elixir >=1.8 is now required (was >= 1.7)
13 - **Breaking:** attachment links (`config :pleroma, :instance, no_attachment_links` and `config :pleroma, Pleroma.Upload, link_name`) disabled by default
14 - 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)
15 - Introduced [quantum](https://github.com/quantum-elixir/quantum-core) job scheduler
16 - Enabled `:instance, extended_nickname_format` in the default config
17 - Add `rel="ugc"` to all links in statuses, to prevent SEO spam
18 - Extract RSS functionality from OStatus
19 - MRF (Simple Policy): Also use `:accept`/`:reject` on the actors rather than only their activities
20 - OStatus: Extract RSS functionality
21 - Deprecated `User.Info` embedded schema (fields moved to `User`)
22 - Store status data inside Flag activity
23 - Deprecated (reorganized as `UserRelationship` entity) User fields with user AP IDs (`blocks`, `mutes`, `muted_reblogs`, `muted_notifications`, `subscribers`).
24 <details>
25 <summary>API Changes</summary>
26
27 - **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)
28 - **Breaking:** Admin API: Return link alongside with token on password reset
29 - **Breaking:** Admin API: `PUT /api/pleroma/admin/reports/:id` is now `PATCH /api/pleroma/admin/reports`, see admin_api.md for details
30 - **Breaking:** `/api/pleroma/admin/users/invite_token` now uses `POST`, changed accepted params and returns full invite in json instead of only token string.
31 - **Breaking** replying to reports is now "report notes", enpoint changed from `POST /api/pleroma/admin/reports/:id/respond` to `POST /api/pleroma/admin/reports/:id/notes`
32 - Admin API: Return `total` when querying for reports
33 - Mastodon API: Return `pleroma.direct_conversation_id` when creating a direct message (`POST /api/v1/statuses`)
34 - Admin API: Return link alongside with token on password reset
35 - Admin API: Support authentication via `x-admin-token` HTTP header
36 - Mastodon API: Add `pleroma.direct_conversation_id` to the status endpoint (`GET /api/v1/statuses/:id`)
37 - Mastodon API: `pleroma.thread_muted` to the Status entity
38 - Mastodon API: Mark the direct conversation as read for the author when they send a new direct message
39 - Mastodon API, streaming: Add `pleroma.direct_conversation_id` to the `conversation` stream event payload.
40 - Admin API: Render whole status in grouped reports
41 - Mastodon API: User timelines will now respect blocks, unless you are getting the user timeline of somebody you blocked (which would be empty otherwise).
42 </details>
43
44 ### Added
45 - `:chat_limit` option to limit chat characters.
46 - Refreshing poll results for remote polls
47 - Authentication: Added rate limit for password-authorized actions / login existence checks
48 - Static Frontend: Add the ability to render user profiles and notices server-side without requiring JS app.
49 - Mix task to re-count statuses for all users (`mix pleroma.count_statuses`)
50 - Mix task to list all users (`mix pleroma.user list`)
51 - 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).
52 - 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.
53 - User notification settings: Add `privacy_option` option.
54 - User settings: Add _This account is a_ option.
55 - OAuth: admin scopes support (relevant setting: `[:auth, :enforce_oauth_admin_scope_usage]`).
56 <details>
57 <summary>API Changes</summary>
58
59 - Job queue stats to the healthcheck page
60 - Admin API: Add ability to fetch reports, grouped by status `GET /api/pleroma/admin/grouped_reports`
61 - Admin API: Add ability to require password reset
62 - Mastodon API: Account entities now include `follow_requests_count` (planned Mastodon 3.x addition)
63 - Pleroma API: `GET /api/v1/pleroma/accounts/:id/scrobbles` to get a list of recently scrobbled items
64 - Pleroma API: `POST /api/v1/pleroma/scrobble` to scrobble a media item
65 - Mastodon API: Add `upload_limit`, `avatar_upload_limit`, `background_upload_limit`, and `banner_upload_limit` to `/api/v1/instance`
66 - Mastodon API: Add `pleroma.unread_conversation_count` to the Account entity
67 - OAuth: support for hierarchical permissions / [Mastodon 2.4.3 OAuth permissions](https://docs.joinmastodon.org/api/permissions/)
68 - Metadata Link: Atom syndication Feed
69 - Mix task to re-count statuses for all users (`mix pleroma.count_statuses`)
70 - Mastodon API: Add `exclude_visibilities` parameter to the timeline and notification endpoints
71 - Admin API: `/users/:nickname/toggle_activation` endpoint is now deprecated in favor of: `/users/activate`, `/users/deactivate`, both accept `nicknames` array
72 - Admin API: Multiple endpoints now require `nicknames` array, instead of singe `nickname`:
73 - `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`
74 - `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)
75 - Admin API: Add `GET /api/pleroma/admin/relay` endpoint - lists all followed relays
76 - Pleroma API: `POST /api/v1/pleroma/conversations/read` to mark all conversations as read
77 - ActivityPub: Support `Move` activities
78 - Mastodon API: Add `/api/v1/markers` for managing timeline read markers
79 - Mastodon API: Add the `recipients` parameter to `GET /api/v1/conversations`
80 - Configuration: `feed` option for user atom feed.
81 - Pleroma API: Add Emoji reactions
82 - Admin API: Add `/api/pleroma/admin/instances/:instance/statuses` - lists all statuses from a given instance
83 - 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
84 - ActivityPub: Configurable `type` field of the actors.
85 - Mastodon API: `/api/v1/accounts/:id` has `source/pleroma/actor_type` field.
86 - Mastodon API: `/api/v1/update_credentials` accepts `actor_type` field.
87 </details>
88
89 ### Fixed
90 - Report emails now include functional links to profiles of remote user accounts
91 - Not being able to log in to some third-party apps when logged in to MastoFE
92 - MRF: `Delete` activities being exempt from MRF policies
93 - OTP releases: Not being able to configure OAuth expired token cleanup interval
94 - OTP releases: Not being able to configure HTML sanitization policy
95 - Favorites timeline now ordered by favorite date instead of post date
96 <details>
97 <summary>API Changes</summary>
98
99 - Mastodon API: Fix private and direct statuses not being filtered out from the public timeline for an authenticated user (`GET /api/v1/timelines/public`)
100 - Mastodon API: Inability to get some local users by nickname in `/api/v1/accounts/:id_or_nickname`
101 - 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)
102 - Admin API: Error when trying to update reports in the "old" format
103 </details>
104
105 ## [1.1.6] - 2019-11-19
106 ### Fixed
107 - Not being able to log into to third party apps when the browser is logged into mastofe
108 - Email confirmation not being required even when enabled
109 - Mastodon API: conversations API crashing when one status is malformed
110
111 ### Bundled Pleroma-FE Changes
112 #### Added
113 - About page
114 - Meme arrows
115
116 #### Fixed
117 - Image modal not closing unless clicked outside of image
118 - Attachment upload spinner not being centered
119 - Showing follow counters being 0 when they are actually hidden
120
121 ## [1.1.5] - 2019-11-09
122 ### Fixed
123 - Polls having different numbers in timelines/notifications/poll api endpoints due to cache desyncronization
124 - Pleroma API: OAuth token endpoint not being found when ".json" suffix is appended
125
126 ### Changed
127 - Frontend bundle updated to [044c9ad0](https://git.pleroma.social/pleroma/pleroma-fe/commit/044c9ad0562af059dd961d50961a3880fca9c642)
128
129 ## [1.1.4] - 2019-11-01
130 ### Fixed
131 - Added a migration that fills up empty user.info fields to prevent breakage after previous unsafe migrations.
132 - Failure to migrate from pre-1.0.0 versions
133 - Mastodon API: Notification stream not including follow notifications
134
135 ## [1.1.3] - 2019-10-25
136 ### Fixed
137 - Blocked users showing up in notifications collapsed as if they were muted
138 - `pleroma_ctl` not working on Debian's default shell
139
140 ## [1.1.2] - 2019-10-18
141 ### Fixed
142 - `pleroma_ctl` trying to connect to a running instance when generating the config, which of course doesn't exist.
143
144 ## [1.1.1] - 2019-10-18
145 ### Fixed
146 - 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:
147 ```
148 delete from users where ap_id = 'https://your.instance.hostname/relay';
149 ```
150 - Bad user search matches
151
152 ## [1.1.0] - 2019-10-14
153 **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.
154
155 **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:
156 ```
157 curl -Lo ./bin/pleroma_ctl 'https://git.pleroma.social/pleroma/pleroma/raw/develop/rel/files/bin/pleroma_ctl'
158 ```
159 ### Security
160 - Mastodon API: respect post privacy in `/api/v1/statuses/:id/{favourited,reblogged}_by`
161
162 ### Removed
163 - **Breaking:** GNU Social API with Qvitter extensions support
164 - Emoji: Remove longfox emojis.
165 - Remove `Reply-To` header from report emails for admins.
166 - ActivityPub: The `/objects/:uuid/likes` endpoint.
167
168 ### Changed
169 - **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
170 - **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
171 - **Breaking:** `/api/pleroma/notifications/read` is moved to `/api/v1/pleroma/notifications/read` and now supports `max_id` and responds with Mastodon API entities.
172 - Configuration: added `config/description.exs`, from which `docs/config.md` is generated
173 - Configuration: OpenGraph and TwitterCard providers enabled by default
174 - Configuration: Filter.AnonymizeFilename added ability to retain file extension with custom text
175 - Federation: Return 403 errors when trying to request pages from a user's follower/following collections if they have `hide_followers`/`hide_follows` set
176 - NodeInfo: Return `skipThreadContainment` in `metadata` for the `skip_thread_containment` option
177 - NodeInfo: Return `mailerEnabled` in `metadata`
178 - Mastodon API: Unsubscribe followers when they unfollow a user
179 - Mastodon API: `pleroma.thread_muted` key in the Status entity
180 - AdminAPI: Add "godmode" while fetching user statuses (i.e. admin can see private statuses)
181 - Improve digest email template
182 – Pagination: (optional) return `total` alongside with `items` when paginating
183 - The `Pleroma.FlakeId` module has been replaced with the `flake_id` library.
184
185 ### Fixed
186 - Following from Osada
187 - Favorites timeline doing database-intensive queries
188 - Metadata rendering errors resulting in the entire page being inaccessible
189 - `federation_incoming_replies_max_depth` option being ignored in certain cases
190 - Mastodon API: Handling of search timeouts (`/api/v1/search` and `/api/v2/search`)
191 - Mastodon API: Misskey's endless polls being unable to render
192 - Mastodon API: Embedded relationships not being properly rendered in the Account entity of Status entity
193 - Mastodon API: Notifications endpoint crashing if one notification failed to render
194 - Mastodon API: `exclude_replies` is correctly handled again.
195 - Mastodon API: Add `account_id`, `type`, `offset`, and `limit` to search API (`/api/v1/search` and `/api/v2/search`)
196 - Mastodon API, streaming: Fix filtering of notifications based on blocks/mutes/thread mutes
197 - Mastodon API: Fix private and direct statuses not being filtered out from the public timeline for an authenticated user (`GET /api/v1/timelines/public`)
198 - Mastodon API: Ensure the `account` field is not empty when rendering Notification entities.
199 - Mastodon API: Inability to get some local users by nickname in `/api/v1/accounts/:id_or_nickname`
200 - Mastodon API: Blocks are now treated consistently between the Streaming API and the Timeline APIs
201 - Rich Media: Parser failing when no TTL can be found by image TTL setters
202 - Rich Media: The crawled URL is now spliced into the rich media data.
203 - ActivityPub S2S: sharedInbox usage has been mostly aligned with the rules in the AP specification.
204 - ActivityPub C2S: follower/following collection pages being inaccessible even when authentifucated if `hide_followers`/ `hide_follows` was set
205 - ActivityPub: Deactivated user deletion
206 - ActivityPub: Fix `/users/:nickname/inbox` crashing without an authenticated user
207 - MRF: fix ability to follow a relay when AntiFollowbotPolicy was enabled
208 - ActivityPub: Correct addressing of Undo.
209 - ActivityPub: Correct addressing of profile update activities.
210 - ActivityPub: Polls are now refreshed when necessary.
211 - Report emails now include functional links to profiles of remote user accounts
212 - Existing user id not being preserved on insert conflict
213 - Pleroma.Upload base_url was not automatically whitelisted by MediaProxy. Now your custom CDN or file hosting will be accessed directly as expected.
214 - Report email not being sent to admins when the reporter is a remote user
215 - Reverse Proxy limiting `max_body_length` was incorrectly defined and only checked `Content-Length` headers which may not be sufficient in some circumstances
216
217 ### Added
218 - Expiring/ephemeral activites. All activities can have expires_at value set, which controls when they should be deleted automatically.
219 - 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.
220 - 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.
221 - Configuration: `ActivityExpiration.enabled` controls whether expired activites will get deleted at the appropriate time. Enabled by default.
222 - Conversations: Add Pleroma-specific conversation endpoints and status posting extensions. Run the `bump_all_conversations` task again to create the necessary data.
223 - MRF: Support for priming the mediaproxy cache (`Pleroma.Web.ActivityPub.MRF.MediaProxyWarmingPolicy`)
224 - MRF: Support for excluding specific domains from Transparency.
225 - MRF: Support for filtering posts based on who they mention (`Pleroma.Web.ActivityPub.MRF.MentionPolicy`)
226 - 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)
227 - Mastodon API, streaming: Add support for passing the token in the `Sec-WebSocket-Protocol` header
228 - Mastodon API, extension: Ability to reset avatar, profile banner, and background
229 - Mastodon API: Add support for `fields_attributes` API parameter (setting custom fields)
230 - Mastodon API: Add support for categories for custom emojis by reusing the group feature. <https://github.com/tootsuite/mastodon/pull/11196>
231 - Mastodon API: Add support for muting/unmuting notifications
232 - 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>
233 - Mastodon API: Add support for the `domain_blocking` attribute in the relationship API (`GET /api/v1/accounts/relationships`).
234 - Mastodon API: Add `pleroma.deactivated` to the Account entity
235 - Mastodon API: added `/auth/password` endpoint for password reset with rate limit.
236 - Mastodon API: /api/v1/accounts/:id/statuses now supports nicknames or user id
237 - Mastodon API: Improve support for the user profile custom fields
238 - Mastodon API: Add support for `fields_attributes` API parameter (setting custom fields)
239 - Mastodon API: Added an endpoint to get multiple statuses by IDs (`GET /api/v1/statuses/?ids[]=1&ids[]=2`)
240 - Admin API: Return users' tags when querying reports
241 - Admin API: Return avatar and display name when querying users
242 - Admin API: Allow querying user by ID
243 - Admin API: Added support for `tuples`.
244 - Admin API: Added endpoints to run mix tasks pleroma.config migrate_to_db & pleroma.config migrate_from_db
245 - Added synchronization of following/followers counters for external users
246 - Configuration: `enabled` option for `Pleroma.Emails.Mailer`, defaulting to `false`.
247 - Configuration: Pleroma.Plugs.RateLimiter `bucket_name`, `params` options.
248 - Configuration: `user_bio_length` and `user_name_length` options.
249 - Addressable lists
250 - Twitter API: added rate limit for `/api/account/password_reset` endpoint.
251 - ActivityPub: Add an internal service actor for fetching ActivityPub objects.
252 - ActivityPub: Optional signing of ActivityPub object fetches.
253 - Admin API: Endpoint for fetching latest user's statuses
254 - Pleroma API: Add `/api/v1/pleroma/accounts/confirmation_resend?email=<email>` for resending account confirmation.
255 - Pleroma API: Email change endpoint.
256 - Admin API: Added moderation log
257 - Web response cache (currently, enabled for ActivityPub)
258 - Reverse Proxy: Do not retry failed requests to limit pressure on the peer
259
260 ### Changed
261 - Configuration: Filter.AnonymizeFilename added ability to retain file extension with custom text
262 - Admin API: changed json structure for saving config settings.
263 - RichMedia: parsers and their order are configured in `rich_media` config.
264 - RichMedia: add the rich media ttl based on image expiration time.
265
266 ## [1.0.7] - 2019-09-26
267 ### Fixed
268 - Broken federation on Erlang 22 (previous versions of hackney http client were using an option that got deprecated)
269 ### Changed
270 - ActivityPub: The first page in inboxes/outboxes is no longer embedded.
271
272 ## [1.0.6] - 2019-08-14
273 ### Fixed
274 - MRF: fix use of unserializable keyword lists in describe() implementations
275 - ActivityPub S2S: POST requests are now signed with `(request-target)` pseudo-header.
276
277 ## [1.0.5] - 2019-08-13
278 ### Fixed
279 - Mastodon API: follower/following counters not being nullified, when `hide_follows`/`hide_followers` is set
280 - Mastodon API: `muted` in the Status entity, using author's account to determine if the thread was muted
281 - Mastodon API: return the actual profile URL in the Account entity's `url` property when appropriate
282 - Templates: properly style anchor tags
283 - Objects being re-embedded to activities after being updated (e.g faved/reposted). Running 'mix pleroma.database prune_objects' again is advised.
284 - Not being able to access the Mastodon FE login page on private instances
285 - MRF: ensure that subdomain_match calls are case-insensitive
286 - Fix internal server error when using the healthcheck API.
287
288 ### Added
289 - **Breaking:** MRF describe API, which adds support for exposing configuration information about MRF policies to NodeInfo.
290 Custom modules will need to be updated by adding, at the very least, `def describe, do: {:ok, %{}}` to the MRF policy modules.
291 - Relays: Added a task to list relay subscriptions.
292 - MRF: Support for filtering posts based on ActivityStreams vocabulary (`Pleroma.Web.ActivityPub.MRF.VocabularyPolicy`)
293 - MRF (Simple Policy): Support for wildcard domains.
294 - Support for wildcard domains in user domain blocks setting.
295 - Configuration: `quarantined_instances` support wildcard domains.
296 - Mix Tasks: `mix pleroma.database fix_likes_collections`
297 - Configuration: `federation_incoming_replies_max_depth` option
298
299 ### Removed
300 - Federation: Remove `likes` from objects.
301 - **Breaking:** ActivityPub: The `accept_blocks` configuration setting.
302
303 ## [1.0.4] - 2019-08-01
304 ### Fixed
305 - Invalid SemVer version generation, when the current branch does not have commits ahead of tag/checked out on a tag
306
307 ## [1.0.3] - 2019-07-31
308 ### Security
309 - OStatus: eliminate the possibility of a protocol downgrade attack.
310 - OStatus: prevent following locked accounts, bypassing the approval process.
311 - TwitterAPI: use CommonAPI to handle remote follows instead of OStatus.
312
313 ## [1.0.2] - 2019-07-28
314 ### Fixed
315 - Not being able to pin unlisted posts
316 - Mastodon API: represent poll IDs as strings
317 - MediaProxy: fix matching filenames
318 - MediaProxy: fix filename encoding
319 - Migrations: fix a sporadic migration failure
320 - Metadata rendering errors resulting in the entire page being inaccessible
321 - Federation/MediaProxy not working with instances that have wrong certificate order
322 - ActivityPub S2S: remote user deletions now work the same as local user deletions.
323
324 ### Changed
325 - Configuration: OpenGraph and TwitterCard providers enabled by default
326 - Configuration: Filter.AnonymizeFilename added ability to retain file extension with custom text
327
328 ## [1.0.1] - 2019-07-14
329 ### Security
330 - OStatus: fix an object spoofing vulnerability.
331
332 ## [1.0.0] - 2019-06-29
333 ### Security
334 - Mastodon API: Fix display names not being sanitized
335 - Rich media: Do not crawl private IP ranges
336
337 ### Added
338 - Digest email for inactive users
339 - Add a generic settings store for frontends / clients to use.
340 - Explicit addressing option for posting.
341 - Optional SSH access mode. (Needs `erlang-ssh` package on some distributions).
342 - [MongooseIM](https://github.com/esl/MongooseIM) http authentication support.
343 - LDAP authentication
344 - External OAuth provider authentication
345 - Support for building a release using [`mix release`](https://hexdocs.pm/mix/master/Mix.Tasks.Release.html)
346 - A [job queue](https://git.pleroma.social/pleroma/pleroma_job_queue) for federation, emails, web push, etc.
347 - [Prometheus](https://prometheus.io/) metrics
348 - Support for Mastodon's remote interaction
349 - Mix Tasks: `mix pleroma.database bump_all_conversations`
350 - Mix Tasks: `mix pleroma.database remove_embedded_objects`
351 - Mix Tasks: `mix pleroma.database update_users_following_followers_counts`
352 - Mix Tasks: `mix pleroma.user toggle_confirmed`
353 - Mix Tasks: `mix pleroma.config migrate_to_db`
354 - Mix Tasks: `mix pleroma.config migrate_from_db`
355 - Federation: Support for `Question` and `Answer` objects
356 - Federation: Support for reports
357 - Configuration: `poll_limits` option
358 - Configuration: `pack_extensions` option
359 - Configuration: `safe_dm_mentions` option
360 - Configuration: `link_name` option
361 - Configuration: `fetch_initial_posts` option
362 - Configuration: `notify_email` option
363 - Configuration: Media proxy `whitelist` option
364 - Configuration: `report_uri` option
365 - Configuration: `email_notifications` option
366 - Configuration: `limit_to_local_content` option
367 - Pleroma API: User subscriptions
368 - Pleroma API: Healthcheck endpoint
369 - Pleroma API: `/api/v1/pleroma/mascot` per-user frontend mascot configuration endpoints
370 - Admin API: Endpoints for listing/revoking invite tokens
371 - Admin API: Endpoints for making users follow/unfollow each other
372 - Admin API: added filters (role, tags, email, name) for users endpoint
373 - Admin API: Endpoints for managing reports
374 - Admin API: Endpoints for deleting and changing the scope of individual reported statuses
375 - Admin API: Endpoints to view and change config settings.
376 - AdminFE: initial release with basic user management accessible at /pleroma/admin/
377 - Mastodon API: Add chat token to `verify_credentials` response
378 - Mastodon API: Add background image setting to `update_credentials`
379 - Mastodon API: [Scheduled statuses](https://docs.joinmastodon.org/api/rest/scheduled-statuses/)
380 - Mastodon API: `/api/v1/notifications/destroy_multiple` (glitch-soc extension)
381 - Mastodon API: `/api/v1/pleroma/accounts/:id/favourites` (API extension)
382 - Mastodon API: [Reports](https://docs.joinmastodon.org/api/rest/reports/)
383 - Mastodon API: `POST /api/v1/accounts` (account creation API)
384 - Mastodon API: [Polls](https://docs.joinmastodon.org/api/rest/polls/)
385 - ActivityPub C2S: OAuth endpoints
386 - Metadata: RelMe provider
387 - OAuth: added support for refresh tokens
388 - Emoji packs and emoji pack manager
389 - Object pruning (`mix pleroma.database prune_objects`)
390 - OAuth: added job to clean expired access tokens
391 - MRF: Support for rejecting reports from specific instances (`mrf_simple`)
392 - MRF: Support for stripping avatars and banner images from specific instances (`mrf_simple`)
393 - MRF: Support for running subchains.
394 - Configuration: `skip_thread_containment` option
395 - Configuration: `rate_limit` option. See `Pleroma.Plugs.RateLimiter` documentation for details.
396 - MRF: Support for filtering out likely spam messages by rejecting posts from new users that contain links.
397 - Configuration: `ignore_hosts` option
398 - Configuration: `ignore_tld` option
399 - Configuration: default syslog tag "Pleroma" is now lowercased to "pleroma"
400
401 ### Changed
402 - **Breaking:** bind to 127.0.0.1 instead of 0.0.0.0 by default
403 - **Breaking:** Configuration: move from Pleroma.Mailer to Pleroma.Emails.Mailer
404 - Thread containment / test for complete visibility will be skipped by default.
405 - Enforcement of OAuth scopes
406 - Add multiple use/time expiring invite token
407 - Restyled OAuth pages to fit with Pleroma's default theme
408 - Link/mention/hashtag detection is now handled by [auto_linker](https://git.pleroma.social/pleroma/auto_linker)
409 - NodeInfo: Return `safe_dm_mentions` feature flag
410 - Federation: Expand the audience of delete activities to all recipients of the deleted object
411 - Federation: Removed `inReplyToStatusId` from objects
412 - Configuration: Dedupe enabled by default
413 - Configuration: Default log level in `prod` environment is now set to `warn`
414 - Configuration: Added `extra_cookie_attrs` for setting non-standard cookie attributes. Defaults to ["SameSite=Lax"] so that remote follows work.
415 - Timelines: Messages involving people you have blocked will be excluded from the timeline in all cases instead of just repeats.
416 - Admin API: Move the user related API to `api/pleroma/admin/users`
417 - Admin API: `POST /api/pleroma/admin/users` will take list of users
418 - Pleroma API: Support for emoji tags in `/api/pleroma/emoji` resulting in a breaking API change
419 - Mastodon API: Support for `exclude_types`, `limit` and `min_id` in `/api/v1/notifications`
420 - Mastodon API: Add `languages` and `registrations` to `/api/v1/instance`
421 - Mastodon API: Provide plaintext versions of cw/content in the Status entity
422 - Mastodon API: Add `pleroma.conversation_id`, `pleroma.in_reply_to_account_acct` fields to the Status entity
423 - 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
424 - Mastodon API: Add `pleroma.show_role`, `pleroma.no_rich_text` fields to the Source subentity
425 - Mastodon API: Add support for updating `no_rich_text`, `hide_followers`, `hide_follows`, `hide_favorites`, `show_role` in `PATCH /api/v1/update_credentials`
426 - Mastodon API: Add `pleroma.is_seen` to the Notification entity
427 - Mastodon API: Add `pleroma.local` to the Status entity
428 - Mastodon API: Add `preview` parameter to `POST /api/v1/statuses`
429 - Mastodon API: Add `with_muted` parameter to timeline endpoints
430 - Mastodon API: Actual reblog hiding instead of a dummy
431 - Mastodon API: Remove attachment limit in the Status entity
432 - Mastodon API: Added support max_id & since_id for bookmark timeline endpoints.
433 - Deps: Updated Cowboy to 2.6
434 - Deps: Updated Ecto to 3.0.7
435 - Don't ship finmoji by default, they can be installed as an emoji pack
436 - Hide deactivated users and their statuses
437 - Posts which are marked sensitive or tagged nsfw no longer have link previews.
438 - HTTP connection timeout is now set to 10 seconds.
439 - Respond with a 404 Not implemented JSON error message when requested API is not implemented
440 - Rich Media: crawl only https URLs.
441
442 ### Fixed
443 - Follow requests don't get 'stuck' anymore.
444 - Added an FTS index on objects. Running `vacuum analyze` and setting a larger `work_mem` is recommended.
445 - Followers counter not being updated when a follower is blocked
446 - Deactivated users being able to request an access token
447 - Limit on request body in rich media/relme parsers being ignored resulting in a possible memory leak
448 - Proper Twitter Card generation instead of a dummy
449 - Deletions failing for users with a large number of posts
450 - NodeInfo: Include admins in `staffAccounts`
451 - ActivityPub: Crashing when requesting empty local user's outbox
452 - Federation: Handling of objects without `summary` property
453 - Federation: Add a language tag to activities as required by ActivityStreams 2.0
454 - Federation: Do not federate avatar/banner if set to default allowing other servers/clients to use their defaults
455 - Federation: Cope with missing or explicitly nulled address lists
456 - Federation: Explicitly ensure activities addressed to `as:Public` become addressed to the followers collection
457 - Federation: Better cope with actors which do not declare a followers collection and use `as:Public` with these semantics
458 - Federation: Follow requests from remote users who have been blocked will be automatically rejected if appropriate
459 - MediaProxy: Parse name from content disposition headers even for non-whitelisted types
460 - MediaProxy: S3 link encoding
461 - Rich Media: Reject any data which cannot be explicitly encoded into JSON
462 - Pleroma API: Importing follows from Mastodon 2.8+
463 - Twitter API: Exposing default scope, `no_rich_text` of the user to anyone
464 - Twitter API: Returning the `role` object in user entity despite `show_role = false`
465 - Mastodon API: `/api/v1/favourites` serving only public activities
466 - Mastodon API: Reblogs having `in_reply_to_id` - `null` even when they are replies
467 - Mastodon API: Streaming API broadcasting wrong activity id
468 - Mastodon API: 500 errors when requesting a card for a private conversation
469 - Mastodon API: Handling of `reblogs` in `/api/v1/accounts/:id/follow`
470 - Mastodon API: Correct `reblogged`, `favourited`, and `bookmarked` values in the reblog status JSON
471 - Mastodon API: Exposing default scope of the user to anyone
472 - Mastodon API: Make `irreversible` field default to `false` [`POST /api/v1/filters`]
473 - Mastodon API: Replace missing non-nullable Card attributes with empty strings
474 - User-Agent is now sent correctly for all HTTP requests.
475 - MRF: Simple policy now properly delists imported or relayed statuses
476
477 ## Removed
478 - Configuration: `config :pleroma, :fe` in favor of the more flexible `config :pleroma, :frontend_configurations`
479
480 ## [0.9.99999] - 2019-05-31
481 ### Security
482 - Mastodon API: Fix lists leaking private posts
483
484 ## [0.9.9999] - 2019-04-05
485 ### Security
486 - Mastodon API: Fix content warnings skipping HTML sanitization
487
488 ## [0.9.999] - 2019-03-13
489 Frontend changes only.
490 ### Added
491 - Added floating action button for posting status on mobile
492 ### Changed
493 - Changed user-settings icon to a pencil
494 ### Fixed
495 - Keyboard shortcuts activating when typing a message
496 - Gaps when scrolling down on a timeline after showing new
497
498 ## [0.9.99] - 2019-03-08
499 ### Changed
500 - Update the frontend to the 0.9.99 tag
501 ### Fixed
502 - Sign the date header in federation to fix Mastodon federation.
503
504 ## [0.9.9] - 2019-02-22
505 This is our first stable release.