server/activitypub: restructure follow & follow requests #350

New Issue

Open

opened 2023-02-26 22:52:37 +00:00 by Johann150 · 0 comments

Johann150 commented

2023-02-26 22:52:37 +00:00

Owner

The following and follow_requests table should be merged. Both tables have the same fields except for "follow_requests"."requestId". This field could be used if nullable to distinguish between a requested and a completed follow.

This would also allow to change the ID generation mechanism for follows to use the ID from following. This would be possible because there is an ID of a Following object that is created before the request is sent. Currently this is not possible because the Following is only created after the FollowRequest is Accepted, and the Following and FollowRequest object have different IDs.

The `following` and `follow_requests` table should be merged. Both tables have the same fields except for `"follow_requests"."requestId"`. This field could be used if nullable to distinguish between a requested and a completed follow. This would also allow to change the ID generation mechanism for follows to use the ID from `following`. This would be possible because there is an ID of a `Following` object that is created before the request is sent. Currently this is not possible because the `Following` is only created after the `FollowRequest` is `Accept`ed, and the `Following` and `FollowRequest` object have different IDs.