search

hzrd149 / blossom

Blobs stored simply on mediaservers
The Unlicense
55 stars 6 forks source link

Why? #6

Closed fishcakeday closed 2 months ago

fishcakeday commented 2 months ago

Why create yet another (and not even standardized) method to upload media? Are you planning to submit this as a PR for the NIPs repo? Was this well-thought-out? Was there a need? This just further creats fragmentation on already highly fragmented protocol. Did you think of scalability, reliability, resiliency of this approach? Costs? Implementation? Do you plan for it to be used only by sole individuals? Larger hosts? What is the point?

hzrd149 commented 2 months ago

to answer your questions in order experimentation, no, kind of, yes, yes, yes, a little, yes, no, yes, everyone, yes, content addressable files

fishcakeday commented 2 months ago

NIP-96 does content addressable content already, all it needed was an add-on to server non-media files, and it was good to go (if you needed other things than audio, video, image). In fact, you can already use it to do that. This is just a shortened and less descriptive copy of it.

ibz commented 1 month ago

Indeed, this feels a lot like NIP-96. I was also thinking, what is the point? I guess we'll have to wait and see which one gains more traction...

ibz commented 1 month ago

NIP-96 does content addressable content already

It does not, actually.