RexSystem1 voteoriginally by @nekoame-git on GitHub1 reply
Agreed, I have the same idea: let the server backend automatically (or manually) upload media files that have exceeded a set expiration time to a self-hosted image hosting service (such as a NAS) via API, and automatically replace the original media file information with the corresponding image hosting link.
This can significantly reduce server storage pressure while ensuring that media files do not become completely invalid.
However, I think there is one issue: how to ensure the authenticity of the original media files is not compromised after replacement? Perhaps a warning message could be displayed near the replaced link after the change. This approach might be more suitable for private, entertainment-oriented self-hosted servers—at least, I would be happy to use it on my server.
RexSystem1 voteoriginally by @rogue-agent on GitHub
The api could give the main server the files MD5 for storage and then every time the file is being called from the user defined storage, the MD5 has to match.
Thread
Comment by @nekoame-git
Comment by @rogue-agent