nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpzfmhxue69uhkummnw3e82efwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9emkjmn99urf278z do you think #Blossom adds something, to this media-manager use case?
We just implemented Blossom in #Alexandria and I'm curious what it could be concretely good for. 🤔
Seems like a media manager would be the right place to add it, but I'm not sure how.
Maybe, but only for publicly sharing media. The thing with sha256 hashes is they are forever, at least as long as someone has the file on their server.
For a personal media management server I think it could make sense if blossom support could be turn enabled on a per file basis. but only so that the user could share it to nostr or another public website.
I was looking into this a little and I have a half finished fork of https://github.com/9001/copyparty locally that has blossom support for specific directories
If the user is just looking to quickly share a baby picture with a friend then there isn't a need to include the sha256 of the file in the URL (blossom) because in that case the user only wants the file to be accessible for a short time
On the other had if the user is running a blog (nostr or something else) then they probably want their media to be accessible and mirrored by as many people as possible. in that case blossom fits perfectly
I'm going to do the sharing with the event wrappers, and they can have expiry dates. Then you could use normal URLs for expiring ones and Blossom for long-term linkage. Or something.
