2019-04-12 15:31:18 -06:00
# Changelog
2020-11-17 05:10:58 -07:00
2019-04-12 15:31:18 -06:00
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/ ).
2024-06-03 15:09:17 -06:00
## UNRELEASED
Restrict media usage to owners
In Mastodon media can only be used by owners and only be associated with
a single post. We currently allow media to be associated with several
posts and until now did not limit their usage in posts to media owners.
However, media update and GET lookup was already limited to owners.
(In accordance with allowing media reuse, we also still allow GET
lookups of media already used in a post unlike Mastodon)
Allowing reuse isn’t problematic per se, but allowing use by non-owners
can be problematic if media ids of private-scoped posts can be guessed
since creating a new post with this media id will reveal the uploaded
file content and alt text.
Given media ids are currently just part of a sequentieal series shared
with some other objects, guessing media ids is with some persistence
indeed feasible.
E.g. sampline some public media ids from a real-world
instance with 112 total and 61 monthly-active users:
17.465.096 at t0
17.472.673 at t1 = t0 + 4h
17.473.248 at t2 = t1 + 20min
This gives about 30 new ids per minute of which most won't be
local media but remote and local posts, poll answers etc.
Assuming the default ratelimit of 15 post actions per 10s, scraping all
media for the 4h interval takes about 84 minutes and scraping the 20min
range mere 6.3 minutes. (Until the preceding commit, post updates were
not rate limited at all, allowing even faster scraping.)
If an attacker can infer (e.g. via reply to a follower-only post not
accessbile to the attacker) some sensitive information was uploaded
during a specific time interval and has some pointers regarding the
nature of the information, identifying the specific upload out of all
scraped media for this timerange is not impossible.
Thus restrict media usage to owners.
Checking ownership just in ActivitDraft would already be sufficient,
since when a scheduled status actually gets posted it goes through
ActivityDraft again, but would erroneously return a success status
when scheduling an illegal post.
Independently discovered and fixed by mint in Pleroma
https://git.pleroma.social/pleroma/pleroma/-/commit/1afde067b12ad0062c1820091ea9b0a680819281
2024-04-24 09:46:18 -06:00
2024-05-02 13:52:09 -06:00
## BREAKING
- Minimum PostgreSQL version is raised to 12
2024-05-16 13:05:01 -06:00
## Added
- Implement [FEP-67ff ](https://codeberg.org/fediverse/fep/src/branch/main/fep/67ff/fep-67ff.md ) (federation documentation)
2024-05-14 23:05:28 -06:00
- Meilisearch: it is now possible to use separate keys for search and admin actions
2024-05-02 14:44:48 -06:00
## Fixed
- Meilisearch: order of results returned from our REST API now actually matches how Meilisearch ranks results
2024-06-03 15:09:17 -06:00
## 2024.04.1 (Security)
## Fixed
- Issue allowing non-owners to use media objects in posts
- Issue allowing use of non-media objects as attachments and crashing timeline rendering
- Issue allowing webfinger spoofing in certain situations
2024-04-27 08:08:21 -06:00
## 2024.04
2024-02-25 15:27:10 -07:00
## Added
2024-04-12 11:50:57 -06:00
- Support for [FEP-fffd ](https://codeberg.org/fediverse/fep/src/branch/main/fep/fffd/fep-fffd.md ) (proxy objects)
2024-04-12 12:13:33 -06:00
- Verified support for elixir 1.16
2024-04-14 12:31:33 -06:00
- Uploadfilter `Pleroma.Upload.Filter.Exiftool.ReadDescription` returns description values to the FE so they can pre fill the image description field
2024-04-25 16:01:13 -06:00
NOTE: this filter MUST be placed before `Exiftool.StripMetadata` to work
2024-04-12 12:13:33 -06:00
2024-02-25 15:27:10 -07:00
## Changed
2024-04-15 19:35:59 -06:00
- Inbound pipeline error handing was modified somewhat, which should lead to less incomprehensible log spam. Hopefully.
2024-04-18 12:05:29 -06:00
- Uploadfilter `Pleroma.Upload.Filter.Exiftool` was replaced by `Pleroma.Upload.Filter.Exiftool.StripMetadata` ;
the latter strips all non-essential metadata by default but can be configured.
To regain the old behaviour of only stripping GPS data set `purge: ["gps:all"]` .
2024-04-16 12:37:00 -06:00
- Uploadfilter `Pleroma.Upload.Filter.Exiftool` has been renamed to `Pleroma.Upload.Filter.Exiftool.StripMetadata`
2024-04-25 15:35:20 -06:00
- MRF.InlineQuotePolicy now prefers to insert display URLs instead of ActivityPub IDs
- Old accounts are no longer listed in WebFinger as aliases; this was breaking spec
2024-02-25 15:27:10 -07:00
## Fixed
- Issue preventing fetching anything from IPv6-only instances
2024-04-11 22:16:47 -06:00
- Issue allowing post content to leak via opengraph tags despite :estrict\_unauthenticated being set
2024-04-25 15:35:20 -06:00
- Move activities no longer operate on stale user data
- Missing definitions in our JSON-LD context
- Issue mangling newlines in code blocks for RSS/Atom feeds
2024-04-26 11:43:39 -06:00
- static\_fe squeezing non-square avatars and emoji
2024-04-25 15:35:20 -06:00
- Issue leading to properly JSON-LD compacted emoji reactions being rejected
- We now use a standard-compliant Accept header when fetching ActivityPub objects
2024-04-26 11:43:39 -06:00
- /api/pleroma/notification\_settings was rejecting body parameters;
2024-04-25 15:35:20 -06:00
this also broke changing this setting via akkoma-fe
- Issue leading to Mastodon bot accounts being rejected
2024-01-23 12:10:01 -07:00
- Scope misdetection of remote posts resulting from not recognising
JSON-LD-compacted forms of public scope; affected e.g. federation with bovine
2024-04-26 12:10:17 -06:00
- Ratelimits encountered when fetching objects are now respected; 429 responses will cause a backoff when we get one.
2024-04-25 15:35:20 -06:00
## Removed
- ActivityPub Client-To-Server write API endpoints have been disabled;
read endpoints are planned to be removed next release unless a clear need is demonstrated
2024-02-25 15:27:10 -07:00
2024-03-30 05:44:34 -06:00
## 2024.03
Sanitise Content-Type of uploads
The lack thereof enables spoofing ActivityPub objects.
A malicious user could upload fake activities as attachments
and (if having access to remote search) trick local and remote
fedi instances into fetching and processing it as a valid object.
If uploads are hosted on the same domain as the instance itself,
it is possible for anyone with upload access to impersonate(!)
other users of the same instance.
If uploads are exclusively hosted on a different domain, even the most
basic check of domain of the object id and fetch url matching should
prevent impersonation. However, it may still be possible to trick
servers into accepting bogus users on the upload (sub)domain and bogus
notes attributed to such users.
Instances which later migrated to a different domain and have a
permissive redirect rule in place can still be vulnerable.
If — like Akkoma — the fetching server is overly permissive with
redirects, impersonation still works.
This was possible because Plug.Static also uses our custom
MIME type mappings used for actually authentic AP objects.
Provided external storage providers don’t somehow return ActivityStream
Content-Types on their own, instances using those are also safe against
their users being spoofed via uploads.
Akkoma instances using the OnlyMedia upload filter
cannot be exploited as a vector in this way — IF the
fetching server validates the Content-Type of
fetched objects (Akkoma itself does this already).
However, restricting uploads to only multimedia files may be a bit too
heavy-handed. Instead this commit will restrict the returned
Content-Type headers for user uploaded files to a safe subset, falling
back to generic 'application/octet-stream' for anything else.
This will also protect against non-AP payloads as e.g. used in
past frontend code injection attacks.
It’s a slight regression in user comfort, if say PDFs are uploaded,
but this trade-off seems fairly acceptable.
(Note, just excluding our own custom types would offer no protection
against non-AP payloads and bear a (perhaps small) risk of a silent
regression should MIME ever decide to add a canonical extension for
ActivityPub objects)
Now, one might expect there to be other defence mechanisms
besides Content-Type preventing counterfeits from being accepted,
like e.g. validation of the queried URL and AP ID matching.
Inserting a self-reference into our uploads is hard, but unfortunately
*oma does not verify the id in such a way and happily accepts _anything_
from the same domain (without even considering redirects).
E.g. Sharkey (and possibly other *keys) seem to attempt to guard
against this by immediately refetching the object from its ID, but
this is easily circumvented by just uploading two payloads with the
ID of one linking to the other.
Unfortunately *oma is thus _both_ a vector for spoofing and
vulnerable to those spoof payloads, resulting in an easy way
to impersonate our users.
Similar flaws exists for emoji and media proxy.
Subsequent commits will fix this by rigorously sanitising
content types in more areas, hardening our checks, improving
the default config and discouraging insecure config options.
2024-03-04 09:50:21 -07:00
## Added
2024-03-28 15:24:02 -06:00
- CLI tasks best-effort checking for past abuse of the recent spoofing exploit
- new `:mrf_steal_emoji, :download_unknown_size` option; defaults to `false`
Sanitise Content-Type of uploads
The lack thereof enables spoofing ActivityPub objects.
A malicious user could upload fake activities as attachments
and (if having access to remote search) trick local and remote
fedi instances into fetching and processing it as a valid object.
If uploads are hosted on the same domain as the instance itself,
it is possible for anyone with upload access to impersonate(!)
other users of the same instance.
If uploads are exclusively hosted on a different domain, even the most
basic check of domain of the object id and fetch url matching should
prevent impersonation. However, it may still be possible to trick
servers into accepting bogus users on the upload (sub)domain and bogus
notes attributed to such users.
Instances which later migrated to a different domain and have a
permissive redirect rule in place can still be vulnerable.
If — like Akkoma — the fetching server is overly permissive with
redirects, impersonation still works.
This was possible because Plug.Static also uses our custom
MIME type mappings used for actually authentic AP objects.
Provided external storage providers don’t somehow return ActivityStream
Content-Types on their own, instances using those are also safe against
their users being spoofed via uploads.
Akkoma instances using the OnlyMedia upload filter
cannot be exploited as a vector in this way — IF the
fetching server validates the Content-Type of
fetched objects (Akkoma itself does this already).
However, restricting uploads to only multimedia files may be a bit too
heavy-handed. Instead this commit will restrict the returned
Content-Type headers for user uploaded files to a safe subset, falling
back to generic 'application/octet-stream' for anything else.
This will also protect against non-AP payloads as e.g. used in
past frontend code injection attacks.
It’s a slight regression in user comfort, if say PDFs are uploaded,
but this trade-off seems fairly acceptable.
(Note, just excluding our own custom types would offer no protection
against non-AP payloads and bear a (perhaps small) risk of a silent
regression should MIME ever decide to add a canonical extension for
ActivityPub objects)
Now, one might expect there to be other defence mechanisms
besides Content-Type preventing counterfeits from being accepted,
like e.g. validation of the queried URL and AP ID matching.
Inserting a self-reference into our uploads is hard, but unfortunately
*oma does not verify the id in such a way and happily accepts _anything_
from the same domain (without even considering redirects).
E.g. Sharkey (and possibly other *keys) seem to attempt to guard
against this by immediately refetching the object from its ID, but
this is easily circumvented by just uploading two payloads with the
ID of one linking to the other.
Unfortunately *oma is thus _both_ a vector for spoofing and
vulnerable to those spoof payloads, resulting in an easy way
to impersonate our users.
Similar flaws exists for emoji and media proxy.
Subsequent commits will fix this by rigorously sanitising
content types in more areas, hardening our checks, improving
the default config and discouraging insecure config options.
2024-03-04 09:50:21 -07:00
## Changed
2024-03-28 15:24:02 -06:00
- `Pleroma.Upload, :base_url` now MUST be configured explicitly if used;
2024-03-04 09:50:22 -07:00
use of the same domain as the instance is **strongly** discouraged
2024-03-28 15:24:02 -06:00
- `:media_proxy, :base_url` now MUST be configured explicitly if used;
use of the same domain as the instance is **strongly** discouraged
- StealEmoji:
- now uses the pack.json format;
existing users must migrate with an out-of-band script (check release notes)
- only steals shortcodes recognised as valid
- URLs of stolen emoji is no longer predictable
2024-03-04 10:39:08 -07:00
- The `Dedupe` upload filter is now always active;
`AnonymizeFilenames` is again opt-in
2024-03-28 15:24:02 -06:00
- received AP data is sanity checked before we attempt to parse it as a user
- Uploads, emoji and media proxy now restrict Content-Type headers to a safe subset
- Akkoma will no longer fetch and parse objects hosted on the same domain
Sanitise Content-Type of uploads
The lack thereof enables spoofing ActivityPub objects.
A malicious user could upload fake activities as attachments
and (if having access to remote search) trick local and remote
fedi instances into fetching and processing it as a valid object.
If uploads are hosted on the same domain as the instance itself,
it is possible for anyone with upload access to impersonate(!)
other users of the same instance.
If uploads are exclusively hosted on a different domain, even the most
basic check of domain of the object id and fetch url matching should
prevent impersonation. However, it may still be possible to trick
servers into accepting bogus users on the upload (sub)domain and bogus
notes attributed to such users.
Instances which later migrated to a different domain and have a
permissive redirect rule in place can still be vulnerable.
If — like Akkoma — the fetching server is overly permissive with
redirects, impersonation still works.
This was possible because Plug.Static also uses our custom
MIME type mappings used for actually authentic AP objects.
Provided external storage providers don’t somehow return ActivityStream
Content-Types on their own, instances using those are also safe against
their users being spoofed via uploads.
Akkoma instances using the OnlyMedia upload filter
cannot be exploited as a vector in this way — IF the
fetching server validates the Content-Type of
fetched objects (Akkoma itself does this already).
However, restricting uploads to only multimedia files may be a bit too
heavy-handed. Instead this commit will restrict the returned
Content-Type headers for user uploaded files to a safe subset, falling
back to generic 'application/octet-stream' for anything else.
This will also protect against non-AP payloads as e.g. used in
past frontend code injection attacks.
It’s a slight regression in user comfort, if say PDFs are uploaded,
but this trade-off seems fairly acceptable.
(Note, just excluding our own custom types would offer no protection
against non-AP payloads and bear a (perhaps small) risk of a silent
regression should MIME ever decide to add a canonical extension for
ActivityPub objects)
Now, one might expect there to be other defence mechanisms
besides Content-Type preventing counterfeits from being accepted,
like e.g. validation of the queried URL and AP ID matching.
Inserting a self-reference into our uploads is hard, but unfortunately
*oma does not verify the id in such a way and happily accepts _anything_
from the same domain (without even considering redirects).
E.g. Sharkey (and possibly other *keys) seem to attempt to guard
against this by immediately refetching the object from its ID, but
this is easily circumvented by just uploading two payloads with the
ID of one linking to the other.
Unfortunately *oma is thus _both_ a vector for spoofing and
vulnerable to those spoof payloads, resulting in an easy way
to impersonate our users.
Similar flaws exists for emoji and media proxy.
Subsequent commits will fix this by rigorously sanitising
content types in more areas, hardening our checks, improving
the default config and discouraging insecure config options.
2024-03-04 09:50:21 -07:00
## Fixed
- Critical security issue allowing Akkoma to be used as a vector for
(depending on configuration) impersonation of other users or creation
of bogus users and posts on the upload domain
2024-03-28 15:24:02 -06:00
- Critical security issue letting Akkoma fall for the above impersonation
payloads due to lack of strict id checking
- Critical security issue allowing domains redirect to to pose as the initial domain
(e.g. with media proxy's fallback redirects)
- refetched objects can no longer attribute themselves to third-party actors
(this had no externally visible effect since actor info is read from the Create activity)
- our litepub JSON-LD schema is now served with the correct content type
- remote APNG attachments are now recognised as images
Sanitise Content-Type of uploads
The lack thereof enables spoofing ActivityPub objects.
A malicious user could upload fake activities as attachments
and (if having access to remote search) trick local and remote
fedi instances into fetching and processing it as a valid object.
If uploads are hosted on the same domain as the instance itself,
it is possible for anyone with upload access to impersonate(!)
other users of the same instance.
If uploads are exclusively hosted on a different domain, even the most
basic check of domain of the object id and fetch url matching should
prevent impersonation. However, it may still be possible to trick
servers into accepting bogus users on the upload (sub)domain and bogus
notes attributed to such users.
Instances which later migrated to a different domain and have a
permissive redirect rule in place can still be vulnerable.
If — like Akkoma — the fetching server is overly permissive with
redirects, impersonation still works.
This was possible because Plug.Static also uses our custom
MIME type mappings used for actually authentic AP objects.
Provided external storage providers don’t somehow return ActivityStream
Content-Types on their own, instances using those are also safe against
their users being spoofed via uploads.
Akkoma instances using the OnlyMedia upload filter
cannot be exploited as a vector in this way — IF the
fetching server validates the Content-Type of
fetched objects (Akkoma itself does this already).
However, restricting uploads to only multimedia files may be a bit too
heavy-handed. Instead this commit will restrict the returned
Content-Type headers for user uploaded files to a safe subset, falling
back to generic 'application/octet-stream' for anything else.
This will also protect against non-AP payloads as e.g. used in
past frontend code injection attacks.
It’s a slight regression in user comfort, if say PDFs are uploaded,
but this trade-off seems fairly acceptable.
(Note, just excluding our own custom types would offer no protection
against non-AP payloads and bear a (perhaps small) risk of a silent
regression should MIME ever decide to add a canonical extension for
ActivityPub objects)
Now, one might expect there to be other defence mechanisms
besides Content-Type preventing counterfeits from being accepted,
like e.g. validation of the queried URL and AP ID matching.
Inserting a self-reference into our uploads is hard, but unfortunately
*oma does not verify the id in such a way and happily accepts _anything_
from the same domain (without even considering redirects).
E.g. Sharkey (and possibly other *keys) seem to attempt to guard
against this by immediately refetching the object from its ID, but
this is easily circumvented by just uploading two payloads with the
ID of one linking to the other.
Unfortunately *oma is thus _both_ a vector for spoofing and
vulnerable to those spoof payloads, resulting in an easy way
to impersonate our users.
Similar flaws exists for emoji and media proxy.
Subsequent commits will fix this by rigorously sanitising
content types in more areas, hardening our checks, improving
the default config and discouraging insecure config options.
2024-03-04 09:50:21 -07:00
2024-04-02 03:20:59 -06:00
## Upgrade Notes
- As mentioned in "Changed", `Pleroma.Upload, :base_url` **MUST** be configured. Uploads will fail without it.
2024-04-02 04:36:26 -06:00
- Akkoma will refuse to start if this is not set.
2024-04-02 03:20:59 -06:00
- Same with media proxy.
2024-02-24 06:54:21 -07:00
## 2024.02
2023-08-07 09:17:17 -06:00
## Added
2023-08-07 09:27:23 -06:00
- Full compatibility with Erlang OTP26
2023-08-12 08:03:43 -06:00
- handling of GET /api/v1/preferences
2024-01-28 11:49:20 -07:00
- Akkoma API is now documented
2024-01-17 12:13:29 -07:00
- ability to auto-approve follow requests from users you are already following
2024-02-10 09:27:11 -07:00
- The SimplePolicy MRF can now strip user backgrounds from selected remote hosts
2023-08-07 09:17:17 -06:00
2023-08-09 07:39:28 -06:00
## Changed
- OTP builds are now built on erlang OTP26
2023-08-15 04:22:18 -06:00
- The base Phoenix framework is now updated to 1.7
2023-12-15 09:32:41 -07:00
- An `outbox` field has been added to actor profiles to comply with AP spec
2024-02-09 13:03:02 -07:00
- User profile backgrounds do now federate with other Akkoma instances and Sharkey
2023-08-15 04:22:18 -06:00
## Fixed
- Documentation issue in which a non-existing nginx file was referenced
2023-08-15 16:12:04 -06:00
- Issue where a bad inbox URL could break federation
2023-09-15 05:00:45 -06:00
- Issue where hashtag rel values would be scrubbed
2024-01-28 14:15:54 -07:00
- Issue where short domains listed in `transparency_obfuscate_domains` were not actually obfuscated
2023-08-09 07:39:28 -06:00
2023-08-05 06:26:42 -06:00
## 2023.08
2023-06-26 07:18:31 -06:00
2023-07-17 11:24:53 -06:00
## Added
2023-06-26 07:18:31 -06:00
- Added a new configuration option to the MediaProxy feature that allows the blocking of specific domains from using the media proxy or being explicitly allowed by the Content-Security-Policy.
- Please make sure instances you wanted to block media from are not in the MediaProxy `whitelist` , and instead use `blocklist` .
2023-06-26 08:07:07 -06:00
- `OnlyMedia` Upload Filter to simplify restricting uploads to audio, image, and video types
2023-07-27 07:41:18 -06:00
- ARM64 OTP builds
- Ubuntu22 builds are available for develop and stable
- other distributions are stable only
2023-08-01 04:43:50 -06:00
- Support for Elixir 1.15
- 1.14 is still supported
2023-08-04 08:37:15 -06:00
- OTP26 is currently "unsupported". It will probably work, but due to the way
it handles map ordering, the test suite will not pass for it as yet.
2023-07-27 07:41:18 -06:00
## Changed
2023-08-04 05:02:57 -06:00
- Alpine OTP builds are now from alpine 3.18, which is OpenSSLv3 compatible.
2023-07-27 07:41:18 -06:00
If you use alpine OTP builds you will have to update your local system.
2023-08-04 05:02:57 -06:00
- Debian OTP builds are now from a base of bookworm, which is OpenSSLv3 compatible.
2023-08-01 04:43:50 -06:00
If you use debian OTP builds you will have to update your local system to
bookworm (currently: stable).
2023-08-04 13:37:17 -06:00
- Ubuntu and debian builds are compatible again! (for now...)
2023-08-04 08:19:06 -06:00
- Blocks/Mutes now return from max ID to min ID, in line with mastodon.
2023-08-04 08:37:15 -06:00
- The AnonymizeFilename filter is now enabled by default.
2023-06-26 07:18:31 -06:00
2023-07-17 11:24:53 -06:00
## Fixed
- Deactivated users can no longer show up in the emoji reaction list
2023-07-17 12:19:03 -06:00
- Embedded posts can no longer bypass `:restrict\_unauthenticated`
2023-08-01 04:26:59 -06:00
- GET/HEAD requests will now work when requesting AWS-based instances.
2023-07-17 11:24:53 -06:00
2023-06-29 00:15:32 -06:00
## Security
- Add `no_new_privs` hardening to OpenRC and systemd service files
2023-08-05 06:29:29 -06:00
- XML parsers cannot load any entities (thanks @Mae@is .badat.dev!)
2023-06-21 17:00:25 -06:00
- Reduced permissions of config files and directories, distros requiring greater permissions like group-read need to pre-create the directories
2023-06-29 00:15:32 -06:00
2023-08-01 04:43:50 -06:00
## Removed
- Builds for debian oldstable (bullseye)
- If you are on oldstable you should NOT attempt to update OTP builds without
first updating your machine.
2023-05-23 07:10:01 -06:00
## 2023.05
2023-04-25 06:30:20 -06:00
2023-05-23 06:16:20 -06:00
## Added
- Custom options for users to accept/reject private messages
- options: everybody, nobody, people\_i\_follow
- MRF to reject notes from accounts newer than a given age
- this will have the side-effect of rejecting legitimate messages if your
post gets boosted outside of your local bubble and people your instance
does not know about reply to it.
2023-04-25 06:30:20 -06:00
## Fixed
- Support for `streams` public key URIs
2023-05-23 06:16:20 -06:00
- Bookmarks are cleaned up on DB prune now
2023-04-25 06:30:20 -06:00
2023-05-26 04:46:18 -06:00
## Security
- Fixed mediaproxy being a bit of a silly billy
2023-04-14 11:00:59 -06:00
## 2023.04
2023-03-15 16:20:32 -06:00
## Added
- Nodeinfo keys for unauthenticated timeline visibility
2023-03-17 09:33:28 -06:00
- Option to disable federated timeline
- Option to make the bubble timeline publicly accessible
2023-04-14 09:56:51 -06:00
- Ability to swap between installed standard frontends
- *mastodon frontends are still not counted as standard frontends due to the complexity in serving them correctly*.
2023-03-15 16:20:32 -06:00
2023-04-14 11:00:59 -06:00
### Upgrade Notes
- Elixir 1.14 is now required. If your distribution does not package this, you can
use [asdf ](https://asdf-vm.com/ ). At time of writing, elixir 1.14.3 / erlang 25.3
is confirmed to work.
2023-03-11 10:26:21 -07:00
## 2023.03
2023-02-23 04:07:59 -07:00
## Fixed
- Allowed contentMap to be updated on edit
2023-03-11 10:26:21 -07:00
- Filter creation now accepts expires\_at
2023-02-23 04:07:59 -07:00
2023-01-27 08:20:34 -07:00
### Changed
- Restoring the database from a dump now goes much faster without need for work-arounds
2023-03-11 10:26:21 -07:00
- Misskey reaction matching uses `content` parameter now
2023-01-27 08:20:34 -07:00
2023-01-23 01:43:16 -07:00
### Added
- Extend the mix task `prune_objects` with option `--prune-orphaned-activities` to also prune orphaned activities, allowing to reclaim even more database space
2023-02-26 15:12:31 -07:00
### Removed
- Possibility of using the `style` parameter on `span` elements. This will break certain MFM parameters.
2023-03-06 04:04:35 -07:00
- Option for "default" image description.
2023-02-26 15:12:31 -07:00
2023-02-11 04:19:33 -07:00
## 2023.02
2022-12-11 12:26:21 -07:00
2022-12-16 04:57:19 -07:00
### Added
- Prometheus metrics exporting from `/api/v1/akkoma/metrics`
2022-12-16 11:33:00 -07:00
- Ability to alter http pool size
2022-12-19 06:06:39 -07:00
- Translation of statuses via ArgosTranslate
2022-12-29 19:46:58 -07:00
- Argon2 password hashing
2022-12-29 13:56:06 -07:00
- Ability to "verify" links in profile fields via rel=me
- Mix tasks to dump/load config to/from json for bulk editing
2022-12-31 11:05:21 -07:00
- Followed hashtag list at /api/v1/followed\_tags, API parity with mastodon
2023-01-15 11:05:02 -07:00
- Ability to set posting language in the post form, API parity with mastodon
2023-01-15 12:02:58 -07:00
- Ability to match domains in MRF by a trailing wildcard
- Currently supported formats:
- `example.com` (implicitly matches `*.example.com` )
- `*.example.com`
- `example.*` (implicitly matches `*.example.*` )
2022-12-16 04:57:19 -07:00
2022-12-11 15:57:43 -07:00
### Removed
2022-12-11 12:26:21 -07:00
- Non-finch HTTP adapters
2022-12-14 05:38:48 -07:00
- Legacy redirect from /api/pleroma/admin to /api/v1/pleroma/admin
2022-12-16 06:20:48 -07:00
- Legacy redirects from /api/pleroma to /api/v1/pleroma
2022-12-29 19:46:58 -07:00
- :crypt dependency
2022-12-14 05:38:48 -07:00
2022-12-11 15:57:43 -07:00
### Changed
- Return HTTP error 413 when uploading an avatar or banner that's above the configured upload limit instead of a 500.
2022-12-16 04:57:19 -07:00
- Non-admin users now cannot register `admin` scope tokens (not security-critical, they didn't work before, but you _could_ create them)
2022-12-17 16:14:49 -07:00
- Admin scopes will be dropped on create
2022-12-16 10:31:04 -07:00
- Rich media will now backoff for 20 minutes after a failure
2022-12-31 11:09:27 -07:00
- Quote posts are now considered as part of the same thread as the post they are quoting
Prune Objects --keep-threads option (#350)
This adds an option to the prune_objects mix task.
The original way deleted all non-local public posts older than a certain time frame.
Here we add a different query which you can call using the option --keep-threads.
We query from the activities table all context id's where
1. the newest activity with this context is still old
2. none of the activities with this context is is local
3. none of the activities with this context is bookmarked
and delete all objects with these contexts.
The idea is that posts with local activities (posts, replies, likes, repeats...) may be interesting to keep.
Besides that, a post lives in a certain context (the thread), so we keep the whole thread as well.
Caveats:
* ~~Quotes have a different context. Therefore, when someone quotes a post, it's possible the quoted post will still be deleted.~~ fixed in https://akkoma.dev/AkkomaGang/akkoma/pulls/379
* Although undocumented (in docs/docs/administration/CLI_tasks/database.md/#prune-old-remote-posts-from-the-database), the 'normal' delete action still kept old remote non-public posts. I added an option to keep this behaviour, but this also means that you now have to explicitly provide that option. **This could be considered a breaking change!**
* ~~Note that this removes from the objects table, but not from the activities.~~ See https://akkoma.dev/AkkomaGang/akkoma/pulls/427 for that.
Some statistics from explain analyse:
(cost=1402845.92..1933782.00 rows=3810907 width=62) (actual time=2562455.486..2562455.495 rows=0 loops=1)
Planning Time: 505.327 ms
Trigger for constraint chat_message_references_object_id_fkey: time=651939.797 calls=921740
Trigger for constraint deliveries_object_id_fkey: time=52036.009 calls=921740
Trigger for constraint hashtags_objects_object_id_fkey: time=20665.778 calls=921740
Execution Time: 3287933.902 ms
***
**TODO**
1. [x] **Question:** Is it OK to keep it like this in regard to quote posts? If not (ie post quoted by local users should also be kept), should we give quotes the same context as the post they are quoting? (If we don't want to give them the same context, I'll have to see how/if I can do it without being too costly)
* See https://akkoma.dev/AkkomaGang/akkoma/pulls/379
2. [x] **Question:** the "original" query only deletes public posts (this is undocumented, but you can check the code). This new one doesn't care for scope. From the docs I get that the idea is that posts can be refetched when needed. But I have from a trusted source that Pleroma can't refetch non-public posts. I assume that's the reason why they are kept here. I see different options to deal with this
1. ~~We keep it as currently implemented and just don't care about scope with this option~~
2. ~~We add logic to not delete non-public posts either (I'll have to see how costly that becomes)~~
3. We add an extra --keep-non-public parameter. This is technically speaking breakage (you didn't have to provide a param before for this, now you do), but I'm inclined to not care much because it wasn't documented nor tested in the first place.
3. [x] See if we can do the query using Elixir
4. [x] Test on a bigger DB to see that we don't run into a timeout
5. [x] Add docs
Co-authored-by: ilja <git@ilja.space>
Reviewed-on: https://akkoma.dev/AkkomaGang/akkoma/pulls/350
Co-authored-by: ilja <akkoma.dev@ilja.space>
Co-committed-by: ilja <akkoma.dev@ilja.space>
2023-01-09 15:15:41 -07:00
- Extend the mix task `prune_objects` with options to keep more relevant posts
2022-12-19 13:41:48 -07:00
- Simplified HTTP signature processing
2022-12-30 20:52:52 -07:00
- Rich media will now hard-exit after 5 seconds, to prevent timeline hangs
2023-01-02 08:21:19 -07:00
- HTTP Content Security Policy is now far more strict to prevent any potential XSS/CSS leakages
2023-02-04 13:51:17 -07:00
- Follow requests are now paginated, matches mastodon API spec, so use the Link header to paginate.
2022-12-11 12:26:21 -07:00
2022-12-19 13:32:16 -07:00
### Fixed
- /api/v1/accounts/lookup will now respect restrict\_unauthenticated
2022-12-20 17:16:39 -07:00
- Unknown atoms in the config DB will no longer crash akkoma on boot
2022-12-19 13:32:16 -07:00
2022-12-14 05:38:48 -07:00
### Upgrade notes
- Ensure `config :tesla, :adapter` is either unset, or set to `{Tesla.Adapter.Finch, name: MyFinch}` in your .exs config
2022-12-16 06:20:48 -07:00
- Pleroma-FE will need to be updated to handle the new /api/v1/pleroma endpoints for custom emoji
2022-12-14 05:38:48 -07:00
2022-12-10 07:50:02 -07:00
## 2022.12
2022-11-24 04:27:01 -07:00
2022-11-24 05:27:16 -07:00
## Added
- Config: HTTP timeout options, :pool\_timeout and :receive\_timeout
2022-11-26 13:45:47 -07:00
- Added statistic gathering about instances which do/don't have signed fetches when they request from us
2022-11-28 06:34:54 -07:00
- Ability to set a default post expiry time, after which the post will be deleted. If used in concert with ActivityExpiration MRF, the expiry which comes _sooner_ will be applied.
2022-12-01 08:00:53 -07:00
- Regular task to prune local transient activities
- Task to manually run the transient prune job (pleroma.database prune\_task)
2022-12-04 11:35:04 -07:00
- Ability to follow hashtags
2022-12-09 12:57:29 -07:00
- Option to extend `reject` in MRF-Simple to apply to entire threads, where the originating instance is rejected
2022-12-09 13:13:31 -07:00
- Extra information to failed HTTP requests
2022-11-24 05:27:16 -07:00
2022-11-24 04:27:01 -07:00
## Changed
- MastoAPI: Accept BooleanLike input on `/api/v1/accounts/:id/follow` (fixes follows with mastodon.py)
2022-11-26 13:45:47 -07:00
- Relays from akkoma are now off by default
2022-11-26 14:06:20 -07:00
- NormalizeMarkup MRF is now on by default
2022-11-27 14:45:41 -07:00
- Follow/Block/Mute imports now spin off into *n* tasks to avoid the oban timeout
2022-12-01 08:00:53 -07:00
- Transient activities recieved from remote servers are no longer persisted in the database
2022-12-07 04:20:53 -07:00
- Overhauled static-fe view for logged-out users
2022-12-09 17:09:45 -07:00
- Blocked instances will now not be sent _any_ requests, even fetch ones that would get rejected by MRF anyhow
2022-12-01 08:00:53 -07:00
2022-12-09 12:59:27 -07:00
## Removed
- FollowBotPolicy
2022-12-09 13:01:38 -07:00
- Passing of undo/block into MRF
2022-12-09 12:59:27 -07:00
2022-12-01 08:00:53 -07:00
## Upgrade Notes
- If you have an old instance, you will probably want to run `mix pleroma.database prune_task` in the foreground to catch it up with the history of your instance.
2022-11-24 04:27:01 -07:00
2022-11-11 09:12:04 -07:00
## 2022.11
2022-10-11 04:40:43 -06:00
2022-10-16 13:25:54 -06:00
## Added
- Officially supported docker release
2022-10-19 04:01:14 -06:00
- Ability to remove followers unilaterally without a block
2022-11-06 15:50:11 -07:00
- Scraping of nodeinfo from remote instances to display instance info
2022-11-09 20:17:00 -07:00
- `requested_by` in relationships when the user has requested to follow you
2022-10-16 13:25:54 -06:00
2022-11-24 04:27:01 -07:00
## Changed
2022-10-11 04:40:43 -06:00
- Follows no longer override domain blocks, a domain block is final
2022-10-11 07:30:08 -06:00
- Deletes are now the lowest priority to publish and will be handled after creates
2022-11-06 16:50:32 -07:00
- Domain blocks are now subdomain-matches by default
2022-10-11 04:40:43 -06:00
2022-11-01 08:21:35 -06:00
## Fixed
- Registrations via ldap are now compatible with the latest OTP24
2022-11-11 09:12:04 -07:00
## Update notes
- If you use LDAP and run from source, please update your elixir/erlang
to the latest. The changes in OTP24.3 are breaking.
- You can now remove the leading `*.` from domain blocks, but you do not have to.
2022-10-11 04:40:43 -06:00
2022-10-06 10:22:15 -06:00
## 2022.10
### Added
- Ability to sync frontend profiles between clients, with a name attached
- Status card generation will now use the media summary if it is available
2022-09-19 11:31:35 -06:00
### Changed
2022-10-06 10:22:15 -06:00
- Emoji updated to latest 15.0 draft
2022-09-19 11:31:35 -06:00
- **Breaking**: `/api/v1/pleroma/backups` endpoints now requires `read:backups` scope instead of `read:accounts`
2022-10-14 05:49:35 -06:00
- Verify that the signature on posts is not domain blocked, and belongs to the correct user
2022-09-19 11:31:35 -06:00
2022-09-20 04:36:21 -06:00
### Fixed
2022-10-06 10:22:15 -06:00
- OAuthPlug no longer joins with the database every call and uses the user cache
- Undo activities no longer try to look up by ID, and render correctly
2022-09-20 04:36:21 -06:00
- prevent false-errors from meilisearch
2022-09-10 08:44:17 -06:00
## 2022.09
2022-07-19 10:22:02 -06:00
2022-08-16 18:22:59 -06:00
### Added
- support for fedibird-fe, and non-breaking API parity for it to function
2022-08-25 10:11:21 -06:00
- support for setting instance languages in metadata
- support for reusing oauth tokens, and not requiring new authorizations
2022-08-27 04:57:57 -06:00
- the ability to obfuscate domains in your MRF descriptions
2022-08-29 13:42:22 -06:00
- automatic translation of statuses via DeepL or LibreTranslate
2022-09-06 13:24:02 -06:00
- ability to edit posts
2022-09-10 08:44:17 -06:00
- ability to react with remote emoji
2022-08-16 18:22:59 -06:00
2022-08-17 21:23:07 -06:00
### Changed
- MFM parsing is now done on the backend by a modified version of ilja's parser -> https://akkoma.dev/AkkomaGang/mfm-parser
2022-09-10 08:44:17 -06:00
- InlineQuotePolicy is now on by default
2022-09-17 21:21:05 -06:00
- Enable remote users to interact with posts
2022-08-17 21:23:07 -06:00
2022-08-16 16:56:49 -06:00
### Fixed
- Compatibility with latest meilisearch
- Resolution of nested mix tasks (i.e search.meilisearch) in OTP releases
2022-08-16 17:24:19 -06:00
- Elasticsearch returning likes and repeats, displaying as posts
2022-08-24 08:38:02 -06:00
- Ensure key generation happens at registration-time to prevent potential race-conditions
2022-08-27 12:12:15 -06:00
- Ensured websockets get closed on logout
- Allowed GoToSocial-style `?query_string` signatures
2022-08-16 16:56:49 -06:00
2022-08-14 17:13:49 -06:00
### Removed
- Non-finch HTTP adapters. `:tesla, :adapter` is now highly recommended to be set to the default.
## 2022.08
2022-07-24 10:42:43 -06:00
### Added
- extended runtime module support, see config cheatsheet
2022-07-25 10:30:06 -06:00
- quote posting; quotes are limited to public posts
2022-07-24 10:42:43 -06:00
2022-07-26 05:09:13 -06:00
### Changed
- quarantining is now considered absolutely; public activities are no longer
an exception.
2022-08-02 08:19:24 -06:00
- also merged quarantine and mrf reject - quarantine is now deprecated
2022-07-28 04:36:51 -06:00
- flavours:
- amd64 is built for debian stable. Compatible with ubuntu 20.
- ubuntu-jammy is built for... well, ubuntu 22 (LTS)
- amd64-musl is built for alpine 3.16
2022-07-26 05:09:13 -06:00
2022-07-20 14:13:50 -06:00
### Fixed
- Updated mastoFE path, for the newer version
2022-07-19 10:22:02 -06:00
### Removed
- Scrobbling support
2022-07-20 06:00:58 -06:00
- `/api/v1/pleroma/scrobble`
- `/api/v1/pleroma/accounts/{id}/scrobbles`
- Deprecated endpoints
- `/api/v1/pleroma/chats`
- `/api/v1/notifications/dismiss`
- `/api/v1/search`
- `/api/v1/statuses/{id}/card`
2022-07-21 04:29:28 -06:00
- Chats, they were half-baked. Just use PMs.
2022-07-21 05:32:17 -06:00
- Prometheus, it causes massive slowdown
2022-07-19 10:22:02 -06:00
2022-07-15 09:31:28 -06:00
## 2022.07
2022-06-21 01:35:05 -06:00
2022-07-04 10:29:39 -06:00
### Added
- Added move account API
2022-07-06 14:00:43 -06:00
- Added ability to set instance accent-color via theme-color
2022-07-08 07:03:18 -06:00
- A fallback page for when a user does not have a frontend installed
2022-07-14 04:59:21 -06:00
- Support for OTP musl11
2022-07-04 10:29:39 -06:00
2022-06-27 05:32:06 -06:00
### Removed
- SSH frontend, to be potentially re-enabled via a bridge rather than wired into the main system
2022-06-27 10:31:16 -06:00
- Gopher frontend, as above
2022-07-08 07:03:18 -06:00
- All pre-compiled javascript
2022-06-27 05:32:06 -06:00
2022-07-06 12:57:00 -06:00
### Fixed
- ES8 support for bulk indexing activities
2022-07-08 07:03:18 -06:00
### Upgrade Notes
- The bundled frontend has been removed, you will need to run the `pleroma.frontend install` mix task to install your frontend of choice. Configuration by default is set to `pleroma-fe` .
2022-07-15 06:27:16 -06:00
- Admin-FE users will have to ensure that :admin is set _BEFORE_ restart, or
you might end up in a situation where you don't have an ability to get it.
2022-07-08 07:03:18 -06:00
2022-06-21 01:35:05 -06:00
## 2.5.2
### Added
- Allow posting and recieving of misskey markdown (requires text/x.misskeymarkdown in `allowed_post_formats` )
### Changed
- Set frontend URLs to akkoma-maintained ones
### Fixed
- Updated `no_empty` MRF to not error when recieving misskey markdown
2022-06-22 10:10:55 -06:00
### Security
- Ensure local-only statuses do not get leaked
2022-06-21 01:35:05 -06:00
## 2.5.1
### Added
- Elasticsearch Search provider support
- Enabled custom emoji reactions to posts via `/api/v1/pleroma/statuses/:id/reactions/:shortcode:`
- Added continuous integration builds for x86 glibc and musl
### Fixed
- Enabled support for non-standard AP entities, such as those used by bookwyrm
2022-06-12 06:35:14 -06:00
## 2.5.0 - 10/06/2022
2020-09-07 10:22:56 -06:00
2021-04-01 09:09:32 -06:00
### Changed
2021-09-05 18:56:16 -06:00
- Allow users to remove their emails if instance does not need email to register
2021-04-01 09:09:32 -06:00
2021-07-31 23:41:24 -06:00
### Added
2021-11-16 16:39:10 -07:00
- `activeMonth` and `activeHalfyear` fields in NodeInfo usage.users object
2021-12-26 09:00:09 -07:00
- 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.
2021-12-26 16:27:48 -07:00
- 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
2021-12-28 14:11:38 -07:00
- 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.
2022-06-12 06:35:14 -06:00
- Readded mastoFE
- Added support for custom emoji reactions
- Added `emoji_url` in notifications to allow for custom emoji rendering
2022-03-02 07:51:46 -07:00
- 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.
2021-07-31 23:41:24 -06:00
### Fixed
2021-08-11 11:45:49 -06:00
- Subscription(Bell) Notifications: Don't create from Pipeline Ingested replies
2021-12-17 14:47:48 -07:00
- Handle Reject for already-accepted Follows properly
2021-12-25 18:57:53 -07:00
- Display OpenGraph data on alternative notice routes.
2021-12-28 14:11:38 -07:00
- Fix replies count for remote replies
- 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
2021-07-31 23:41:24 -06:00
### Removed
2022-06-22 09:25:05 -06:00
### 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
2021-08-09 03:03:58 -06:00
2021-04-01 09:09:32 -06:00
### Changed
2021-08-15 11:49:12 -06:00
- Make `mix pleroma.database set_text_search_config` run concurrently and indefinitely
2021-04-01 09:09:32 -06:00
2021-08-14 10:08:39 -06:00
### Added
- AdminAPI: Missing configuration description for StealEmojiPolicy
2021-08-09 03:03:58 -06:00
### Fixed
- MastodonAPI: Stream out Create activities
2021-08-09 23:41:06 -06:00
- MRF ObjectAgePolicy: Fix pattern matching on "published"
2021-08-10 12:33:00 -06:00
- TwitterAPI: Make `change_password` and `change_email` require params on body instead of query
2021-08-11 11:45:49 -06:00
- Subscription(Bell) Notifications: Don't create from Pipeline Ingested replies
2021-08-11 08:38:16 -06:00
- AdminAPI: Fix rendering reports containing a `nil` object
2021-08-12 02:29:53 -06:00
- Mastodon API: Activity Search fallbacks on status fetching after a DB Timeout/Error
2021-08-13 09:25:42 -06:00
- Mastodon API: Fix crash in Streamer related to reblogging
2021-08-14 12:42:12 -06:00
- AdminAPI: List available frontends when `static/frontends` folder is missing
2021-08-27 19:43:50 -06:00
- Make activity search properly use language-aware GIN indexes
2021-08-14 05:42:32 -06:00
- AdminAPI: Fix suggestions for MRF Policies
2021-08-12 02:29:53 -06:00
2021-08-09 03:03:58 -06:00
## 2.4.0 - 2021-08-08
2021-07-31 23:41:24 -06:00
2021-04-01 09:09:32 -06:00
### Changed
2020-08-04 09:42:52 -06:00
- **Breaking:** Configuration: `:chat, enabled` moved to `:shout, enabled` and `:instance, chat_limit` moved to `:shout, limit`
2021-01-16 16:06:04 -07:00
- **Breaking** Entries for simple_policy, transparency_exclusions and quarantined_instances now list both the instance and a reason.
2021-06-04 14:50:10 -06:00
- Support for Erlang/OTP 24
2021-03-03 07:35:25 -07:00
- 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.
2021-04-19 16:06:19 -06:00
- HTTPSecurityPlug now sends a response header to opt out of Google's FLoC (Federated Learning of Cohorts) targeted advertising.
2021-05-20 11:50:43 -06:00
- 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.
2021-06-09 10:56:54 -06:00
- Improved Twittercard and OpenGraph meta tag generation including thumbnails and image dimension metadata when available.
2021-07-13 20:44:42 -06:00
- AdminAPI: sort users so the newest are at the top.
2020-09-18 06:22:27 -06:00
- ActivityPub Client-to-Server(C2S): Limitation on the type of Activity/Object are lifted as they are now passed through ObjectValidators
2022-05-08 12:10:40 -06:00
- MRF (`AntiFollowbotPolicy`): Bot accounts are now also considered followbots. Users can still allow bots to follow them by first following the bot.
2021-03-03 07:35:25 -07:00
2021-04-01 09:09:32 -06:00
### 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.
2021-04-29 11:20:46 -06:00
- Return OAuth token `id` (primary key) in POST `/oauth/token` .
2021-07-14 08:03:20 -06:00
- AdminAPI: return `created_at` date with users.
2021-07-17 14:05:20 -06:00
- AdminAPI: add DELETE `/api/v1/pleroma/admin/instances/:instance` to delete all content from a remote instance.
2021-06-08 11:56:03 -06:00
- `AnalyzeMetadata` upload filter for extracting image/video attachment dimensions and generating blurhashes for images. Blurhashes for videos are not generated at this time.
2021-05-18 15:46:51 -06:00
- Attachment dimensions and blurhashes are federated when available.
2021-07-17 19:57:00 -06:00
- Mastodon API: support `poll` notification.
2021-05-27 11:20:21 -06:00
- Pinned posts federation
2022-08-02 07:54:22 -06:00
- Possibility to discover users like `user@example.org` , while Akkoma is working on `akkoma.example.org` . Additional configuration required.
2021-04-01 09:09:32 -06:00
2021-05-03 13:30:21 -06:00
### Fixed
- Don't crash so hard when email settings are invalid.
2021-05-18 15:28:21 -06:00
- Checking activated Upload Filters for required commands.
2021-06-30 11:25:20 -06:00
- Remote users can no longer reappear after being deleted.
- Deactivated users may now be deleted.
2021-07-12 15:59:54 -06:00
- Deleting an activity with a lot of likes/boosts no longer causes a database timeout.
2021-06-07 14:05:18 -06:00
- Mix task `pleroma.database prune_objects`
2021-07-27 07:30:38 -06:00
- Fixed rendering of JSON errors on ActivityPub endpoints.
2021-07-08 11:33:17 -06:00
- Linkify: Parsing crash with URLs ending in unbalanced closed paren, no path separator, and no query parameters
2021-03-23 10:37:25 -06:00
- Try to save exported ConfigDB settings (migrate_from_db) in the system temp directory if default location is not writable.
2021-04-13 09:52:53 -06:00
- Uploading custom instance thumbnail via AdminAPI/AdminFE generated invalid URL to the image
2021-04-13 13:39:44 -06:00
- Applying ConcurrentLimiter settings via AdminAPI
2021-04-01 09:07:57 -06:00
- User login failures if their `notification_settings` were in a NULL state.
2021-04-22 09:15:05 -06:00
- Mix task `pleroma.user delete_activities` query transaction timeout is now :infinity
2021-04-02 11:18:35 -06:00
- 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.
2021-05-01 10:28:06 -06:00
- Fixed some Markdown issues, including trailing slash in links.
2021-03-23 10:37:25 -06:00
2021-07-31 23:41:24 -06:00
### Removed
- **Breaking**: Remove deprecated `/api/qvitter/statuses/notifications/read` (replaced by `/api/v1/pleroma/notifications/read` )
2021-08-06 00:41:58 -06:00
## [2.3.0] - 2021-03-01
2020-09-07 10:22:56 -06:00
2021-02-22 15:19:08 -07:00
### Security
- Fixed client user agent leaking through MediaProxy
2021-02-17 10:47:38 -07:00
### Removed
- `:auth, :enforce_oauth_admin_scope_usage` configuration option.
2020-11-17 05:10:58 -07:00
### Changed
2021-01-25 09:05:38 -07:00
- **Breaking**: Changed `mix pleroma.user toggle_confirmed` to `mix pleroma.user confirm`
2021-01-25 09:36:51 -07:00
- **Breaking**: Changed `mix pleroma.user toggle_activated` to `mix pleroma.user activate/deactivate`
2020-12-28 15:21:53 -07:00
- **Breaking:** NSFW hashtag is no longer added on sensitive posts
2020-11-17 05:21:46 -07:00
- Polls now always return a `voters_count` , even if they are single-choice.
2020-11-17 05:10:58 -07:00
- Admin Emails: The ap id is used as the user link in emails now.
2020-11-21 09:24:45 -07:00
- Improved registration workflow for email confirmation and account approval modes.
2020-11-20 08:28:00 -07:00
- Search: When using Postgres 11+, Pleroma will use the `websearch_to_tsvector` function to parse search queries.
2020-12-03 08:18:35 -07:00
- Emoji: Support the full Unicode 13.1 set of Emoji for reactions, plus regional indicators.
2021-01-12 15:40:29 -07:00
- Deprecated `Pleroma.Uploaders.S3, :public_endpoint` . Now `Pleroma.Upload, :base_url` is the standard configuration key for all uploaders.
2021-01-25 17:23:05 -07:00
- Improved Apache webserver support: updated sample configuration, MediaProxy cache invalidation verified with the included sample script
2021-02-02 11:12:37 -07:00
- Improve OAuth 2.0 provider support. A missing `fqn` field was added to the response, but does not expose the user's email address.
2021-02-03 09:53:09 -07:00
- Provide redirect of external posts from `/notice/:id` to their original URL
2021-02-03 13:52:49 -07:00
- Admins no longer receive notifications for reports if they are the actor making the report.
2021-02-06 12:20:58 -07:00
- Improved Mailer configuration setting descriptions for AdminFE.
2021-02-15 06:52:36 -07:00
- Updated default avatar to look nicer.
2020-11-17 05:10:58 -07:00
2021-01-21 08:51:21 -07:00
< 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.
2021-01-21 09:17:37 -07:00
- **Breaking:** AdminAPI `GET /api/pleroma/admin/instances/:instance/statuses` changed response format and added the number of total users posts.
2021-01-21 08:51:21 -07:00
- Admin API: Reports now ordered by newest
2021-02-17 05:58:33 -07:00
- Pleroma API: `GET /api/v1/pleroma/chats` is deprecated in favor of `GET /api/v2/pleroma/chats` .
2021-02-18 14:59:06 -07:00
- Pleroma API: Reroute `/api/pleroma/*` to `/api/v1/pleroma/*`
2021-01-21 08:51:21 -07:00
< / details >
2021-03-23 10:37:25 -06:00
- Improved hashtag timeline performance (requires a background migration).
2020-11-17 05:10:58 -07:00
2020-09-09 08:10:44 -06:00
### Added
2020-11-17 05:10:58 -07:00
2020-11-13 06:35:46 -07:00
- Reports now generate notifications for admins and mods.
2020-12-13 05:47:43 -07:00
- Support for local-only statuses.
2020-11-17 05:21:46 -07:00
- Support pagination of blocks and mutes.
- Account backup.
2020-10-27 11:42:24 -06:00
- Configuration: Add `:instance, autofollowing_nicknames` setting to provide a way to make accounts automatically follow new users that register on the local Pleroma instance.
2020-10-10 02:44:20 -06:00
- `[:activitypub, :blockers_visible]` config to control visibility of blockers.
2020-11-17 05:21:46 -07:00
- Ability to view remote timelines, with ex. `/api/v1/timelines/public?instance=lain.com` and streams `public:remote` and `public:remote:media` .
2020-11-11 09:19:09 -07:00
- The site title is now injected as a `title` tag like preloads or metadata.
2020-11-19 04:29:41 -07:00
- Password reset tokens now are not accepted after a certain age.
2020-12-13 05:47:43 -07:00
- Mix tasks to help with displaying and removing ConfigDB entries. See `mix pleroma.config` .
2020-11-28 11:51:06 -07:00
- OAuth form improvements: users are remembered by their cookie, the CSS is overridable by the admin, and the style has been improved.
2020-12-12 12:21:59 -07:00
- 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.
2020-10-08 14:46:03 -06:00
- Ability to set ActivityPub aliases for follower migration.
2021-01-21 00:12:01 -07:00
- Configurable background job limits for RichMedia (link previews) and MediaProxyWarmingPolicy
2021-01-21 04:58:18 -07:00
- Ability to define custom HTTP headers per each frontend
2021-02-08 14:32:47 -07:00
- MRF (`NoEmptyPolicy`): New MRF Policy which will deny empty statuses or statuses of only mentions from being created by local users
2021-02-04 15:14:37 -07:00
- New users will receive a simple email confirming their registration if no other emails will be dispatched. (e.g., Welcome, Confirmation, or Approval Required)
2020-09-09 08:10:44 -06:00
2020-11-17 05:10:58 -07:00
< details >
< summary > API Changes< / summary >
- Admin API: (`GET /api/pleroma/admin/users`) filter users by `unconfirmed` status and `actor_type` .
2021-03-02 09:49:17 -07:00
- Admin API: OpenAPI spec for the user-related operations
2021-02-17 05:58:33 -07:00
- Pleroma API: `GET /api/v2/pleroma/chats` added. It is exactly like `GET /api/v1/pleroma/chats` except supports pagination.
2020-11-17 05:10:58 -07:00
- 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.
2020-12-13 05:47:43 -07:00
- Admin API: An endpoint to manage frontends.
- Streaming API: Add follow relationships updates.
2021-01-28 22:41:21 -07:00
- WebPush: Introduce `pleroma:chat_mention` and `pleroma:emoji_reaction` notification types.
2021-02-02 10:11:38 -07:00
- Mastodon API: Add monthly active users to `/api/v1/instance` (`pleroma.stats.mau`).
2021-02-01 04:09:23 -07:00
- Mastodon API: Home, public, hashtag & list timelines accept `only_media` , `remote` & `local` parameters for filtration.
2021-01-28 22:41:21 -07:00
- Mastodon API: `/api/v1/accounts/:id` & `/api/v1/mutes` endpoints accept `with_relationships` parameter and return filled `pleroma.relationship` field.
2021-02-15 10:48:13 -07:00
- Mastodon API: Endpoint to remove a conversation (`DELETE /api/v1/conversations/:id`).
2021-02-11 03:01:48 -07:00
- Mastodon API: `expires_in` in the scheduled post `params` field on `/api/v1/statuses` and `/api/v1/scheduled_statuses/:id` endpoints.
2020-11-17 05:10:58 -07:00
< / details >
### Fixed
2020-11-19 09:30:02 -07:00
- 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.).
2020-12-13 05:47:43 -07:00
- Streaming API: Posts and notifications are not dropped, when CLI task is executing.
2020-12-23 08:03:16 -07:00
- Creating incorrect IPv4 address-style HTTP links when encountering certain numbers.
2021-01-19 06:57:00 -07:00
- 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.
2021-01-21 15:49:19 -07:00
- Tag URLs in statuses are now absolute
2021-02-02 10:15:47 -07:00
- Removed duplicate jobs to purge expired activities
2021-02-02 11:03:20 -07:00
- File extensions of some attachments were incorrectly changed. This feature has been disabled for now.
2021-02-02 11:16:01 -07:00
- Mix task pleroma.instance creates missing parent directories if the configuration or SQL output paths are changed.
2020-11-19 09:30:02 -07:00
2020-11-17 05:10:58 -07:00
< details >
< summary > API Changes< / summary >
2020-11-19 09:13:19 -07:00
- 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.
2021-01-18 08:29:29 -07:00
- Mastodon API: Fix not being able to add or remove multiple users at once in lists.
2021-01-22 08:47:59 -07:00
- Mastodon API: Fixed own_votes being not returned with poll data.
2021-02-01 08:22:26 -07:00
- Mastodon API: Fixed creation of scheduled posts with polls.
2021-01-25 05:34:59 -07:00
- Mastodon API: Support for expires_in/expires_at in the Filters.
2020-11-17 05:10:58 -07:00
< / details >
2021-08-06 00:41:58 -06:00
## [2.2.2] - 2021-01-18
2021-01-08 06:10:49 -07:00
2020-12-23 06:56:57 -07:00
### Fixed
2020-12-25 01:53:01 -07:00
- StealEmojiPolicy creates dir for emojis, if it doesn't exist.
2021-01-18 06:20:36 -07:00
- Updated `elixir_make` to a non-retired version
### Upgrade notes
1. Restart Pleroma
2020-12-23 06:56:57 -07:00
## [2.2.1] - 2020-12-22
2020-11-17 13:21:48 -07:00
### Changed
2020-12-23 06:56:57 -07:00
- Updated Pleroma FE
2020-11-17 13:21:48 -07:00
2020-11-17 05:10:58 -07:00
### Fixed
2020-11-17 05:21:46 -07:00
- Config generation: rename `Pleroma.Upload.Filter.ExifTool` to `Pleroma.Upload.Filter.Exiftool` .
2020-11-17 05:20:57 -07:00
- S3 Uploads with Elixir 1.11.
2020-11-17 08:28:46 -07:00
- Mix task pleroma.user delete_activities for source installations.
2020-12-23 06:56:57 -07:00
- Search: RUM index search speed has been fixed.
2020-12-12 12:21:59 -07:00
- Rich Media Previews sometimes showed the wrong preview due to a bug following redirects.
2020-12-23 06:56:57 -07:00
- Fixes for the autolinker.
- Forwarded reports duplication from Pleroma instances.
2021-01-17 05:55:33 -07:00
- Emoji Reaction activity filtering from blocked and muted accounts.
2020-11-17 10:03:28 -07:00
2020-12-23 06:56:57 -07:00
- < details >
< summary > API< / summary >
- Statuses were not displayed for Mastodon forwarded reports.
< / details >
2020-11-17 10:03:28 -07:00
2020-12-23 06:56:57 -07:00
### Upgrade notes
1. Restart Pleroma
2020-11-17 05:10:58 -07:00
2020-11-11 13:12:52 -07:00
## [2.2.0] - 2020-11-12
2020-11-05 06:33:51 -07:00
### Security
2020-11-17 05:10:58 -07:00
2020-11-05 06:33:51 -07:00
- Fixed the possibility of using file uploads to spoof posts.
2020-09-09 08:10:44 -06:00
2020-09-07 10:55:14 -06:00
### Changed
2020-09-08 05:35:34 -06:00
2020-09-10 15:02:11 -06:00
- **Breaking** Requires `libmagic` (or `file` ) to guess file types.
2020-11-17 05:10:58 -07:00
- **Breaking:** App metrics endpoint (`/api/pleroma/app_metrics`) is disabled by default, check `docs/API/prometheus.md` on enabling and configuring.
2020-10-05 11:40:53 -06:00
- **Breaking:** Pleroma Admin API: emoji packs and files routes changed.
2020-10-06 13:54:21 -06:00
- **Breaking:** Sensitive/NSFW statuses no longer disable link previews.
2020-09-24 07:56:17 -06:00
- Search: Users are now findable by their urls.
2020-09-08 03:23:08 -06:00
- 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.
2020-09-17 07:48:17 -06:00
- The `discoverable` field in the `User` struct will now add a NOINDEX metatag to profile pages when false.
2020-11-19 09:30:02 -07:00
- Users with the `is_discoverable` field set to false will not show up in searches ([bug](https://git.pleroma.social/pleroma/pleroma/-/issues/2301)).
2020-09-14 11:07:31 -06:00
- Minimum lifetime for ephmeral activities changed to 10 minutes and made configurable (`:min_lifetime` option).
2020-09-29 08:34:49 -06:00
- Introduced optional dependencies on `ffmpeg` , `ImageMagick` , `exiftool` software packages. Please refer to `docs/installation/optional/media_graphics_packages.md` .
2020-11-11 13:12:52 -07:00
- < details >
2020-09-24 00:54:10 -06:00
< summary > API Changes< / summary >
2020-11-11 13:12:52 -07:00
- API: Empty parameter values for integer parameters are now ignored in non-strict validaton mode.
2020-09-24 00:54:10 -06:00
< / details >
2020-09-16 13:30:42 -06:00
2020-09-07 10:22:56 -06:00
### Removed
2020-09-10 12:53:58 -06:00
- **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).
2020-09-10 06:00:19 -06:00
- 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.
2020-09-17 22:09:53 -06:00
2020-09-16 13:30:42 -06:00
### Added
2020-11-17 05:10:58 -07:00
2020-09-29 08:30:18 -06:00
- Media preview proxy (requires `ffmpeg` and `ImageMagick` to be installed and media proxy to be enabled; see `:media_preview_proxy` config for more details).
2020-10-27 11:47:56 -06:00
- Mix tasks for controlling user account confirmation status in bulk (`mix pleroma.user confirm_all` and `mix pleroma.user unconfirm_all` )
2020-12-12 07:30:08 -07:00
- Mix task for sending confirmation emails to all unconfirmed users (`mix pleroma.email resend_confirmation_emails`)
2020-10-27 11:47:56 -06:00
- Mix task option for force-unfollowing relays
- App metrics: ability to restrict access to specified IP whitelist.
2020-09-24 00:54:10 -06:00
< details >
< summary > API Changes< / summary >
2020-09-23 02:57:53 -06:00
- Admin API: Importing emoji from a zip file
2020-11-11 13:12:52 -07:00
- Pleroma API: Importing the mutes users from CSV files.
2020-09-24 00:54:10 -06:00
- Pleroma API: Pagination for remote/local packs and emoji.
< / details >
2020-09-16 13:30:42 -06:00
2020-09-22 09:17:19 -06:00
### Fixed
2020-09-23 05:49:19 -06:00
2020-09-22 09:17:19 -06:00
- Add documented-but-missing chat pagination.
2020-09-23 02:54:24 -06:00
- Allow sending out emails again.
2020-10-22 04:56:17 -06:00
- Allow sending chat messages to yourself
2020-10-11 13:34:28 -06:00
- OStatus / static FE endpoints: fixed inaccessibility for anonymous users on non-federating instances, switched to handling per `:restrict_unauthenticated` setting.
2020-10-27 16:44:31 -06:00
- Fix remote users with a whitespace name.
2020-09-17 22:09:53 -06:00
2020-10-15 12:43:46 -06:00
### Upgrade notes
2020-09-29 12:49:04 -06:00
2020-10-15 12:43:46 -06:00
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
2020-09-29 12:49:04 -06:00
2020-09-17 11:40:52 -06:00
## [2.1.2] - 2020-09-17
2020-09-17 06:13:36 -06:00
### Security
2020-09-17 11:40:52 -06:00
- Fix most MRF rules either crashing or not being applied to objects passed into the Common Pipeline (ChatMessage, Question, Answer, Audio, Event).
2020-09-14 16:11:08 -06:00
2020-09-14 11:08:32 -06:00
### Fixed
2020-09-17 11:40:52 -06:00
- 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.
2020-09-08 03:07:33 -06:00
2020-09-17 11:40:52 -06:00
### Changed
2020-09-12 04:05:36 -06:00
2020-09-17 11:40:52 -06:00
- 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
2020-09-12 04:05:36 -06:00
2020-09-17 11:40:52 -06:00
1. Restart Pleroma
2020-09-12 04:05:36 -06:00
2020-09-08 05:21:34 -06:00
## [2.1.1] - 2020-09-08
2020-09-02 00:55:58 -06:00
2020-09-08 03:49:27 -06:00
### Security
2020-09-08 05:21:34 -06:00
- 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.
2020-08-31 15:11:13 -06:00
### 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.
2020-09-08 05:21:34 -06:00
- Improved error message when cmake is not available at build stage.
2020-08-31 13:35:22 -06:00
2020-09-02 05:21:28 -06:00
### Added
2020-09-08 05:21:34 -06:00
- Rich media failure tracking (along with `:failure_backoff` option).
2020-09-02 05:21:28 -06:00
2020-08-30 06:15:14 -06:00
< 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 >
2020-09-01 11:56:32 -06:00
### Fixed
2020-09-08 05:21:34 -06:00
- Default HTTP adapter not respecting pool setting, leading to possible OOM.
2020-09-08 03:28:38 -06:00
- Fixed uploading webp images when the Exiftool Upload Filter is enabled by skipping them
2020-09-01 11:56:32 -06:00
- Mastodon API: Search parameter `following` now correctly returns the followings rather than the followers
2020-09-02 04:44:08 -06:00
- Mastodon API: Timelines hanging for (`number of posts with links * rich media timeout`) in the worst case.
Reduced to just rich media timeout.
2020-09-08 05:21:34 -06:00
- 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.
2020-09-01 11:56:32 -06:00
2020-08-25 07:16:20 -06:00
## [2.1.0] - 2020-08-28
2020-03-28 12:21:23 -06:00
### Changed
2020-08-18 23:55:03 -06:00
2020-08-18 05:24:39 -06:00
- **Breaking:** The default descriptions on uploads are now empty. The old behavior (filename as default) can be configured, see the cheat sheet.
2020-08-07 08:20:13 -06:00
- **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.
2020-06-16 17:29:32 -06:00
- **Breaking:** Elixir >=1.9 is now required (was >= 1.8)
2020-07-21 16:18:17 -06:00
- **Breaking:** Configuration: `:auto_linker, :opts` moved to `:pleroma, Pleroma.Formatter` . Old config namespace is deprecated.
2020-08-18 23:55:03 -06:00
- **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` .
2020-06-15 04:30:11 -06:00
- In Conversations, return only direct messages as `last_status`
2020-06-16 05:09:28 -06:00
- Using the `only_media` filter on timelines will now exclude reblog media
2020-06-01 05:48:51 -06:00
- MFR policy to set global expiration for all local Create activities
2020-06-11 07:57:31 -06:00
- OGP rich media parser merged with TwitterCard
2020-06-17 01:47:20 -06:00
- 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.
2020-07-11 01:36:36 -06:00
- Configuration: `:media_proxy, whitelist` format changed to host with scheme (e.g. `http://example.com` instead of `example.com` ). Domain format is deprecated.
2020-03-21 00:47:05 -06:00
2020-03-28 12:21:23 -06:00
< details >
< summary > API Changes< / summary >
2020-05-09 05:32:08 -06:00
2020-07-07 08:51:44 -06:00
- **Breaking:** Pleroma API: The routes to update avatar, banner and background have been removed.
2020-07-06 03:18:01 -06:00
- **Breaking:** Image description length is limited now.
2020-03-28 12:21:23 -06:00
- **Breaking:** Emoji API: changed methods and renamed routes.
2020-08-18 23:55:03 -06:00
- **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` .
2020-07-07 08:51:44 -06:00
- MastodonAPI: Allow removal of avatar, banner and background.
2020-07-02 01:54:48 -06:00
- Streaming: Repeats of a user's posts will no longer be pushed to the user's stream.
2020-07-02 12:01:22 -06:00
- Mastodon API: Added `pleroma.metadata.fields_limits` to /api/v1/instance
2020-07-03 08:46:11 -06:00
- Mastodon API: On deletion, returns the original post text.
2019-11-25 08:59:55 -07:00
- Mastodon API: Add `pleroma.unread_count` to the Marker entity.
2020-07-17 09:45:41 -06:00
- Mastodon API: Added `pleroma.metadata.post_formats` to /api/v1/instance
2020-07-23 11:59:40 -06:00
- Mastodon API (legacy): Allow query parameters for `/api/v1/domain_blocks` , e.g. `/api/v1/domain_blocks?domain=badposters.zone`
2020-08-16 16:07:23 -06:00
- Mastodon API: Make notifications about statuses from muted users and threads read automatically
2020-07-30 02:00:07 -06:00
- Pleroma API: `/api/pleroma/captcha` responses now include `seconds_valid` with an integer value.
2020-08-18 23:55:03 -06:00
2020-03-28 12:21:23 -06:00
< / details >
2020-05-09 05:32:08 -06:00
< details >
< summary > Admin API Changes< / summary >
2020-08-18 23:55:03 -06:00
- **Breaking** Changed relay `/api/pleroma/admin/relay` endpoints response format.
2020-05-09 05:32:08 -06:00
- Status visibility stats: now can return stats per instance.
- Mix task to refresh counter cache (`mix pleroma.refresh_counter_cache`)
2020-08-18 23:55:03 -06:00
2020-05-09 05:32:08 -06:00
< / details >
2020-03-16 11:05:21 -06:00
### Removed
2020-08-18 23:55:03 -06:00
2020-03-16 11:05:21 -06:00
- **Breaking:** removed `with_move` parameter from notifications timeline.
2020-03-18 08:37:54 -06:00
### Added
2020-06-19 03:31:55 -06:00
2020-08-03 10:23:26 -06:00
- Frontends: Add mix task to install frontends.
2020-07-29 05:09:42 -06:00
- Frontends: Add configurable frontends for primary and admin fe.
2020-08-04 04:49:56 -06:00
- Configuration: Added a blacklist for email servers.
2020-07-03 07:59:42 -06:00
- Chats: Added `accepts_chat_messages` field to user, exposed in APIs and federation.
2020-06-03 11:25:57 -06:00
- Chats: Added support for federated chats. For details, see the docs.
2020-05-22 09:13:09 -06:00
- ActivityPub: Added support for existing AP ids for instances migrated from Mastodon.
2020-05-20 04:14:17 -06:00
- Instance: Add `background_image` to configuration and `/api/v1/instance`
2020-04-27 06:35:12 -06:00
- Instance: Extend `/api/v1/instance` with Pleroma-specific information.
2020-03-18 08:37:54 -06:00
- NodeInfo: `pleroma:api/v1/notifications:include_types_filter` to the `features` list.
2020-03-31 09:22:25 -06:00
- NodeInfo: `pleroma_emoji_reactions` to the `features` list.
2020-03-20 04:04:37 -06:00
- Configuration: `:restrict_unauthenticated` setting, restrict access for unauthenticated users to timelines (public and federate), user profiles and statuses.
2020-05-14 05:36:49 -06:00
- Configuration: Add `:database_config_whitelist` setting to whitelist settings which can be configured from AdminFE.
2020-05-22 09:30:13 -06:00
- Configuration: `filename_display_max_length` option to set filename truncate limit, if filename display enabled (0 = no limit).
2020-03-30 03:16:45 -06:00
- New HTTP adapter [gun ](https://github.com/ninenines/gun ). Gun adapter requires minimum OTP version of 22.2 otherwise Pleroma won’
2020-04-17 03:33:11 -06:00
- Mix task to create trusted OAuth App.
2020-06-12 07:51:11 -06:00
- Mix task to reset MFA for user accounts
2020-05-01 00:51:41 -06:00
- Notifications: Added `follow_request` notification type.
2020-04-13 12:48:32 -06:00
- Added `:reject_deletes` group to SimplePolicy
2020-04-14 10:59:04 -06:00
- MRF (`EmojiStealPolicy`): New MRF Policy which allows to automatically download emojis from remote instances
2020-06-19 03:31:55 -06:00
- Support pagination in emoji packs API (for packs and for files in pack)
2020-07-07 22:09:39 -06:00
- Support for viewing instances favicons next to posts and accounts
2020-07-10 15:46:26 -06:00
- Added Pleroma.Upload.Filter.Exiftool as an alternate EXIF stripping mechanism targeting GPS/location metadata.
2020-07-14 17:47:23 -06:00
- "By approval" registrations mode.
2020-08-02 07:54:59 -06:00
- 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.
2020-07-29 11:45:32 -06:00
- Ability to hide favourites and emoji reactions in the API with `[:instance, :show_reactions]` config.
2020-06-19 03:31:55 -06:00
2020-03-18 08:37:54 -06:00
< details >
< summary > API Changes< / summary >
2020-07-20 05:41:43 -06:00
- Mastodon API: Add pleroma.parent_visible field to statuses.
2020-04-27 06:35:12 -06:00
- Mastodon API: Extended `/api/v1/instance` .
2020-03-18 08:37:54 -06:00
- Mastodon API: Support for `include_types` in `/api/v1/notifications` .
2020-03-15 15:50:03 -06:00
- Mastodon API: Added `/api/v1/notifications/:id/dismiss` endpoint.
2019-11-25 08:59:55 -07:00
- 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.
2020-07-07 22:09:39 -06:00
- Mastodon API: Add pleroma.favicon field to accounts.
2020-04-17 03:33:11 -06:00
- Admin API: endpoints for create/update/delete OAuth Apps.
2020-05-05 07:08:44 -06:00
- Admin API: endpoint for status view.
2020-06-12 07:42:23 -06:00
- OTP: Add command to reload emoji packs
2020-03-18 08:37:54 -06:00
< / details >
2020-03-24 10:18:27 -06:00
### Fixed
2020-08-26 07:40:00 -06:00
- Fix list pagination and other list issues.
2020-03-24 10:18:27 -06:00
- Support pagination in conversations API
2020-04-13 12:48:32 -06:00
- **Breaking**: SimplePolicy `:reject` and `:accept` allow deletions again
2020-04-22 09:31:03 -06:00
- Fix follower/blocks import when nicknames starts with @
2020-04-11 07:01:09 -06:00
- Filtering of push notifications on activities from blocked domains
2020-05-04 04:22:31 -06:00
- Resolving Peertube accounts with Webfinger
2020-05-29 09:33:31 -06:00
- `blob:` urls not being allowed by connect-src CSP
2020-05-18 09:46:04 -06:00
- Mastodon API: fix `GET /api/v1/notifications` not returning the full result set
2020-07-07 10:21:05 -06:00
- Rich Media Previews for Twitter links
2020-05-18 13:56:09 -06:00
- 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`
2020-07-03 16:19:43 -06:00
- Fix CSP policy generation to include remote Captcha services
2020-07-10 10:22:29 -06:00
- Fix edge case where MediaProxy truncates media, usually caused when Caddy is serving content for the other Federated instance.
2020-07-21 16:29:11 -06:00
- Emoji Packs could not be listed when instance was set to `public: false`
2020-08-05 14:39:11 -06:00
- Fix whole_word always returning false on filter get requests
2020-08-17 01:58:24 -06:00
- Migrations not working on OTP releases if the database was connected over ssl
2020-08-18 23:40:26 -06:00
- Fix relay following
2020-03-24 10:18:27 -06:00
2020-06-12 12:09:40 -06:00
## [2.0.7] - 2020-06-13
### Security
2020-06-12 14:06:49 -06:00
- Fix potential DoSes exploiting atom leaks in rich media parser and the `UserAllowListPolicy` MRF policy
2020-06-12 12:09:40 -06:00
### 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
2020-06-07 16:33:43 -06:00
## [2.0.6] - 2020-06-09
### Security
- CSP: harden `image-src` and `media-src` when MediaProxy is used
2020-05-08 14:54:16 -06:00
2020-05-08 14:51:59 -06:00
### Fixed
2020-06-07 16:33:43 -06:00
- AP C2S: Fix pagination in inbox/outbox
- Various compilation errors on OTP 23
- Mastodon API streaming: Repeats from muted threads not being filtered
2020-03-24 10:18:27 -06:00
2020-06-07 16:33:43 -06:00
### 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
2020-05-12 15:08:07 -06:00
## [2.0.5] - 2020-05-13
### Security
- Fix possible private status leaks in Mastodon Streaming API
2020-05-08 14:54:16 -06:00
2020-05-08 14:51:59 -06:00
### Fixed
2020-05-12 15:08:07 -06:00
- 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
2020-05-09 17:36:32 -06:00
## [2.0.4] - 2020-05-10
2020-05-10 10:54:37 -06:00
### Security
- AP C2S: Fix a potential DoS by creating nonsensical objects that break timelines
2020-05-09 17:36:32 -06:00
### Fixed
- Peertube user lookups not working
- `InsertSkeletonsForDeletedUsers` migration failing on some instances
2020-05-08 14:51:59 -06:00
- Healthcheck reporting the number of memory currently used, rather than allocated in total
2020-05-09 17:36:32 -06:00
- 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
2020-05-08 14:51:59 -06:00
2020-05-08 14:54:16 -06:00
## [2.0.3] - 2020-05-02
2020-04-30 15:28:28 -06:00
### Security
2020-04-30 15:33:04 -06:00
- Disallow re-registration of previously deleted users, which allowed viewing direct messages addressed to them
2020-04-30 15:28:28 -06:00
- 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
2020-05-08 14:54:16 -06:00
- CSP: Sandbox uploads
2020-04-30 15:28:28 -06:00
2020-04-12 23:59:06 -06:00
### Fixed
2020-05-08 14:54:16 -06:00
- Notifications from blocked domains
- Potential federation issues with Mastodon versions before 3.0.0
2020-04-17 12:21:10 -06:00
- HTTP Basic Authentication permissions issue
2020-05-08 14:54:16 -06:00
- 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
2020-04-20 06:59:16 -06:00
- ObjectAgePolicy didn't filter out old messages
2020-05-08 14:54:16 -06:00
- `blob:` urls not being allowed by CSP
2020-04-10 10:37:02 -06:00
2020-04-13 05:07:23 -06:00
### Added
2020-04-20 06:59:16 -06:00
- NodeInfo: ObjectAgePolicy settings to the `federation` list.
2020-05-08 14:54:16 -06:00
- Follow request notifications
2020-04-13 05:07:23 -06:00
< details >
< summary > API Changes< / summary >
- Admin API: `GET /api/pleroma/admin/need_reboot` .
< / details >
2020-04-10 10:37:02 -06:00
2020-05-08 14:54:16 -06:00
### Upgrade notes
1. Restart Pleroma
2. Run database migrations (inside Pleroma directory):
- OTP: `./bin/pleroma_ctl migrate`
- From Source: `mix ecto.migrate`
2020-05-09 05:32:08 -06:00
3. Reset status visibility counters (inside Pleroma directory):
- OTP: `./bin/pleroma_ctl refresh_counter_cache`
- From Source: `mix pleroma.refresh_counter_cache`
2020-05-08 14:54:16 -06:00
2020-04-07 15:39:55 -06:00
## [2.0.2] - 2020-04-08
2020-04-02 14:37:14 -06:00
### Added
- Support for Funkwhale's `Audio` activity
- Admin API: `PATCH /api/pleroma/admin/users/:nickname/update_credentials`
2020-03-31 04:59:26 -06:00
### 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
2020-04-02 14:37:14 -06:00
- Incorrect URL for Funkwhale channels
2020-03-31 04:59:26 -06:00
2020-04-07 15:38:48 -06:00
### Upgrade notes
1. Restart Pleroma
2020-03-15 08:26:58 -06:00
## [2.0.1] - 2020-03-15
2020-03-31 04:59:26 -06:00
### Security
- Static-FE: Fix remote posts not being sanitized
2020-03-15 08:26:58 -06:00
### Fixed
2020-03-15 15:18:16 -06:00
- Rate limiter crashes when there is no explicitly specified ip in the config
2020-03-15 08:26:58 -06:00
- 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
2020-02-12 19:39:47 -07:00
### Changed
2020-03-15 08:26:58 -06:00
- 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
2020-02-12 19:39:47 -07:00
2020-03-15 15:50:03 -06:00
### Upgrade notes
#### Nginx only
1. Remove `proxy_ignore_headers Cache-Control;` and `proxy_hide_header Cache-Control;` from your config.
2020-03-16 11:05:21 -06:00
2020-03-15 15:50:03 -06:00
#### Everyone
1. Run database migrations (inside Pleroma directory):
- OTP: `./bin/pleroma_ctl migrate`
- From Source: `mix ecto.migrate`
2. Restart Pleroma
2020-03-18 08:37:54 -06:00
2020-03-05 12:35:23 -07:00
## [2.0.0] - 2019-03-08
2020-02-28 07:59:16 -07:00
### Security
2020-04-01 10:49:09 -06:00
- Mastodon API: Fix being able to request enormous amount of statuses in timelines leading to DoS. Now limited to 40 per request.
2020-02-28 07:59:16 -07:00
2019-10-18 06:34:29 -06:00
### Removed
- **Breaking**: Removed 1.0+ deprecated configurations `Pleroma.Upload, :strip_exif` and `:instance, :dedupe_media`
2019-10-17 16:29:28 -06:00
- **Breaking**: OStatus protocol support
2020-01-11 10:19:54 -07:00
- **Breaking**: MDII uploader
2020-01-27 06:21:50 -07:00
- **Breaking**: Using third party engines for user recommendation
2020-02-05 11:28:05 -07:00
< details >
< summary > API Changes< / summary >
2020-07-20 05:41:43 -06:00
2020-02-05 11:28:05 -07:00
- **Breaking**: AdminAPI: migrate_from_db endpoint
< / details >
2019-10-18 06:34:29 -06:00
### Changed
2020-01-16 09:01:31 -07:00
- **Breaking:** Pleroma won't start if it detects unapplied migrations
2019-10-18 06:34:29 -06:00
- **Breaking:** Elixir >=1.8 is now required (was >= 1.7)
2020-01-29 13:58:15 -07:00
- **Breaking:** `Pleroma.Plugs.RemoteIp` and `:rate_limiter` enabled by default. Please ensure your reverse proxy forwards the real IP!
2019-11-10 05:02:47 -07:00
- **Breaking:** attachment links (`config :pleroma, :instance, no_attachment_links` and `config :pleroma, Pleroma.Upload, link_name` ) disabled by default
2020-01-10 00:52:21 -07:00
- **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.
2020-01-24 07:04:25 -07:00
- **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.
2020-02-11 14:39:19 -07:00
- **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.
2019-10-18 06:34:29 -06:00
- 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
2019-11-06 07:19:32 -07:00
- OStatus: Extract RSS functionality
- Deprecated `User.Info` embedded schema (fields moved to `User` )
- Store status data inside Flag activity
2019-11-20 05:57:51 -07:00
- Deprecated (reorganized as `UserRelationship` entity) User fields with user AP IDs (`blocks`, `mutes` , `muted_reblogs` , `muted_notifications` , `subscribers` ).
2019-12-13 09:00:26 -07:00
- Rate limiter is now disabled for localhost/socket (unless remoteip plug is enabled)
2019-12-11 08:32:53 -07:00
- Logger: default log level changed from `warn` to `info` .
2020-01-23 07:23:02 -07:00
- Config mix task `migrate_to_db` truncates `config` table before migrating the config file.
2020-02-26 09:13:53 -07:00
- Allow account registration without an email
2020-02-25 03:51:01 -07:00
- Default to `prepare: :unnamed` in the database configuration.
2020-03-04 12:41:04 -07:00
- Instance stats are now loaded on startup instead of being empty until next hourly job.
2019-10-18 06:34:29 -06:00
< details >
< summary > API Changes< / summary >
2020-02-07 06:59:26 -07:00
- **Breaking** EmojiReactions: Change endpoints and responses to align with Mastodon
2019-11-06 07:19:32 -07:00
- **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)
2019-10-18 06:34:29 -06:00
- **Breaking:** Admin API: Return link alongside with token on password reset
2019-11-11 03:16:04 -07:00
- **Breaking:** Admin API: `PUT /api/pleroma/admin/reports/:id` is now `PATCH /api/pleroma/admin/reports` , see admin_api.md for details
2019-10-18 06:34:29 -06:00
- **Breaking:** `/api/pleroma/admin/users/invite_token` now uses `POST` , changed accepted params and returns full invite in json instead of only token string.
2020-03-28 06:00:48 -06:00
- **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`
2020-01-30 09:47:57 -07:00
- Mastodon API: stopped sanitizing display names, field names and subject fields since they are supposed to be treated as plaintext
2019-10-18 06:34:29 -06:00
- 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
2019-11-19 01:58:20 -07:00
- Admin API: Support authentication via `x-admin-token` HTTP header
2019-10-18 06:34:29 -06:00
- 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
2019-10-30 18:44:27 -06:00
- Mastodon API, streaming: Add `pleroma.direct_conversation_id` to the `conversation` stream event payload.
2019-11-24 08:04:29 -07:00
- Admin API: Render whole status in grouped reports
2019-12-09 06:43:57 -07:00
- Mastodon API: User timelines will now respect blocks, unless you are getting the user timeline of somebody you blocked (which would be empty otherwise).
2020-01-20 08:31:12 -07:00
- 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.
2020-02-28 07:59:16 -07:00
- Mastodon API: Limit timeline requests to 3 per timeline per 500ms per user/ip by default.
2020-01-31 11:07:46 -07:00
- Admin API: `PATCH /api/pleroma/admin/users/:nickname/credentials` and `GET /api/pleroma/admin/users/:nickname/credentials`
2019-10-18 06:34:29 -06:00
< / details >
2019-09-18 15:00:05 -06:00
### Added
2019-12-04 04:49:46 -07:00
- `:chat_limit` option to limit chat characters.
2020-01-30 15:20:37 -07:00
- `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.
2019-09-18 15:00:05 -06:00
- Refreshing poll results for remote polls
2019-10-18 06:34:29 -06:00
- Authentication: Added rate limit for password-authorized actions / login existence checks
2019-11-09 10:50:45 -07:00
- Static Frontend: Add the ability to render user profiles and notices server-side without requiring JS app.
2019-10-18 06:34:29 -06:00
- Mix task to re-count statuses for all users (`mix pleroma.count_statuses`)
2019-11-17 13:58:30 -07:00
- Mix task to list all users (`mix pleroma.user list`)
2020-01-20 05:23:21 -07:00
- Mix task to send a test email (`mix pleroma.email test`)
2019-10-18 06:56:14 -06:00
- 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).
2019-11-15 05:31:09 -07:00
- 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.
2019-12-08 11:46:20 -07:00
- User notification settings: Add `privacy_option` option.
2019-12-05 06:18:25 -07:00
- Support for custom Elixir modules (such as MRF policies)
2019-12-10 06:19:26 -07:00
- User settings: Add _This account is a_ option.
2020-01-22 11:29:07 -07:00
- A new users admin digest email
2019-12-05 14:25:44 -07:00
- OAuth: admin scopes support (relevant setting: `[:auth, :enforce_oauth_admin_scope_usage]` ).
2019-12-16 12:06:58 -07:00
- Add an option `authorized_fetch_mode` to require HTTP signatures for AP fetches.
2020-02-08 09:58:02 -07:00
- ActivityPub: support for `replies` collection (output for outgoing federation & fetching on incoming federation).
2020-01-09 12:18:55 -07:00
- Mix task to refresh counter cache (`mix pleroma.refresh_counter_cache`)
2019-10-18 06:34:29 -06:00
< details >
< summary > API Changes< / summary >
2019-10-02 01:51:30 -06:00
- Job queue stats to the healthcheck page
2019-11-11 03:06:09 -07:00
- Admin API: Add ability to fetch reports, grouped by status `GET /api/pleroma/admin/grouped_reports`
2019-09-22 14:14:18 -06:00
- Admin API: Add ability to require password reset
2019-09-27 20:13:26 -06:00
- Mastodon API: Account entities now include `follow_requests_count` (planned Mastodon 3.x addition)
2019-09-28 20:18:34 -06:00
- 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
2019-10-01 16:16:29 -06:00
- Mastodon API: Add `upload_limit` , `avatar_upload_limit` , `background_upload_limit` , and `banner_upload_limit` to `/api/v1/instance`
2019-10-01 15:37:08 -06:00
- Mastodon API: Add `pleroma.unread_conversation_count` to the Account entity
2019-10-06 02:43:49 -06:00
- OAuth: support for hierarchical permissions / [Mastodon 2.4.3 OAuth permissions ](https://docs.joinmastodon.org/api/permissions/ )
2019-10-07 06:20:41 -06:00
- Metadata Link: Atom syndication Feed
2019-10-09 00:11:57 -06:00
- Mix task to re-count statuses for all users (`mix pleroma.count_statuses`)
2019-10-08 14:05:57 -06:00
- Mastodon API: Add `exclude_visibilities` parameter to the timeline and notification endpoints
2019-10-10 15:24:31 -06:00
- Admin API: `/users/:nickname/toggle_activation` endpoint is now deprecated in favor of: `/users/activate` , `/users/deactivate` , both accept `nicknames` array
2019-11-11 03:16:04 -07:00
- 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)
2019-10-11 10:12:29 -06:00
- Admin API: Add `GET /api/pleroma/admin/relay` endpoint - lists all followed relays
2019-10-10 21:40:58 -06:00
- Pleroma API: `POST /api/v1/pleroma/conversations/read` to mark all conversations as read
2019-11-12 04:51:12 -07:00
- ActivityPub: Support `Move` activities
2019-10-21 02:53:11 -06:00
- Mastodon API: Add `/api/v1/markers` for managing timeline read markers
2019-11-06 17:00:21 -07:00
- Mastodon API: Add the `recipients` parameter to `GET /api/v1/conversations`
2019-11-07 23:23:24 -07:00
- Configuration: `feed` option for user atom feed.
2019-11-10 04:32:50 -07:00
- Pleroma API: Add Emoji reactions
2019-11-14 07:44:07 -07:00
- Admin API: Add `/api/pleroma/admin/instances/:instance/statuses` - lists all statuses from a given instance
2020-02-26 04:47:19 -07:00
- Admin API: Add `/api/pleroma/admin/users/:nickname/statuses` - lists all statuses from a given user
2019-11-19 04:14:02 -07:00
- 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
2019-12-10 06:19:26 -07:00
- 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.
2019-12-11 08:29:31 -07:00
- Captcha: Support native provider
- Captcha: Enable by default
2019-12-17 03:00:46 -07:00
- Mastodon API: Add support for `account_id` param to filter notifications by the account
2020-01-20 08:24:20 -07:00
- Mastodon API: Add `emoji_reactions` property to Statuses
2020-01-22 05:58:02 -07:00
- Mastodon API: Change emoji reaction reply format
2020-01-22 12:12:45 -07:00
- Notifications: Added `pleroma:emoji_reaction` notification type
2020-01-24 02:53:01 -07:00
- Mastodon API: Change emoji reaction reply format once more
2019-12-17 12:13:45 -07:00
- Configuration: `feed.logo` option for tag feed.
- Tag feed: `/tags/:tag.rss` - list public statuses by hashtag.
2020-01-29 03:40:57 -07:00
- Mastodon API: Add `reacted` property to `emoji_reactions`
2020-02-19 09:17:05 -07:00
- Pleroma API: Add reactions for a single emoji.
2020-02-08 09:58:02 -07:00
- ActivityPub: `[:activitypub, :note_replies_output_limit]` setting sets the number of note self-replies to output on outgoing federation.
2020-01-09 12:18:55 -07:00
- Admin API: `GET /api/pleroma/admin/stats` to get status count by visibility scope
2020-02-10 04:32:38 -07:00
- Admin API: `GET /api/pleroma/admin/statuses` - list all statuses (accepts `godmode` and `local_only` )
2019-10-27 07:11:25 -06:00
< / details >
2019-09-29 09:43:27 -06:00
2019-09-20 08:54:38 -06:00
### Fixed
2019-10-18 06:34:29 -06:00
- Report emails now include functional links to profiles of remote user accounts
2019-11-11 07:05:30 -07:00
- Not being able to log in to some third-party apps when logged in to MastoFE
2019-12-04 16:50:38 -07:00
- MRF: `Delete` activities being exempt from MRF policies
2019-12-08 07:36:44 -07:00
- OTP releases: Not being able to configure OAuth expired token cleanup interval
2019-12-08 09:42:40 -07:00
- OTP releases: Not being able to configure HTML sanitization policy
2020-02-07 09:21:55 -07:00
- OTP releases: Not being able to change upload limit (again)
2019-12-11 14:03:54 -07:00
- Favorites timeline now ordered by favorite date instead of post date
2020-02-06 07:03:53 -07:00
- Support for cancellation of a follow request
2019-10-18 06:34:29 -06:00
< details >
< summary > API Changes< / summary >
2019-09-20 08:54:38 -06:00
- Mastodon API: Fix private and direct statuses not being filtered out from the public timeline for an authenticated user (`GET /api/v1/timelines/public`)
2019-10-03 16:05:50 -06:00
- Mastodon API: Inability to get some local users by nickname in `/api/v1/accounts/:id_or_nickname`
2019-11-21 21:35:21 -07:00
- 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)
2019-11-16 02:44:48 -07:00
- Admin API: Error when trying to update reports in the "old" format
2020-01-06 07:10:07 -07:00
- 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
2019-10-18 06:34:29 -06:00
< / details >
2019-09-17 14:48:26 -06:00
2020-03-05 12:28:37 -07:00
## [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
2019-11-19 14:01:58 -07:00
## [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
2019-11-15 15:02:08 -07:00
## [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
2019-10-18 15:37:39 -06:00
## [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.
2019-09-17 14:48:26 -06:00
2019-10-18 06:34:29 -06:00
## [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'
```
2019-07-31 11:23:16 -06:00
### Security
2019-09-13 16:50:15 -06:00
- Mastodon API: respect post privacy in `/api/v1/statuses/:id/{favourited,reblogged}_by`
2019-07-31 11:23:16 -06:00
2019-09-06 09:28:01 -06:00
### Removed
- **Breaking:** GNU Social API with Qvitter extensions support
- Emoji: Remove longfox emojis.
- Remove `Reply-To` header from report emails for admins.
2019-10-18 06:34:29 -06:00
- ActivityPub: The `/objects/:uuid/likes` endpoint.
2019-09-06 09:28:01 -06:00
2019-07-10 02:09:55 -06:00
### 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
2019-07-26 07:33:25 -06:00
- **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
2019-09-04 02:33:08 -06:00
- **Breaking:** `/api/pleroma/notifications/read` is moved to `/api/v1/pleroma/notifications/read` and now supports `max_id` and responds with Mastodon API entities.
2019-08-30 05:09:07 -06:00
- Configuration: added `config/description.exs` , from which `docs/config.md` is generated
2019-07-10 02:09:55 -06:00
- Configuration: OpenGraph and TwitterCard providers enabled by default
- Configuration: Filter.AnonymizeFilename added ability to retain file extension with custom text
2019-07-12 12:49:16 -06:00
- Federation: Return 403 errors when trying to request pages from a user's follower/following collections if they have `hide_followers` /`hide_follows` set
2019-07-10 02:09:55 -06:00
- NodeInfo: Return `skipThreadContainment` in `metadata` for the `skip_thread_containment` option
2019-07-29 10:17:40 -06:00
- NodeInfo: Return `mailerEnabled` in `metadata`
2019-07-14 13:25:03 -06:00
- Mastodon API: Unsubscribe followers when they unfollow a user
2019-08-30 05:09:07 -06:00
- Mastodon API: `pleroma.thread_muted` key in the Status entity
2019-07-23 16:50:09 -06:00
- AdminAPI: Add "godmode" while fetching user statuses (i.e. admin can see private statuses)
2019-08-20 06:50:50 -06:00
- Improve digest email template
2019-09-03 04:58:27 -06:00
– `total` alongside with `items` when paginating
2019-10-18 06:34:29 -06:00
- The `Pleroma.FlakeId` module has been replaced with the `flake_id` library.
2019-07-10 02:09:55 -06:00
### Fixed
2019-08-26 13:34:52 -06:00
- Following from Osada
2019-08-22 18:17:20 -06:00
- Favorites timeline doing database-intensive queries
2019-07-10 02:09:55 -06:00
- Metadata rendering errors resulting in the entire page being inaccessible
2019-08-11 14:19:20 -06:00
- `federation_incoming_replies_max_depth` option being ignored in certain cases
2019-07-10 02:09:55 -06:00
- Mastodon API: Handling of search timeouts (`/api/v1/search` and `/api/v2/search` )
2019-09-05 02:58:02 -06:00
- Mastodon API: Misskey's endless polls being unable to render
2019-07-10 02:09:55 -06:00
- Mastodon API: Embedded relationships not being properly rendered in the Account entity of Status entity
2019-09-04 23:32:49 -06:00
- Mastodon API: Notifications endpoint crashing if one notification failed to render
2019-10-18 06:34:29 -06:00
- Mastodon API: `exclude_replies` is correctly handled again.
2019-07-11 07:55:31 -06:00
- Mastodon API: Add `account_id` , `type` , `offset` , and `limit` to search API (`/api/v1/search` and `/api/v2/search` )
2019-07-21 20:43:55 -06:00
- Mastodon API, streaming: Fix filtering of notifications based on blocks/mutes/thread mutes
2019-10-18 06:34:29 -06:00
- 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
2019-07-21 09:22:22 -06:00
- Rich Media: Parser failing when no TTL can be found by image TTL setters
2019-07-23 16:58:31 -06:00
- Rich Media: The crawled URL is now spliced into the rich media data.
2019-07-21 20:18:45 -06:00
- ActivityPub S2S: sharedInbox usage has been mostly aligned with the rules in the AP specification.
2019-10-18 06:34:29 -06:00
- ActivityPub C2S: follower/following collection pages being inaccessible even when authentifucated if `hide_followers` / `hide_follows` was set
2019-08-14 16:42:43 -06:00
- ActivityPub: Deactivated user deletion
2019-09-09 12:30:02 -06:00
- ActivityPub: Fix `/users/:nickname/inbox` crashing without an authenticated user
2019-08-29 18:38:03 -06:00
- MRF: fix ability to follow a relay when AntiFollowbotPolicy was enabled
2019-10-18 06:34:29 -06:00
- 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
2019-07-10 02:09:55 -06:00
2019-06-27 15:34:27 -06:00
### Added
2019-08-24 09:33:17 -06:00
- 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.
2019-08-24 07:48:33 -06:00
- Configuration: `ActivityExpiration.enabled` controls whether expired activites will get deleted at the appropriate time. Enabled by default.
2019-08-12 06:26:18 -06:00
- Conversations: Add Pleroma-specific conversation endpoints and status posting extensions. Run the `bump_all_conversations` task again to create the necessary data.
2019-06-27 15:34:27 -06:00
- MRF: Support for priming the mediaproxy cache (`Pleroma.Web.ActivityPub.MRF.MediaProxyWarmingPolicy`)
2019-07-13 12:30:45 -06:00
- MRF: Support for excluding specific domains from Transparency.
2019-07-17 07:55:47 -06:00
- MRF: Support for filtering posts based on who they mention (`Pleroma.Web.ActivityPub.MRF.MentionPolicy`)
2019-06-30 03:08:46 -06:00
- 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 )
2019-07-09 11:49:04 -06:00
- Mastodon API, streaming: Add support for passing the token in the `Sec-WebSocket-Protocol` header
2019-07-09 12:20:36 -06:00
- Mastodon API, extension: Ability to reset avatar, profile banner, and background
2019-10-18 06:34:29 -06:00
- Mastodon API: Add support for `fields_attributes` API parameter (setting custom fields)
2019-07-14 07:29:31 -06:00
- 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
2019-07-16 05:04:11 -06:00
- 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 >
2019-07-24 09:12:27 -06:00
- Mastodon API: Add support for the `domain_blocking` attribute in the relationship API (`GET /api/v1/accounts/relationships`).
2019-07-16 05:14:46 -06:00
- Mastodon API: Add `pleroma.deactivated` to the Account entity
2019-07-16 15:44:50 -06:00
- Mastodon API: added `/auth/password` endpoint for password reset with rate limit.
2019-07-15 16:10:33 -06:00
- Mastodon API: /api/v1/accounts/:id/statuses now supports nicknames or user id
2019-07-26 06:08:46 -06:00
- Mastodon API: Improve support for the user profile custom fields
2019-10-18 06:34:29 -06:00
- 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`)
2019-07-01 05:04:24 -06:00
- Admin API: Return users' tags when querying reports
- Admin API: Return avatar and display name when querying users
2019-07-05 10:33:53 -06:00
- Admin API: Allow querying user by ID
2019-07-11 07:02:13 -06:00
- Admin API: Added support for `tuples` .
2019-07-30 10:36:05 -06:00
- Admin API: Added endpoints to run mix tasks pleroma.config migrate_to_db & pleroma.config migrate_from_db
2019-07-09 11:36:35 -06:00
- Added synchronization of following/followers counters for external users
2019-07-09 23:34:21 -06:00
- Configuration: `enabled` option for `Pleroma.Emails.Mailer` , defaulting to `false` .
2019-07-13 05:49:39 -06:00
- Configuration: Pleroma.Plugs.RateLimiter `bucket_name` , `params` options.
2019-08-05 02:33:34 -06:00
- Configuration: `user_bio_length` and `user_name_length` options.
2019-07-11 07:17:03 -06:00
- Addressable lists
2019-07-16 15:44:50 -06:00
- Twitter API: added rate limit for `/api/account/password_reset` endpoint.
2019-07-17 11:49:21 -06:00
- ActivityPub: Add an internal service actor for fetching ActivityPub objects.
2019-07-17 17:07:53 -06:00
- ActivityPub: Optional signing of ActivityPub object fetches.
2019-07-13 15:37:19 -06:00
- Admin API: Endpoint for fetching latest user's statuses
2019-07-28 14:30:10 -06:00
- Pleroma API: Add `/api/v1/pleroma/accounts/confirmation_resend?email=<email>` for resending account confirmation.
2019-09-13 00:09:35 -06:00
- Pleroma API: Email change endpoint.
2019-08-25 13:39:37 -06:00
- Admin API: Added moderation log
2019-09-09 12:53:08 -06:00
- Web response cache (currently, enabled for ActivityPub)
2019-10-01 14:00:27 -06:00
- Reverse Proxy: Do not retry failed requests to limit pressure on the peer
2019-06-30 03:08:46 -06:00
2019-07-11 07:02:13 -06:00
### Changed
- Configuration: Filter.AnonymizeFilename added ability to retain file extension with custom text
- Admin API: changed json structure for saving config settings.
2019-07-14 00:20:54 -06:00
- RichMedia: parsers and their order are configured in `rich_media` config.
2019-07-16 10:52:36 -06:00
- RichMedia: add the rich media ttl based on image expiration time.
2019-07-11 07:02:13 -06:00
2019-09-26 16:16:24 -06:00
## [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.
2019-09-17 14:48:26 -06:00
## [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.
2019-09-17 15:24:21 -06:00
- **Breaking:** ActivityPub: The `accept_blocks` configuration setting.
2019-09-17 14:48:26 -06:00
## [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
2019-08-03 22:32:45 -06:00
2019-07-14 11:49:12 -06:00
## [1.0.1] - 2019-07-14
### Security
- OStatus: fix an object spoofing vulnerability.
2019-06-28 09:15:44 -06:00
## [1.0.0] - 2019-06-29
2019-06-18 05:09:15 -06:00
### Security
- Mastodon API: Fix display names not being sanitized
2019-06-25 21:46:06 -06:00
- Rich media: Do not crawl private IP ranges
2019-04-12 15:31:18 -06:00
### Added
2019-06-03 18:08:00 -06:00
- Digest email for inactive users
2019-05-31 11:15:44 -06:00
- Add a generic settings store for frontends / clients to use.
2019-06-04 02:49:57 -06:00
- Explicit addressing option for posting.
2019-05-22 05:07:51 -06:00
- Optional SSH access mode. (Needs `erlang-ssh` package on some distributions).
2019-05-21 10:57:36 -06:00
- [MongooseIM ](https://github.com/esl/MongooseIM ) http authentication support.
2019-04-12 15:31:18 -06:00
- LDAP authentication
- External OAuth provider authentication
2019-06-09 04:56:41 -06:00
- Support for building a release using [`mix release` ](https://hexdocs.pm/mix/master/Mix.Tasks.Release.html )
2019-04-12 15:31:18 -06:00
- 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
2019-05-16 12:17:09 -06:00
- Mix Tasks: `mix pleroma.database bump_all_conversations`
2019-04-18 15:26:46 -06:00
- Mix Tasks: `mix pleroma.database remove_embedded_objects`
2019-05-16 14:04:08 -06:00
- Mix Tasks: `mix pleroma.database update_users_following_followers_counts`
2019-05-16 07:23:41 -06:00
- Mix Tasks: `mix pleroma.user toggle_confirmed`
2019-06-14 09:45:05 -06:00
- Mix Tasks: `mix pleroma.config migrate_to_db`
- Mix Tasks: `mix pleroma.config migrate_from_db`
2019-06-03 01:55:16 -06:00
- Federation: Support for `Question` and `Answer` objects
2019-04-12 15:31:18 -06:00
- Federation: Support for reports
2019-06-03 01:55:16 -06:00
- Configuration: `poll_limits` option
2019-06-25 21:48:59 -06:00
- Configuration: `pack_extensions` option
2019-04-12 15:31:18 -06:00
- Configuration: `safe_dm_mentions` option
- Configuration: `link_name` option
- Configuration: `fetch_initial_posts` option
2019-04-17 01:27:51 -06:00
- Configuration: `notify_email` option
2019-04-25 17:27:38 -06:00
- Configuration: Media proxy `whitelist` option
2019-05-15 23:49:40 -06:00
- Configuration: `report_uri` option
2019-06-03 18:08:00 -06:00
- Configuration: `email_notifications` option
2019-06-11 08:25:53 -06:00
- Configuration: `limit_to_local_content` option
2019-04-22 20:47:43 -06:00
- Pleroma API: User subscriptions
2019-04-22 01:19:53 -06:00
- Pleroma API: Healthcheck endpoint
2019-05-20 07:19:42 -06:00
- Pleroma API: `/api/v1/pleroma/mascot` per-user frontend mascot configuration endpoints
2019-04-12 15:31:18 -06:00
- Admin API: Endpoints for listing/revoking invite tokens
- Admin API: Endpoints for making users follow/unfollow each other
2019-05-08 08:34:36 -06:00
- Admin API: added filters (role, tags, email, name) for users endpoint
2019-05-16 13:09:18 -06:00
- Admin API: Endpoints for managing reports
- Admin API: Endpoints for deleting and changing the scope of individual reported statuses
2019-06-14 09:45:05 -06:00
- Admin API: Endpoints to view and change config settings.
2019-05-14 13:47:23 -06:00
- AdminFE: initial release with basic user management accessible at /pleroma/admin/
2019-06-15 03:27:27 -06:00
- Mastodon API: Add chat token to `verify_credentials` response
2019-06-15 03:02:05 -06:00
- Mastodon API: Add background image setting to `update_credentials`
2019-04-12 15:31:18 -06:00
- Mastodon API: [Scheduled statuses ](https://docs.joinmastodon.org/api/rest/scheduled-statuses/ )
- Mastodon API: `/api/v1/notifications/destroy_multiple` (glitch-soc extension)
2019-04-22 20:47:43 -06:00
- Mastodon API: `/api/v1/pleroma/accounts/:id/favourites` (API extension)
2019-04-12 15:31:18 -06:00
- Mastodon API: [Reports ](https://docs.joinmastodon.org/api/rest/reports/ )
2019-05-14 13:47:23 -06:00
- Mastodon API: `POST /api/v1/accounts` (account creation API)
2019-06-03 01:55:16 -06:00
- Mastodon API: [Polls ](https://docs.joinmastodon.org/api/rest/polls/ )
2019-04-12 15:31:18 -06:00
- ActivityPub C2S: OAuth endpoints
2019-05-14 13:47:23 -06:00
- Metadata: RelMe provider
2019-05-06 11:51:03 -06:00
- OAuth: added support for refresh tokens
2019-04-20 06:17:21 -06:00
- Emoji packs and emoji pack manager
2019-05-20 19:22:27 -06:00
- Object pruning (`mix pleroma.database prune_objects`)
2019-05-22 09:44:50 -06:00
- OAuth: added job to clean expired access tokens
2019-05-21 23:55:09 -06:00
- MRF: Support for rejecting reports from specific instances (`mrf_simple`)
- MRF: Support for stripping avatars and banner images from specific instances (`mrf_simple`)
2019-06-03 23:37:31 -06:00
- MRF: Support for running subchains.
2019-06-03 12:05:45 -06:00
- Configuration: `skip_thread_containment` option
2019-06-11 01:36:51 -06:00
- Configuration: `rate_limit` option. See `Pleroma.Plugs.RateLimiter` documentation for details.
2019-06-19 21:01:03 -06:00
- MRF: Support for filtering out likely spam messages by rejecting posts from new users that contain links.
2019-06-25 21:46:06 -06:00
- Configuration: `ignore_hosts` option
- Configuration: `ignore_tld` option
2019-06-27 15:25:55 -06:00
- Configuration: default syslog tag "Pleroma" is now lowercased to "pleroma"
2019-04-12 15:31:18 -06:00
### Changed
2019-06-23 00:31:39 -06:00
- **Breaking:** bind to 127.0.0.1 instead of 0.0.0.0 by default
2019-04-13 12:17:10 -06:00
- **Breaking:** Configuration: move from Pleroma.Mailer to Pleroma.Emails.Mailer
2019-06-07 06:28:14 -06:00
- Thread containment / test for complete visibility will be skipped by default.
2019-04-12 15:31:18 -06:00
- 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
2019-04-15 02:50:36 -06:00
- Federation: Removed `inReplyToStatusId` from objects
2019-04-12 15:31:18 -06:00
- Configuration: Dedupe enabled by default
2019-06-08 09:02:57 -06:00
- Configuration: Default log level in `prod` environment is now set to `warn`
2019-04-16 08:24:24 -06:00
- Configuration: Added `extra_cookie_attrs` for setting non-standard cookie attributes. Defaults to ["SameSite=Lax"] so that remote follows work.
2019-04-25 17:27:38 -06:00
- Timelines: Messages involving people you have blocked will be excluded from the timeline in all cases instead of just repeats.
2019-05-14 13:47:23 -06:00
- Admin API: Move the user related API to `api/pleroma/admin/users`
2019-05-17 00:35:31 -06:00
- Admin API: `POST /api/pleroma/admin/users` will take list of users
2019-05-14 13:47:23 -06:00
- Pleroma API: Support for emoji tags in `/api/pleroma/emoji` resulting in a breaking API change
2019-04-12 15:31:18 -06:00
- 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
2019-04-22 03:02:41 -06:00
- Mastodon API: Add `pleroma.conversation_id` , `pleroma.in_reply_to_account_acct` fields to the Status entity
2019-04-24 11:01:42 -06:00
- 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
2019-04-25 00:14:35 -06:00
- Mastodon API: Add `pleroma.show_role` , `pleroma.no_rich_text` fields to the Source subentity
2019-04-24 11:01:42 -06:00
- Mastodon API: Add support for updating `no_rich_text` , `hide_followers` , `hide_follows` , `hide_favorites` , `show_role` in `PATCH /api/v1/update_credentials`
2019-04-12 15:31:18 -06:00
- 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
2019-05-13 12:35:45 -06:00
- Mastodon API: Added support max_id & since_id for bookmark timeline endpoints.
2019-04-12 15:31:18 -06:00
- Deps: Updated Cowboy to 2.6
- Deps: Updated Ecto to 3.0.7
2019-04-20 06:17:21 -06:00
- Don't ship finmoji by default, they can be installed as an emoji pack
2019-05-14 05:40:21 -06:00
- Hide deactivated users and their statuses
2019-05-17 14:43:31 -06:00
- Posts which are marked sensitive or tagged nsfw no longer have link previews.
2019-05-20 22:58:26 -06:00
- HTTP connection timeout is now set to 10 seconds.
2019-05-20 19:40:29 -06:00
- Respond with a 404 Not implemented JSON error message when requested API is not implemented
2019-06-25 21:43:53 -06:00
- Rich Media: crawl only https URLs.
2019-04-12 15:31:18 -06:00
### Fixed
2019-06-05 08:51:28 -06:00
- Follow requests don't get 'stuck' anymore.
2019-05-03 11:15:55 -06:00
- Added an FTS index on objects. Running `vacuum analyze` and setting a larger `work_mem` is recommended.
2019-04-12 15:31:18 -06:00
- 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
2019-05-14 13:47:23 -06:00
- Proper Twitter Card generation instead of a dummy
2019-05-06 10:45:22 -06:00
- Deletions failing for users with a large number of posts
2019-04-12 15:31:18 -06:00
- 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
2019-04-25 17:27:38 -06:00
- Federation: Follow requests from remote users who have been blocked will be automatically rejected if appropriate
2019-04-12 15:31:18 -06:00
- 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
2019-04-20 12:28:08 -06:00
- Pleroma API: Importing follows from Mastodon 2.8+
2019-04-24 11:01:42 -06:00
- 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`
2019-04-12 15:31:18 -06:00
- 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
2019-04-18 23:35:05 -06:00
- Mastodon API: Handling of `reblogs` in `/api/v1/accounts/:id/follow`
2019-04-15 11:32:14 -06:00
- Mastodon API: Correct `reblogged` , `favourited` , and `bookmarked` values in the reblog status JSON
2019-04-24 11:01:42 -06:00
- Mastodon API: Exposing default scope of the user to anyone
2019-05-13 12:05:33 -06:00
- Mastodon API: Make `irreversible` field default to `false` [`POST /api/v1/filters`]
2019-05-30 15:03:31 -06:00
- Mastodon API: Replace missing non-nullable Card attributes with empty strings
2019-05-17 14:31:39 -06:00
- User-Agent is now sent correctly for all HTTP requests.
2019-05-25 19:57:22 -06:00
- MRF: Simple policy now properly delists imported or relayed statuses
2019-04-12 15:31:18 -06:00
2019-05-14 11:52:08 -06:00
## Removed
2019-05-16 07:23:41 -06:00
- Configuration: `config :pleroma, :fe` in favor of the more flexible `config :pleroma, :frontend_configurations`
2019-05-14 11:52:08 -06:00
2019-05-31 06:25:17 -06:00
## [0.9.99999] - 2019-05-31
### Security
- Mastodon API: Fix lists leaking private posts
2019-04-12 15:31:18 -06:00
## [0.9.9999] - 2019-04-05
### Security
2019-04-13 12:17:10 -06:00
- Mastodon API: Fix content warnings skipping HTML sanitization
2019-04-12 15:31:18 -06:00
## [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.
