Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
work anyway
Not sure why we tried to jam this through Pleroma.HTTP in the first place as upstream wants Hackney
|
|
|
|
Too many tests break as they don't include injected user agent in expected response
|
|
All tests related to streaming/chunking have been removed
|
|
expires is ignored.
|
|
|
|
Remove the :send_user_agent setting. We should always send the user agent.
Remove duplicate setting of the user agent from ReverseProxy module
|
|
Change the get_media/4 to get_media/3 as we don't need to special case following redirects anymore and we probably should have always been following redirects anyway
|
|
|
|
Deletion resilience
See merge request pleroma/pleroma!3237
|
|
add nixos to supported distros
See merge request pleroma/pleroma!3600
|
|
MRFs with Updates
See merge request pleroma/pleroma!3808
|
|
fix atom and rss feeds for users and tags
See merge request pleroma/pleroma!3783
|
|
# Conflicts:
# CHANGELOG.md
|
|
Fix TwitterCard meta tags
See merge request pleroma/pleroma!3811
|
|
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
|
|
|
|
|
|
|
|
_tag_activity.xml.eex used activity_content() instead
of activity_description(), and did not escape html properly.
|
|
|
|
|
|
|
|
|
|
Changes:
- make the XML closer to spec (RSS does not pass w3c's validator, but works)
- fix dates (RFC3339 for Atom, doc says RFC822 for RSS but RFC1123 is closer)
- fix attachment/enclosure links (but see below)
- set feed item title to post's "summary" if present
- pruned several elements that validators did not like
- examples: ap_enabled, user banner urls.
Specs:
- https://www.rssboard.org/rss-specification
- https://validator.w3.org/feed/docs/atom.html
- https://www.intertwingly.net/wiki/pie/Rss20AndAtom10Compared
Validators:
- https://validator.w3.org/feed/
- https://rssatom.com/feedvalidator.php
Attachment/enclosure links should have a "length" field (mandatory
according to the spec). This is not present in the object's data
map.
|
|
CI: Fix image for amd64-musl
See merge request pleroma/pleroma!3810
|
|
|
|
Extract translatable strings
See merge request pleroma/pleroma!3764
|
|
|
|
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
|
|
Fix failure when registering a user with no email when approval required
Closes #3021
See merge request pleroma/pleroma!3807
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
Add Gitlab Release™ into Release MR template
See merge request pleroma/pleroma!3797
|
|
Upgrade docs improvement: reccomend tagged releases over pulling stable branch
See merge request pleroma/pleroma!3800
|
|
|
|
CI: Tag amd64 releases for amd64 runners
See merge request pleroma/pleroma!3799
|