Filters API: expires_in/expires_at not supported
Mastodon docs have expires_in
field during create/update and expires_at
field during fetching.
Actually, expires_at
always null with any expires_in
specified. I also tested it on Mastodon intance https://indieweb.social/ and it is working as documented in docs.
Pleroma FE don't use it, but it is part of the Mastodon API so I think it should be implemented or documented as API difference at https://docs-develop.pleroma.social/backend/API/differences_in_mastoapi_responses/
Tested on 2.2.50-708-gbe7a76ab
Create filter example request
POST /api/v1/filters HTTP/1.1
{"context":["notifications"],"irreversible":false,"phrase":"aaa","whole_word":false,"expires_in":205975}
Response
{
"context": ["notifications"],
"expires_at": null,
"id": "1",
"irreversible": false,
"phrase": "aaa",
"whole_word": false
}