@hongminhee I can't find a spec (although I'm bad at finding specs), but they add the quoteUri
field (from http://fedibird.com/ns#
) to notes, with the id of the quoted post, along with a source
field that's an object containing content
(with the original content) and optionally mediaType
(with the media type of the original content)
@Tak Oh, thank you for letting me know!
@hongminhee @Tak other software also sends them as tags in the ap object
I do both tbh just in case
@gabboman Can you name software that works like that? I'd like to test it out!
@hongminhee You can use FEP-e232 in combination with quoteUrl
property (there are other properties like quoteUri
and _misskey_quote
but they are supported by fewer projects).
@silverpill Oh, thank you for providing the link!
@silverpill By the way, do you know any implementations that use the `quoteURL` property?
@hongminhee No. It was mentioned in Threads announcement but I think they actually meant quoteUrl
@silverpill @hongminhee FEP-e232 is a standardized generic framework for microsyntaxes including, but not limited to, "quotes", but does it standardize any concrete link relation for quoting? The convention to use `https://misskey-hub.net/ns#_misskey_quote` as the `rel` value isn't standardized by the FEP nor Misskey Hub, I think?
Also, note that Misskey doesn't support it (both incoming and outgoing), so its support isn't overwhelming yet number-of-end-users-wise (Misskey happens to have the second largest server in the Fediverse)
@silverpill @hongminhee Seems like the URI fragment is missing for some reason… I meant `/ns#_misskey_quote`
https://misskey-hub.net/ns#_misskey_quote
type has not been standardized yet. I think this relation type and other things related to quotes (such as quotes
collection) should be specified in a separate FEP.
>note that Misskey doesn't support it (both incoming and outgoing)
Yes, but Misskey and Pleroma support quoteUrl
property (IIRC it is defined as as:quoteUrl
). FEP-e232 + quoteUrl should work everywhere