server/activitypub: restructure follow & follow requests #350
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The
following
andfollow_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 aFollowing
object that is created before the request is sent. Currently this is not possible because theFollowing
is only created after theFollowRequest
isAccept
ed, and theFollowing
andFollowRequest
object have different IDs.