How bad is the idea of people contributing alternative URLs to images published in notes using a special event and clients loading these when the primary URL fails?
Discussion
Example:
Bob publishes a kind:1 note: "look at this image: 
"
Alice publishes a kind:789 with tags:
["e", bob's note]
["original", ""]
["alternative", "
"]
I came to say that images.com is also blocked in Iran.
Until the next fact
Doesn't this mean that Alice could:
A: ddos Bob's media source and harvest the ip addresses etc of Bob's followers.
B: ddos Bob's media source and spread false information by high jacking Bob's media.
What could be the main use case of this backup?
You got to hash the image so no one can alter the original intent or add exploits to the image. The hash can be looked up on cacheable media, e.g. IPFS
If URIs were wrapped as a magnet š§² then additional mirrors could simply add to the URI array.
This would ensure copies share the same hash,
The bonus is clients could also act as mirrors in a swarming scenario with WebRTC
For a muggle it sounds confusing š„¹
When I first joined Nostrā I looked up how to change my cover photo on Damus (as much as I respect ostrichesā I knew I could not look at them everyday on my profile) so used some type ofābuildā image thing to get a link to plug in. I wish I would have saved how I did thisā wondering if this is what you mean. nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac did I see you share something related?
Sorry if Iām off in my own worldā lol
What if the alternative image is something completely different?
#NIP-96 discussion - using #multiple #content server locations for jpg gif mp4
I would limit the alternative image to the original pubkey, to avoid a "content attack" to falsify the original.
Think of what could happen if tomorrow nostr.build went offline (I wish you long life!), chaos.
Or at least give priority to the owner of the note.
You can trust some people to provide faithful alternatives. You definitely shouldn't accept any alternative from anyone.
I don't understand why integrating torrents isn't a thing.
Apple doesn't allow for torrent apps in the app store, so integrating torrent in damus wouldn't go through. But nostr isn't damus and I'm sure someone will integrate (something like) torrent in a nostr client/app sooner or later.
There could probably be a "leech" service (free or paid), through which one could translate torrent to a "regular link".
One can imagine a torrent-like video service "back end" where the social interface is nostr and if you want to watch, you pay sats per MB. Also if you seed you get paid. Some free/sponsored streams possible if someone sponsors them.
These ideas are not new for sure. Just waiting for the right implementation.
I know it would be a āforkā for relays, but could it be integrated at that layer? Sats / MB would be good incentive for a relay to want to integrate it if the user wanted to pay the relay to host a file.
Also
"you should see this, I'm sponsoring you one view or x MB direcly likned to your npub, expires in 24h"
"y'all shoul see this! I'm sponsoring x GB of streaming so you can watch it for free"
"advertising :)"
...
I am not sure why original URL would fail. I am more of a content creator rabbit making images than a tech rabbit. This is a new warren, but I am curious, what if they where published on PiƱata?
Better than nothing, but ideally we would have some way for the original note to commit to a hash of the image, to avoid malicious replacements.
Mirror links? How important is this for pictures and gifs do you think?
Seem like a pretty weak system. Even if you only trust alternatives from people you follow, how are the those people supposed to know what was at the original URL? Providing these alternatives seems like a highly specialized task that is likely to be done by relays or other third parties which makes it even worse. Only trusting the original author to provide alternatives is a little better. But how is your non-technical grandmother ever going to understand who to trust in this scenario?
Content-addressed media is the solution we really need but I donāt see an easy way to get it adopted.
I agree. Something that can be embedded directly in the original note with a hash and multiple alt urls would be much better.
Sounds easy to Sybil attack by posting unrelated image. Perhaps the original note should commit to the image's hash?
Thereās also the case where the link just turns bad and is out of your control. E.g. when using link shortener and they recycle the urls.
Now, your image may point to completely different picture (or 404).
If thereās no image hashing/UUID signed by the author this does not sound very solid solution.
What would it look like to have ephemeral asset URLs?
Can the links be assigned and maintained dynamically / periodically enabling moving assets from one domain host to another.