Thanks nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszythwden5te0dehhxarj9emkjmn99u0t7re4 as always. I’m happy to take a look and give some feedback. You should consider the GET side of this using range requests. This would assist in downloading larger files.
A rough draft of a BUD-10 for multi-part uploads to blossom servers. not sure if this is a good idea so I'm looking for feedback
https://github.com/hzrd149/blossom/pull/67
The biggest issue comes from the fact that blossom relies on the sha256 hash of the whole blob. so there isn't a way to verify that each uploaded chunk is part of a whole until the all the chunks are uploaded.
I think this issue can be mitigated slightly if the client includes `x` tags in the auth event for each chunk its uploading. so that the server can verify that each chunk was created by the client.
In the case of payments, I think it could be possible for the client to pay for each chunk. although this might require more requests or the server to define an x sats/bytes pricing.
Inspiration taken from https://tus.io/
Thanks to nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 for making me aware of it
Discussion
No replies yet.