[bug] denying follow requests from rejected instances does not work #338

New Issue

Open

opened 2022-12-04 18:56:27 +00:00 by nyancrimew · 1 comment

nyancrimew commented

2022-12-04 18:56:27 +00:00

it would probably make sense to either automatically purge frqs from rejected instances or purge them from the list once manually denied, even though the remote interaction fails

if a user gets a follow request from an instance that gets added to a reject MRF after the request is received but before it is acted upon it is impossible to ever deny the follow request, making it forever stuck in the follow request list. it would probably make sense to either automatically purge frqs from rejected instances or purge them from the list once manually denied, even though the remote interaction fails

Ghost commented

2022-12-04 19:07:57 +00:00

I think this might be solved somewhat by #334, but that's just for purging rejected FRQs daily and might be better UX to handle this case specifically

I *think* this might be solved somewhat by https://akkoma.dev/AkkomaGang/akkoma/pulls/334, but that's just for purging rejected FRQs daily and might be better UX to handle this case specifically

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#338

No description provided.