Age | Commit message (Collapse) | Author |
|
|
|
memory leaks on recursive replies fetching.
|
|
|
|
|
|
|
|
|
|
because the objects are no longer supposed to be embedded
|
|
|
|
Some objects were not completely rewritten in the tests, which caused object
containment violations. Fix them by rewriting the object IDs to be in an
appropriate namespace.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This leads to a few situations where it is impossible to follow a user.
|
|
|
|
|
|
|
|
MRF: subchain policy
See merge request pleroma/pleroma!1233
|
|
|
|
|
|
|
|
|
|
visibility: if litepub:directMessage is asserted, always report the object as "direct" visibility
See merge request pleroma/pleroma!1230
|
|
|
|
as "direct" visibility
|
|
Our previous list visibility resolver grabbed posts if either follower
collection of the user in a list who is followed is in `to` or if
follower collection of the user in a list was in `cc`. This not only
missed unlisted posts but also lead to leaking private posts when
`fix_explicit_addressing` mistakingly started putting follower collections
to `cc` (also fixed in this MR).
Reported by @kurisu@iscute.moe via a DM
|
|
for it
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fix domain-unblocked reblogs
Closes #892
See merge request pleroma/pleroma!1157
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|