Age | Commit message (Collapse) | Author |
|
1.0.5 release
See merge request pleroma/pleroma!1549
|
|
|
|
|
|
|
|
memory leaks on recursive replies fetching.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
describe()
|
|
|
|
|
|
Anyone who is interested in dropping blocks can write their own MRF
policy at this point. This setting predated the MRF framework.
Disabling the side effect (unsubscription) is still a config option
per policy.
|
|
|
|
`name` key and use a depth limit when fetching it
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
because the objects are no longer supposed to be embedded
|
|
in the Create activity
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes: https://git.pleroma.social/pleroma/pleroma/issues/1155
[ci skip]
|
|
Closes: https://git.pleroma.social/pleroma/pleroma/issues/1058
|
|
|
|
[ci skip]
|
|
|
|
|
|
`User.profile_url` already fallbacks to ap_id
|
|
mention URL
Fixes #1165
|
|
It was calling CommonAPI.thread_muted? with post author's account
instead of viewer's one.
|
|
followers/following is enabled
We are already doing that in AP representation, so I think we should do
it here as well for consistency.
|
|
1.0.4 release
See merge request pleroma/pleroma!1519
|