make conversation-id deterministic #154

Merged

floatingghost merged 6 commits from conversation-id into develop

2022-08-06 20:59:16 +00:00

floatingghost commented

2022-08-06 20:49:14 +00:00

Owner

Basis from https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3717

floatingghost added 6 commits 2022-08-06 20:49:15 +00:00

Object: remove context_id field 662a9e7518

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.

CommonFields: remove context_id 520c78aa13