Good morning Fediverse. The sky is gray and so are my thoughts.
Anyway, this post by @silverpill triggered me to look at media attachments in the Fediverse again 😭😭😭
This resulted in inputs#48 and a general state of despair. The situation could be nice. One could provide a recommendation on how to do media attachments. They could include stuff like the width and height of an image, that has been broken and reported in ActivityStreams for over 5 years. One could include a file size and digest, because one cares about bandwidth and integrity (ActivityStreams doesn't).
Instead one gets this and that. I'm not going to detail everything wrong about this. 🤷♂️ It would take more time than writing a proper specification document.
If you have opinions, in particular on the digest format and what to use to represent file size, please comment. A note on digest. digestMultibase
seems like a footgun to me due to the inclusion of the length byte. Not sure if there is something better.
@helge An alternative to digestMultibase is digestSRI (mentioned in VC spec), but digestMultibase seems to be more popular among VCDI spec authors and unlike digestSRI, it is now in security context.
Regarding width, height, digest and others: perhaps these properties should be added to
url
? One image may have multiple representations, for example low res and high res. IIRC PeerTube provides videos in multiple variants and has a long array of links inurl
.@helge An alternative to digestMultibase is digestSRI (mentioned in VC spec), but digestMultibase seems to be more popular among VCDI spec authors and unlike digestSRI, it is now in security context.
Regarding width, height, digest and others: perhaps these properties should be added to
url
? One image may have multiple representations, for example low res and high res. IIRC PeerTube provides videos in multiple variants and has a long array of links inurl
.