Age | Commit message (Collapse) | Author |
|
|
|
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
|
|
|
|
|
|
Use Pleroma.Config everywhere
See merge request pleroma/pleroma!1214
|
|
|
|
|
|
|
|
remove @httpoison, @ostatus and @websub compile-time constants
See merge request pleroma/pleroma!1203
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
move key generation functions into Pleroma.Keys module
See merge request pleroma/pleroma!1186
|
|
MastoAPI AccountView: fill source.note with plaintext version of note
Closes #926
See merge request pleroma/pleroma!1189
|
|
Closes: https://git.pleroma.social/pleroma/pleroma/issues/926
|
|
|
|
MongooseIM: Add basic integration endpoints.
See merge request pleroma/pleroma!1172
|
|
|
|
|
|
when requested API is not implemented
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|