aboutsummaryrefslogtreecommitdiff
path: root/config
diff options
context:
space:
mode:
authorHélène <pleroma-dev@helene.moe>2022-08-06 03:24:31 +0200
committerHélène <pleroma-dev@helene.moe>2022-08-09 20:10:43 +0200
commitf3e061c9645571997a01b1091d0e8a3f68c6bb21 (patch)
tree8e1affaa297de59dba8c81172bd82a685ff99ced /config
parent7de21ec9910ef5d2fa36cb6335c25bed67ebc3a4 (diff)
downloadpleroma-f3e061c9645571997a01b1091d0e8a3f68c6bb21.tar.gz
Object: remove context_id field
30 to 70% of the objects in the object table are simple JSON objects containing a single field, 'id', being the context's ID. The reason for the creation of an object per context seems to be an old relic from the StatusNet era, and has only been used nowadays as an helper for threads in Pleroma-FE via the `pleroma.conversation_id` field in status views. An object per context was created, and its numerical ID (table column) was used and stored as 'context_id' in the object and activity along with the full 'context' URI/string. This commit removes this field and stops creation of objects for each context, which will also allow incoming activities to use activity IDs as contexts, something which was not possible before, or would have been very broken under most circumstances. The `pleroma.conversation_id` field has been reimplemented in a way to maintain backwards-compatibility by calculating a CRC32 of the full context URI/string in the object, instead of relying on the row ID for the created context object.
Diffstat (limited to 'config')
0 files changed, 0 insertions, 0 deletions