Age | Commit message (Collapse) | Author |
|
|
|
|
|
MediaProxyController: Apply CSP sandbox
See merge request pleroma/pleroma!3890
|
|
Fix ObjectTest
See merge request pleroma/pleroma!3887
|
|
Make sure object refetching follows update rules
See merge request pleroma/pleroma!3883
|
|
Set background worker timeout to 15 minutes
See merge request pleroma/pleroma!3857
|
|
Remove crypt(3) support
Closes #3030 and #3062
See merge request pleroma/pleroma!3847
|
|
fix: atom/rss feed issues
Closes #3045
See merge request pleroma/pleroma!3851
|
|
fix: remove static_fe pipeline for /users/:nickname/feed
See merge request pleroma/pleroma!3852
|
|
Stop oban from retrying if validating errors occur when processing incoming data
See merge request pleroma/pleroma!3844
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Cachex for this was not started
|
|
|
|
|
|
|
|
This reverts commit 4504c810802e2253599f06ddf6d58d3389fb23ac.
|
|
|
|
|
|
revoking privileges
|
|
fine_grained_moderation_privileges
|
|
MRFs with Updates
See merge request pleroma/pleroma!3808
|
|
fine_grained_moderation_privileges
|
|
# 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
|
|
|
|
fine_grained_moderation_privileges
|
|
_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.
|
|
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
|
|
|
|
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.
|