Age | Commit message (Collapse) | Author |
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When someone isn't a superuser any more, they shouldn't see the reporsts any more either.
Here we delete the report notifications from a user when that user gets updated from being a superuser to a non-superuser.
|
|
|
|
Closes: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3790
|
|
Closes: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3790
|
|
|
|
|
|
|
|
|
|
Alter priority of Delete activities to be lowest
See merge request pleroma/pleroma!3782
|
|
Object.Fetcher: Set reachable on successful fetch
See merge request pleroma/pleroma!3780
|
|
This will prevent a user with a large number of posts from negatively affecting performance of the outgoing federation queue if they delete their account.
|
|
Fix typo in CSP Report-To header name
See merge request pleroma/pleroma!3768
|
|
|
|
Give admin the choice to not strip reported statuses
Closes #2887
See merge request pleroma/pleroma!3773
|
|
|
|
|
|
|
|
|
|
The header name was Report-To, not Reply-To.
In any case, that's now being changed to the Reporting-Endpoints HTTP
Response Header.
https://w3c.github.io/reporting/#header
https://github.com/w3c/reporting/issues/177
CanIUse says the Report-To header is still supported by current Chrome
and friends.
https://caniuse.com/mdn-http_headers_report-to
It doesn't have any data for the Reporting-Endpoints HTTP header, but
this article says Chrome 96 supports it.
https://web.dev/reporting-api/
(Even though that's come out one year ago, that's not compatible with
Network Error Logging which's still using the Report-To version of the
API)
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
|
|
|
|
|
Fix User.get_or_fetch/1 with usernames starting with http
Closes #2930
See merge request pleroma/pleroma!3751
|
|
Push.Impl: support edits
See merge request pleroma/pleroma!3760
|
|
As a side-effect it also changes the ChatMessage delete ID to an
Activity.id rather than MessageReference.id
Closes: https://git.pleroma.social/pleroma/pleroma/-/issues/2958
|
|
|
|
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
|
|
User: search: exclude inactive users from user search
See merge request pleroma/pleroma!3755
|
|
Make instance document controller test sync
Closes #2940
See merge request pleroma/pleroma!3757
|
|
Bugfix: Elixir 1.14
See merge request pleroma/pleroma!3740
|
|
|
|
|
|
Use Websockex to replace websocket_client
See merge request pleroma/pleroma!3743
|
|
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
|
|
|
|
Randomness is a huge resource sink, so let's just use
a some that we made earlier
|
|
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
|
|
# 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.
|