| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Favorites were paginating wrongly, because the pagination headers
where using the id of the id of the `Create` activity, while the
ordering was by the id of the `Like` activity. This isn't easy to
notice in most cases, as they usually have a similar order because
people tend to favorite posts as they come in. This commit adds a
way to give different pagination ids to the pagination helper, so
we can paginate correctly in cases like this.
|
|
remake-remodel-dms
|
|
|
|
|
|
|
|
|
|
Add OpenAPI spec for AdminAPI.RelayController
See merge request pleroma/pleroma!2579
|
|
Delete outgoing pending follow requests on user deletion
See merge request pleroma/pleroma!2631
|
|
remake-remodel-dms
|
|
|
|
remake-remodel-dms
|
|
|
|
|
|
|
|
|
|
|
|
Related: https://git.pleroma.social/pleroma/pleroma/issues/1643
|
|
|
|
|
|
|
|
activity-pub-use-atoms-as-keys
|
|
remake-remodel-dms
|
|
Fix AP C2S pagination
Closes #866 and #751
See merge request pleroma/pleroma!2491
|
|
This is to run things like streaming notifications out, which will
sometimes need data that is created by the transaction, but is
streamed out asynchronously.
|
|
As the notification type changes depending on the follow state,
the notification should not be created and streamed out before the
state settles. For this reason, the notification creation has been
delayed until it's clear if the user has been followed or not.
This is a bit hacky but it will be properly rewritten using the
pipeline soon.
|
|
This is to prevent wrong values in the stream.
|
|
|
|
|
|
|
|
remake-remodel-dms
|
|
|
|
|
|
|
|
|
|
|
|
# Conflicts:
# lib/pleroma/web/admin_api/controllers/admin_api_controller.ex
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
