Age | Commit message (Collapse) | Author |
|
|
|
Too many tests break as they don't include injected user agent in expected response
|
|
All tests related to streaming/chunking have been removed
|
|
Remove the :send_user_agent setting. We should always send the user agent.
Remove duplicate setting of the user agent from ReverseProxy module
|
|
|
|
Deletion resilience
See merge request pleroma/pleroma!3237
|
|
MRFs with Updates
See merge request pleroma/pleroma!3808
|
|
# Conflicts:
# CHANGELOG.md
|
|
TwitterCard meta tags are supposed to use the attributes "name" and "content".
OpenGraph tags use the attributes "property" and "content".
Twitter itself is smart enough to detect broken meta tags and discover the TwitterCard
using "property" and "content", but other platforms that only implement parsing of TwitterCards
and not OpenGraph may fail to correctly detect the tags as they're under the wrong attributes.
> "Open Graph protocol also specifies the use of property and content attributes for markup while
> Twitter cards use name and content. Twitter’s parser will fall back to using property and content,
> so there is no need to modify existing Open Graph protocol markup if it already exists." [0]
[0] https://developer.twitter.com/en/docs/twitter-for-websites/cards/guides/getting-started
|
|
|
|
|
|
|
|
Uploading an avatar media exceeding max size returns a 413
Closes #2856
See merge request pleroma/pleroma!3804
|
|
Update to Phoenix 1.6, Elixir 1.11, and chase dependencies
See merge request pleroma/pleroma!3766
|
|
|
|
|
|
This is inspired by https://akkoma.dev/AkkomaGang/akkoma/commit/d5828f1c5e54ca236e50ef7837bfba3d1e665854
|
|
This is inspired by https://akkoma.dev/AkkomaGang/akkoma/commit/d5828f1c5e54ca236e50ef7837bfba3d1e665854
|
|
|
|
|
|
Until now it was returning a 500 because the upload plug were going
through the changeset and ending in the JSON encoder, which raised
because struct has to @derive the encoder.
|
|
Report an Object, not a Create Activity
Closes #2986
See merge request pleroma/pleroma!3788
|
|
|
|
Change follow_operation schema to use type BooleanLike
Closes #2999
See merge request pleroma/pleroma!3787
|
|
|
|
Mergeback: 2.4.5
See merge request pleroma/pleroma!3794
|
|
|
|
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>
|