silverpill on Nostr: nprofile1q…dksj0 >most server implementations (Mastodon, Misskey, etc.) don't ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqpqruw808pyr6vnuj50qu45v4pkhc36umgvjascsnyz90w78wmngqhdksj0 (nprofile…ksj0)
>most server implementations (Mastodon, Misskey, etc.) don't properly handle this content as of April 2025
How multilingual content should be handled, in your opinion? Specification doesn't provide any guidance on that matter.
>I'm considering several approaches:
I'd use (2) as primary representation and (3) as fallback.
(1) is fine too (FEP-e232 links could be used instead of inReplyTo, if top-level posts are preferable).
(4) should be avoided, because such content will be rendered as a long post with no clear boundaries between translations. I don't think <hr> is a good solution, and it's not widely supported (m).
>most server implementations (Mastodon, Misskey, etc.) don't properly handle this content as of April 2025
How multilingual content should be handled, in your opinion? Specification doesn't provide any guidance on that matter.
>I'm considering several approaches:
I'd use (2) as primary representation and (3) as fallback.
(1) is fine too (FEP-e232 links could be used instead of inReplyTo, if top-level posts are preferable).
(4) should be avoided, because such content will be rendered as a long post with no clear boundaries between translations. I don't think <hr> is a good solution, and it's not widely supported (m).