[Idea] FASP spec for local and/or remote storage

[shleeable]

Goal: There services handling remote cache de-duplication when connected to multiple instances for shared benefit.

https://github.com/Timshel/s3-dedup-proxy is a port of Jortage to Scala (and I'd imagine we could add a FASP API endpoint) to handle any spec on top of that tooling.

Please engage with Tim if you find value is appending the FASP api... but I figure you might build your own reference design in another language.

• Remote Storage FASP host - A mastodon instance can add one or many FASP service to host/serve a copy of their remote cache
• Local Storage FASP host - A mastodon instance can add a FASP service to host/serve a copy of their primary files. This doesn't require deduplication because it's only unique files (unless the host is also offering remote cache for other instances).

A remote storage FASP is an excellent use case for FASP... I believe we should consider a standard format to handle the file hashing and paths to multiple version of this to offer hosting services... and be easily switched up without any outages or migrations required for remote cache.

[shleeable]

Renchap has a lot of interesting things to say about this which I 100% agree with... this cannot come soon enough