@sam is working on this now so we should be able to get
image://vaLFE+HaBPe06ZIwhR6iqv64zE4.png
vs
//assets-meta-cdck-prod-meta.s3.dualstack.us-west-1.amazonaws.com/original/3X/d/8/d813b1138aa816ad87eeeebf55af33ebf3c66cf0.png
which I, at least, view as a substantial quality of life improvement for day to day image handling in posts.
(note that we’ll need to use base62, to avoid the / and + chars in URLs though)
