@annika if it's images, https://jetpack.com/support/image-cdn/ may be handy. Also Google's appengine image store is quite useful for caching and scaling with a decent free tier. https://medium.com/google-cloud/uploading-resizing-and-serving-images-with-google-cloud-platform-ca9631a2c556
@cwebber so you still have to read char by char, constructing a number until you see a ':' then you read that many bytes as a data element? That seems oddly redundant - if you're scanning for delimiters anyway why do you . need the counts?
I've seen offset+tag counted files like IFF (WAV, AIFF, mov etc) when they're binary, and COBS that does it with octets http://www.stuartcheshire.org/papers/COBSforToN/
I'm not sure what the length + colon is providing compared to TSV or JSON
This person's question was answered like 12 times because Mastodon only shows replies from the federated timeline. A lot of the replies are from different domains, so people probably replied to a question they thought was unanswered. https://mastodon.social/@younesouhbi/99738093930667404
This, and the overhead of finding and following folks, are two of my biggest Mastodon pain points. I usually view toots on their home server before engaging, to see all replies.