forked from mirrors/akkoma
3cb471ec06
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. |
||
|---|---|---|
| .. | ||
| bbs | ||
| config | ||
| conversation | ||
| emails | ||
| fixtures | ||
| http | ||
| integration | ||
| object | ||
| plugs | ||
| support | ||
| tasks | ||
| upload | ||
| web | ||
| activity_expiration_test.exs | ||
| activity_expiration_worker_test.exs | ||
| activity_test.exs | ||
| bookmark_test.exs | ||
| captcha_test.exs | ||
| config_test.exs | ||
| conversation_test.exs | ||
| emoji_test.exs | ||
| filter_test.exs | ||
| flake_id_test.exs | ||
| formatter_test.exs | ||
| healthcheck_test.exs | ||
| html_test.exs | ||
| http_test.exs | ||
| keys_test.exs | ||
| list_test.exs | ||
| notification_test.exs | ||
| object_test.exs | ||
| registration_test.exs | ||
| repo_test.exs | ||
| reverse_proxy_test.exs | ||
| scheduled_activity_test.exs | ||
| scheduled_activity_worker_test.exs | ||
| signature_test.exs | ||
| test_helper.exs | ||
| upload_test.exs | ||
| user_invite_token_test.exs | ||
| user_search_test.exs | ||
| user_test.exs | ||
| xml_builder_test.exs | ||