RFI: How does reticulum resolve handle media such as models from reticulum.io?

[ipeakermit]

I'm trying to understand why reticulum fails to resolve/load a URL through the API at https://codi15.dyndns.org:4000/api/v1/media on my self-hosted hubs instance. It seems to hinge on the MediaResolver resolve method, media_resolver.ex at around line 124, not finding an appropriate resolve clause for an URL pointing to reticulum.io. Presumably there is a generic resolve clause that should apply, but which one is it? The URL in question is https://uploads-prod.reticulum.io/files/728260ab-4e8f-4052-8e1a-c7fae3492989.glb and is requested by Spoke, but rejected by reticulum, causing Spoke to fail. Should my self-hosted Spoke not load from reticulum.io? What is the expected resolve handler for files at reticulum.io?

[brianpeiris]

In theory your server ought to be able to load files from reticulum.io, so I'm not sure why it's failing.
Arguably, the root cause of this issue should be fixed in Spoke, since we probably should not hard-code reticulum.io URLs in the default Spoke templates (https://github.com/mozilla/Spoke/tree/master/src/assets/templates)