Fabio Manganiello on Nostr: image formats for sharing what is supposed to be plain-text content (or Markdown at ...
image formats for sharing what is supposed to be plain-text content (or Markdown at best) are an accessibility nightmare - not to mention how they make content less searchable/discoverable, and how they affect performance (a few KB/MB of JPEG/PNG content exchanged instead of a few bytes of text).
> Besides plain text, I’m not aware of a good meaning-embed rich-text preservation standard for snippet exchange.
Well except for Mastodon, intra-platform quotes are supported by basically every social platform out there. They all offer a way of sharing/quoting a post, which will be fetched and rendered at runtime when the quoting post is rendered.
But Mastodon doesn’t support quotes for ideological reasons, and all other platforms don’t support quotes/embeds outside of their own walled gardens. So we’ve ended up with the proliferation of screenshots to fill the gap.
From a purely technological perspective, I don’t see the reason why the response to a query to a link within a post couldn’t be rendered as some kind of multipart form, with an attachments field containing a list of payloads, content types and roles (e.g. body, quote, media…).
It doesn’t even to be an ActivityPub thing, it’s simple enough that all platforms could adopt it tomorrow if they want, and enable posts to be shared and quoted consistently across all of them.
Published at
2024-05-27 11:46:52Event JSON
{
"id": "fcddd98ec30680ec09c126615ccb6d751b40e9910c1675172549284ae1668ca5",
"pubkey": "8179879e743ecc0b539b67420e7dc29a1f097751a00fa1c74d3cea319465223b",
"created_at": 1716810412,
"kind": 1,
"tags": [
[
"p",
"8179879e743ecc0b539b67420e7dc29a1f097751a00fa1c74d3cea319465223b"
],
[
"e",
"0da92529dfe131151a980cbcd670276fc11ce8a6cc3f33ddc86a93c52c4fb491",
"",
"reply"
],
[
"p",
"d704f0ae435f081465cf287c52be636b181c21270bd937b1fab7b62e973d05db"
],
[
"e",
"3b8222adbe4584ef06851942a8994f1a1fd1021f5ff4fc4be9d1d310a99ecbc9",
"",
"root"
],
[
"proxy",
"https://manganiello.social/objects/c90c6380-8451-41bc-8c12-37cb166218fa",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://manganiello.social/objects/c90c6380-8451-41bc-8c12-37cb166218fa",
"pink.momostr"
]
],
"content": "image formats for sharing what is supposed to be plain-text content (or Markdown at best) are an accessibility nightmare - not to mention how they make content less searchable/discoverable, and how they affect performance (a few KB/MB of JPEG/PNG content exchanged instead of a few bytes of text).\n\n\u003e Besides plain text, I’m not aware of a good meaning-embed rich-text preservation standard for snippet exchange.\n\nWell except for Mastodon, intra-platform quotes are supported by basically every social platform out there. They all offer a way of sharing/quoting a post, which will be fetched and rendered at runtime when the quoting post is rendered.\n\nBut Mastodon doesn’t support quotes for ideological reasons, and all other platforms don’t support quotes/embeds outside of their own walled gardens. So we’ve ended up with the proliferation of screenshots to fill the gap.\n\nFrom a purely technological perspective, I don’t see the reason why the response to a query to a link within a post couldn’t be rendered as some kind of multipart form, with an attachments field containing a list of payloads, content types and roles (e.g. body, quote, media…).\n\nIt doesn’t even to be an ActivityPub thing, it’s simple enough that all platforms could adopt it tomorrow if they want, and enable posts to be shared and quoted consistently across all of them.",
"sig": "62dbdf46d15648a473e22182465bb6a97d9bdc984128c674a5a1218c29978e34a7bc584c5389a3327a5847d1b074db044138fe5a7c73eeec4d3b5bcaeaca7663"
}