Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Refactor Follows/Followers counter syncronization and set hide_followers/hide_follows for remote users
See merge request pleroma/pleroma!1411
|
|
This enables to address the same group of people every time.
|
|
|
|
|
|
Disallow following locked accounts over OStatus
See merge request pleroma/pleroma!1512
|
|
|
|
|
|
This closes embargoed bug #1135.
|
|
|
|
|
|
|
|
|
|
|
|
This reverts merge request !1504
|
|
|
|
refactoring: begin to use constants
See merge request pleroma/pleroma!1500
|
|
|
|
|
|
|
|
for remote users
Closes #1104
|
|
|
|
|
|
|
|
|
|
|
|
Fix remote follow from /ostatus_subscribe
Closes #1103
See merge request pleroma/pleroma!1472
|
|
|
|
|
|
This ensures admin has full control over the path where media resides.
|
|
|
|
|
|
/api/v1/accounts/relationships)
|
|
actor"
This reverts commit 2981821db834448bf9b2ba26590314e36201664c.
|
|
NOTE: rewrite the commit msg
|
|
|
|
In the "pleroma" section of the MastoAPI for status activities you can
see an expires_at item that states when the activity will expire, or
nothing if the activity will not expire.
The expires_at date is only visible to the person who posted the
activity. This is the conservative approach in case some attacker
decides to write a logger for expiring posts. However, in the future of
OCAP, signed requests, and all that stuff, this attack might not be that
likely. Some other pleroma dev should remove the restriction in the code
at that time, if they're satisfied with the security implications of
doing so.
|