diff options
| author | Mike Verdone <spiral@arcseconds.net> | 2019-07-24 12:43:20 +0200 |
|---|---|---|
| committer | Mike Verdone <spiral@arcseconds.net> | 2019-07-24 14:47:22 +0200 |
| commit | 3cb471ec0688b81c8ef37dd27f2b82e6c858431f (patch) | |
| tree | fa538e4012cfbff2ad99f68fe818b9df582fa01c /docs/api/differences_in_mastoapi_responses.md | |
| parent | 36012ef6c1dfea2489e61063e14783fa3fb52700 (diff) | |
| download | pleroma-3cb471ec0688b81c8ef37dd27f2b82e6c858431f.tar.gz | |
Expose expires_at datetime in mastoAPI only for the activity actor
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.
Diffstat (limited to 'docs/api/differences_in_mastoapi_responses.md')
| -rw-r--r-- | docs/api/differences_in_mastoapi_responses.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/docs/api/differences_in_mastoapi_responses.md b/docs/api/differences_in_mastoapi_responses.md index 7d5be4713..168a13f4e 100644 --- a/docs/api/differences_in_mastoapi_responses.md +++ b/docs/api/differences_in_mastoapi_responses.md @@ -25,6 +25,7 @@ Has these additional fields under the `pleroma` object: - `in_reply_to_account_acct`: the `acct` property of User entity for replied user (if any) - `content`: a map consisting of alternate representations of the `content` property with the key being it's mimetype. Currently the only alternate representation supported is `text/plain` - `spoiler_text`: a map consisting of alternate representations of the `spoiler_text` property with the key being it's mimetype. Currently the only alternate representation supported is `text/plain` +- `expires_on`: a datetime (iso8601) that states when the post will expire (be deleted automatically), or empty if the post won't expire ## Attachments |