You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Microsub specification currently does not define a standard way of including an item's post type in a timeline response.
From what I can tell, there are currently some server implementations that include post type in their response, like Aperture in the post-type property, but there does not seem to be consensus on how to do this (mainly due to a lack of implementations).
Wouldn't it make sense to make this part of the spec? I would consider this a part of data normalization/transformation which is literally the purpose of a server.
I suggest we use a top-level field like _kind (to match _id, _is_read and _source) as a standard way to indicate post type, post-type seems inappropriate since post type is part of an items metadata and not a MF2/JF2 property.
The text was updated successfully, but these errors were encountered:
The Microsub specification currently does not define a standard way of including an item's post type in a timeline response.
From what I can tell, there are currently some server implementations that include post type in their response, like Aperture in the
post-type
property, but there does not seem to be consensus on how to do this (mainly due to a lack of implementations).Wouldn't it make sense to make this part of the spec? I would consider this a part of data normalization/transformation which is literally the purpose of a server.
I suggest we use a top-level field like
_kind
(to match_id
,_is_read
and_source
) as a standard way to indicate post type,post-type
seems inappropriate since post type is part of an items metadata and not a MF2/JF2 property.The text was updated successfully, but these errors were encountered: