Age | Commit message (Collapse) | Author |
|
|
|
Rewrite integration-test websocket client with Mint.WebSocket, closes #2812
Closes #2812
See merge request pleroma/pleroma!3649
|
|
|
|
|
|
|
|
|
|
|
|
Fix fedi-fe build URL, addresses #2920
See merge request pleroma/pleroma!3736
|
|
emoji-test: update to latest 15.0 draft
See merge request pleroma/pleroma!3726
|
|
Improve static page style
See merge request pleroma/pleroma!3729
|
|
Fix flaky rate_limiter_test.exs test "it restricts based on config values"
See merge request pleroma/pleroma!3688
|
|
Fix flaky/erratic test/pleroma/config/transfer_task_test.exs
See merge request pleroma/pleroma!3703
|
|
fix flaky participation_test.exs
See merge request pleroma/pleroma!3689
|
|
|
|
|
|
fix flaky test filter_controller_test.exs:200
See merge request pleroma/pleroma!3699
|
|
|
|
fix flaky test_user_relationship_test.exs:81
See merge request pleroma/pleroma!3697
|
|
|
|
OAuthPlug: use user cache instead of joining
See merge request pleroma/pleroma!3734
|
|
Add glitch-lily as an installable frontend
See merge request pleroma/pleroma!3727
|
|
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.
|
|
|
|
Use latest alpine version for docker image
See merge request pleroma/pleroma!3719
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Document the changes for Varnish 7.0+ compatibility and RFC compliance
See merge request pleroma/pleroma!3723
|
|
|
|
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
|
|
Synchronized settings for apps (frontends)
See merge request pleroma/pleroma!3698
|
|
Backport: bugfix/follow-state
Closes #2902
See merge request pleroma/pleroma!3718
|
|
Fix Varnish7 support
See merge request pleroma/pleroma!3722
|