Memo to nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqln5q8np5aezhtt7ztv6tah86xk4t3smjuchdvxp0u6uta056204qlatd70 (nprofile…td70) nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqdf6eyr7x6cv4gq99h3rjnhj6f4yqzxa97pxf2ecxeq82ea8mwdyqrp7epg (nprofile…7epg) on transcripts:
Apple Podcasts reads both VTT and SRT (if you don’t give them a VTT). Your SRTs are just fine.
My proposal was to suggest that full support of the transcript tag should be suggested to be simply “VTT”. That if you only support VTT (both publisher and client) then that’s full support of the tag. And if you do not support VTT, you do not support the tag. That’s all.
SRT, JSON, HTML, LaTeX, JPEG or any other transcript tag is still fine, and within the spec. But if you are not providing, or not consuming, VTT then you are not supporting it properly. By all means, send whatever else you want. But VTT is the minimum standard to claim full support for the transcript tag.
Right now, we’re all expected to support 4 different formats. My proposal simplifies the world for developers and for creators alike. It doesn’t stop anyone doing anything. It isn’t banning anything. It just makes it simpler. Happy to hop on a call to explain this if you’d like.
James Cridland
npub1g5…9t5sr
2026-06-13 03:57:51 UTC
Author Public Key
npub1g5h6rwmps922vx6m3rfj23r9wlkkp9dzrwefuyzfkjktqnfwvxasc9t5srSeen on
wss://relay.ditto.pubPublished at
2026-06-13 03:57:51 UTCEvent JSON
{
"id": "2c8ea648592937d1625ffdb01665f7a4e7cd3c0930a2b0fd46554ee7b8b8d713",
"pubkey": "452fa1bb618154a61b5b88d325446577ed6095a21bb29e1049b4acb04d2e61bb",
"created_at": 1781323071,
"kind": 1,
"tags": [
[
"p",
"fce803cc34ee4575afc25b34bedcfa35aab8c372e62ed6182fe6b8bebe9a53ea",
"wss://relay.ditto.pub"
],
[
"p",
"6a75920fc6d6195400a5bc4729de5a4d48011ba5f04c956706c80eacf4fb7348",
"wss://relay.ditto.pub"
],
[
"p",
"01b564093b88a80fa5269f27044e1dea1d832f56f9b40f2064a6ba39506f27e2",
"wss://relay.ditto.pub"
],
[
"p",
"0defbe4cf05d9acfedd61b9421e7cb6b72165b4e6749840320735a27d47e1447",
"wss://relay.ditto.pub"
],
[
"proxy",
"https://bne.social/users/james/statuses/116740788830421048",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "Memo to nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqln5q8np5aezhtt7ztv6tah86xk4t3smjuchdvxp0u6uta056204qlatd70 nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqdf6eyr7x6cv4gq99h3rjnhj6f4yqzxa97pxf2ecxeq82ea8mwdyqrp7epg on transcripts:\n\nApple Podcasts reads both VTT and SRT (if you don’t give them a VTT). Your SRTs are just fine.\n\nMy proposal was to suggest that full support of the transcript tag should be suggested to be simply “VTT”. That if you only support VTT (both publisher and client) then that’s full support of the tag. And if you do not support VTT, you do not support the tag. That’s all. \n\nSRT, JSON, HTML, LaTeX, JPEG or any other transcript tag is still fine, and within the spec. But if you are not providing, or not consuming, VTT then you are not supporting it properly. By all means, send whatever else you want. But VTT is the minimum standard to claim full support for the transcript tag.\n\nRight now, we’re all expected to support 4 different formats. My proposal simplifies the world for developers and for creators alike. It doesn’t stop anyone doing anything. It isn’t banning anything. It just makes it simpler. Happy to hop on a call to explain this if you’d like.",
"sig": "4e89039c1122bb472bf54d7912af720a818ecd713d143a6871bf737264bc2bf18bb7aea8a3363740d6f05bda6f487d712939205355904f3686dfc83db25f3985"
}