the tradeoffs with hosting your own images and videos are that if you want others to see it, you can't really just use a server. you have to start using big tech CDN (content delivery networks that cache everything at the edge where its close to who is downloading it). otherwise it all loads at modem speed and nobody will see it. this is why nostr build is fast. and im sure you could do this with immich or anything you just need amazon or cloudflare or some other CDN. you can even have real one time urls and all kinds of fancy big tech nicetys ..

but yeah, not really something i want to do for others but i do it for myself all the time.

Reply to this note

Please Login to reply.

Discussion

i mean, if i thought i could get any normie to signup for aws i could provide tooling for things, but generally.. they won't.

what would be awesome is an app that fires off the requests to the giant CDN which is a cache with resolution converters, and a blossom front end, and it fetches them from other blossom servers. then the self hosting would be seeding and the main delivery is the big cache.

this is kinda what you would want to do. except also with awesome transcoding and processing. im not convinced blossom will be enough because of this, more like multi-blossom. each video needs like 6 diff versions, and then those all need to be shipped to a CDN.

or, give users something to look at or a video game to play while it takes 2min to download your 10 second clip.

a CDN with a GPU on it could stream the transcodes just in time and background process other versions. it could also run a subscription scheme based on the events to proactively cache new content. maybe blossom is not the right protocol, it is content addressable. extend it maybe, with query strings or some other protocol extension.

the point would just be to allow self hosting of content but scalable delivery.