Age | Commit message (Collapse) | Author |
|
|
|
Done via the following command:
git diff fcd5dd259a1700a045be902b43391b0d1bd58a5b --stat --name-only | xargs sed -i '/Pleroma Authors/c# Copyright © 2017-2020 Pleroma Authors <https:\/\/pleroma.social\/>'
|
|
|
|
|
|
UserRelationship-related functionality.
|
|
UserRelationships. User to UserRelationship relations and functions refactoring.
|
|
Admin API: Grouped reports, update multiple reports in one query
Closes admin-fe#43
See merge request pleroma/pleroma!1815
|
|
|
|
|
|
refactor/following-relationships
|
|
Misc. fixes / improvements.
|
|
|
|
|
|
|
|
# Conflicts:
# CHANGELOG.md
|
|
This saves us lots of sending out because we can use sharedInbox.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Simplify updating user's `info`
See merge request pleroma/pleroma!1712
|
|
|
|
|
|
|
|
|
|
|
|
sixohsix/pleroma-post_expiration
|
|
|
|
|
|
|
|
If we didn't put some kind of lifetime requirement on these, I guess you
could annoy people by sending large numbers of ephemeral posts that
provoke notifications but then disappear before anyone can read them.
|
|
The "expires_at" parameter accepts an ISO8601-formatted date which
defines when the activity will expire.
At this point the API will not give you any feedback about if your post
will expire or not.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes #1038
|
|
|
|
|
|
|