Age | Commit message (Collapse) | Author |
|
just activities
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
MRF: subchain policy
See merge request pleroma/pleroma!1233
|
|
Generic settings store for frontend user settings
See merge request pleroma/pleroma!1221
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Mastodon Conversations API: Align to Mastodon behavior
See merge request pleroma/pleroma!1215
|
|
|
|
exclusion work
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
notification controls, part 2
See merge request pleroma/pleroma!1204
|
|
|
|
|
|
|
|
Also in this commit by accident:
- Fix query ordering causing exclude_poll_votes to not work
- Do not create notifications for Answer objects
|
|
|
|
|
|
visibility: if litepub:directMessage is asserted, always report the object as "direct" visibility
See merge request pleroma/pleroma!1230
|
|
|
|
as "direct" visibility
|
|
|
|
|
|
https://docs.joinmastodon.org/api/rest/accounts/
https://docs.joinmastodon.org/api/rest/search/
|
|
Mastodon API: Fix lists leaking private posts
See merge request pleroma/pleroma!1222
|
|
|
|
|
|
This is to provide a generic frontend settings storage mechanism for all kinds
of frontends.
|
|
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
|
|
|