Age | Commit message (Collapse) | Author |
|
|
|
User: search: exclude inactive users from user search
See merge request pleroma/pleroma!3755
|
|
Bugfix: Elixir 1.14
See merge request pleroma/pleroma!3740
|
|
MastoAPI: POST /api/v1/accounts/:id/remove_from_followers
See merge request pleroma/pleroma!3647
|
|
This way we don't pollute search results with deactivated and deleted users
|
|
|
|
Non-Create/Listen activities had their associated object field
normalized and fetched, but only to use their `id` field, which is both
slow and redundant. This also failed on Undo activities, which delete
the associated object/activity in database.
Undo activities will now render properly and database loads should
improve ever so slightly.
|
|
Make backups require its own scope
Closes #2892
See merge request pleroma/pleroma!3721
|
|
User: generate private keys on user creation
See merge request pleroma/pleroma!3737
|
|
Bump minimum Elixir version to 1.10
See merge request pleroma/pleroma!3741
|
|
# Conflicts:
# CHANGELOG.md
|
|
This fixes a race condition bug where keys could be regenerated
post-federation, causing activities and HTTP signatures from an user to
be dropped due to key differences.
|
|
GoToSocial federation fixes
See merge request pleroma/pleroma!3725
|
|
Fix reply context fixing (Pleroma replies to Misskey threads) and removal of context objects
See merge request pleroma/pleroma!3717
|
|
Streaming fix
Closes #2796
See merge request pleroma/pleroma!3738
|
|
When generating OpenGraph and TwitterCard metadata for a post, the
summary field will be used first if it is set to generate the post
description.
|
|
BBS: add functionnalities and readability
See merge request pleroma/pleroma!3675
|
|
Add function to calculate associated object id
Closes #2307
See merge request pleroma/pleroma!3692
|
|
Editing
Closes #1429, #2859, and #2288
See merge request pleroma/pleroma!3678
|
|
Remote interaction with posts
Closes #2807 and #978
See merge request pleroma/pleroma!3587
|
|
1.9 being end-of-life
|
|
|
|
With the release of Elixir 1.14, Elixir 1.9 is now end-of-life.
Elixir 1.10 Release Notes:
https://github.com/elixir-lang/elixir/releases/tag/v1.10.0
|
|
|
|
|
|
|
|
|
|
emoji-test: update to latest 15.0 draft
See merge request pleroma/pleroma!3726
|
|
fix flaky test_user_relationship_test.exs:81
See merge request pleroma/pleroma!3697
|
|
|
|
As this plug is called on every request, this should reduce load on the
database by not requiring to select on the users table every single
time, and to instead use the by-ID user cache whenever possible.
|
|
|
|
|
|
|
|
|
|
There are two reasons for adding a GET endpoint:
0: Barely displaying the form does not change anything on the server.
1: It makes frontend development easier as they can now use a link,
instead of a form, to allow remote users to interact with local ones.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Some software, like GoToSocial, expose replies as ActivityPub
Collections, but do not expose any item array directly in the object,
causing validation to fail via the ObjectID validator. Now, Pleroma will
drop that field in this situation too.
|
|
The (request-target) used by Pleroma is non-standard, but many HTTP
signature implementations do it this way due to a misinterpretation of
the draft 06 of HTTP signatures: "path" was interpreted as not having
the query, though later examples show that it must be the absolute path
with the query part of the URL as well.
This behavior is kept to make sure most software (Pleroma itself,
Mastodon, and probably others) do not break, but Pleroma now accepts
signatures for a (request-target) containing the query, as expected by
many HTTP signature libraries, and clarified in the draft 11 of HTTP
signatures.
Additionally, the new draft renamed (request-target) to @request-target.
We now support both for incoming requests' signatures.
|
|
|
|
Due to the lengthiness of this task, the migration has been adapted into
a BaseMigrator migration, running in the background instead.
|
|
`context` fields for objects and activities can now be generated based
on the object/activity `inReplyTo` field or its ActivityPub ID, as a
fallback method in cases where `context` fields are missing for incoming
activities and objects.
|
|
'develop'
Treat MRF rejects as success in Oban worker
Closes #2912
See merge request pleroma/pleroma!3720
|
|
'develop'
Fix flaky tests with DB connections; Allow higher amount of restarts for Pleroma.Repo during testing
See merge request pleroma/pleroma!3696
|