balas on Nostr: the year is 2025 and people still use .mov to share video content on the internet. ...
the year is 2025 and people still use .mov to share video content on the internet. This means they are uploading directly from their iPhone with probably little to no optimization at all. I blame this on the current media servers that allow direct upload and serve the file as is. Sure, the option to actually serve the original file is good but for the health of the ecosystem (and if they wish to actually scale), it would be better to perform some actions to the file and serve an optimized version instead. These files tend to be much higher quality than needed and cost a lot of wasted bandwidth and have much less compatibility. maybe we need NIPs with specific video encoding format
Published at
2025-02-11 15:03:54Event JSON
{
"id": "8538ec30f13b042f8b09655f3ace31b2a87fd664d8afa6c7e2b7957c1e8396ba",
"pubkey": "9ec7a778167afb1d30c4833de9322da0c08ba71a69e1911d5578d3144bb56437",
"created_at": 1739286234,
"kind": 1,
"tags": [],
"content": "the year is 2025 and people still use .mov to share video content on the internet. This means they are uploading directly from their iPhone with probably little to no optimization at all. I blame this on the current media servers that allow direct upload and serve the file as is. Sure, the option to actually serve the original file is good but for the health of the ecosystem (and if they wish to actually scale), it would be better to perform some actions to the file and serve an optimized version instead. These files tend to be much higher quality than needed and cost a lot of wasted bandwidth and have much less compatibility. maybe we need NIPs with specific video encoding format\nhttps://image.nostr.build/3193622ba87e2263bb1e10be8dd550a5da402f9cfd775995a1e6310034814b26.gif",
"sig": "f3f5a731bc4b15de96a5525642f9c291addfe696e1c420cf101e6c95ed778165089840dbefe29b990e13b921c6068c44d10edab504132de4cb2da57b8f759c01"
}