a9111bcaf2
This field seems to be a left-over from the StatusNet era. If your application uses `pleroma.conversation_id`: this field is deprecated. It is currently stubbed instead by doing a CRC32 of the context, and clearing the MSB to avoid overflow exceptions with signed integers on the different clients using this field (Java/Kotlin code, mostly; see Husky and probably other mobile clients.) This should be removed in a future version of Pleroma. Pleroma-FE currently depends on this field, as well. |
||
---|---|---|
.. | ||
account_view.ex | ||
announcement_view.ex | ||
app_view.ex | ||
conversation_view.ex | ||
custom_emoji_view.ex | ||
filter_view.ex | ||
follow_request_view.ex | ||
instance_view.ex | ||
list_view.ex | ||
marker_view.ex | ||
media_view.ex | ||
notification_view.ex | ||
poll_view.ex | ||
report_view.ex | ||
scheduled_activity_view.ex | ||
status_view.ex | ||
subscription_view.ex | ||
suggestion_view.ex | ||
timeline_view.ex |