Uploading images and videos on Mastodon is generally awful.
I can't count the number of times I've tried to post video at a live event, only to experience a complete failure to upload. Instead of being present and posting at the event, I'm fiddling with trying to get a 15 second video to upload at all. The shortcoming keeps me from being fully active on the platform, and reduces my ability to share with my community.
A large part of the problem is the cost associated with Digital Asset Management (DAM).
Whatever random Mastodon server I've signed up with has to absorb the cost of our uploads. That may be fine for someone in the weeds enough to run their own Mastodon instance – but it's a huge burden, such that even someone as deeply nerdy as I am is not willing to dedicate the time and attention to do it. My Mastodon server is good enough.
But I still want a better video upload solution!
Bring Your Own DAM
What if Mastodon provided users with the ability to configure personal asset servers? This would have several benefits:
- Shared Mastodon instances wouldn't be forced to absorb the cost of media hosting. This would make it easier for instances to stay afloat and rely less on community funding.
- People who post a lot of images and video can optimize their experience according to their own needs. My ability to post high quality video of any duration is only constrained by my own budget.
- Groups can come together to share in the cost of Digital Asset Management hosting. For example, a group of community reporters or avid photographers could go in on a DAM, sharing the cost, without also having to invest in all the nerdery of running their own Mastodon instance.
How it would work:
- A standalone DAM is provided, and has its own upload URL and an API token
- Mastodon provides a new "Digital Asset Management" settings panel where these two details can be entered
- When a Mastodon client posts, if any media is present, the client asks the Mastodon server for a single-use upload token. This token is then used to upload directly to the DAM, avoiding the Mastodon server entirely (routing around the Mastodon server is necessary because streaming media through the Mastodon instance would be a significant performance bottleneck).
Unfortunate intermediate nerdery: not all media servers support single-use tokens, and there is no standard contract for how these services work.
A relatively simple solution could be something like a minimal config, and easy to install Cloudflare Worker as an intermediary. The worker could handle the complexity associated with managing the single-use token and translating upload to S3, Cloudinary, Cloudflare Stream and Cloudflare Images (or even a DIY DAM with whatever technology you want, hosted from your closet!).
Middleware like this could act as a proof of concept to make the case to SaaS providers for a first-class Mastodon DAM API.
Beyond Mastodon
A generalized approach to BYO DAM on the Fediverse could make adoption of non-Mastodon apps more tractable as well, and make it easier for folks to really own their own content, and ensure it's highly available without offloading that cost on the community. Host your own long-form videos on PeerTube. Host your own hi-res photos on Pixelfed. Host your own shorts on Loops. Regardless of the specific Fediverse app, the same principle applies — let users own their storage, and the platforms become lighter and more sustainable.
