@!
Zap Kind of an informal poll. How bad do folks here want the Mastodon API so we can support more client apps? There's always the "microblog vs. conversation" issue to deal with, but to me the issue with the most importance to most of you is how much information we cache from the network. For a **single user** site with aggressive expiration this is like to grow from about 3-4GB to somewhere around 10GB (not counting your personal cloud storage requirements). For larger sites it will grow proportionally more.
The reason is the Mastodon API sort of forces every site to download the cover/banner photo as well as the profile photo for every foreign channel that is seen by your site; just to determine if it's animated or not. And then provide two copies (one static) if it's animated. Currently we cache all profile photos, but this would be a significant increase.
I'll invest the effort in doing this if that's what folks want, but just want you to be aware of the hidden costs.