Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
refactor/following-relationships
|
|
|
|
Misc. fixes / improvements.
|
|
|
|
|
|
|
|
|
|
|
|
# Conflicts:
# CHANGELOG.md
|
|
This saves us lots of sending out because we can use sharedInbox.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Attachment field was filled in after the empty status check
|
|
|
|
|
|
|
|
Simplify updating user's `info`
See merge request pleroma/pleroma!1712
|
|
Replace `Pleroma.FlakeId` with `flake_id` hex package
See merge request pleroma/pleroma!1692
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
sixohsix/pleroma-post_expiration
|
|
|
|
|
|
|
|
|
|
|
|
This reverts merge request !1504
|
|
|
|
|
|
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.
|
|
|