ringo2 on Nostr: I think its a function of how many users (how many relays each of those users is ...
I think its a function of how many users (how many relays each of those users is allowing to read events to) because each read and publish is equivalent to an http fetch, in your case of a nostr.build URL.
if even one person on one of those relays DL's the image, then that's a successful HTTP/OK. this isn't taking into account people who are fetching and not following a user, and just having the image display in global as they browse, which is also a fetch.
there's a lot of overhead that's inherently unnecessary, because of the way the protocol is designed.
it's really not that efficient.
actually come to think of it, it'd have been a lot easier to just build something like a lighthttpd server, and each person "builds a webpage" on their device and then posts go out, and you can control weather or not people who are your contacts can see the thing, OR if you want to broadcast to the whole web.
In fact I'm surprised it wasn't done like this in the first place.
if even one person on one of those relays DL's the image, then that's a successful HTTP/OK. this isn't taking into account people who are fetching and not following a user, and just having the image display in global as they browse, which is also a fetch.
there's a lot of overhead that's inherently unnecessary, because of the way the protocol is designed.
it's really not that efficient.
actually come to think of it, it'd have been a lot easier to just build something like a lighthttpd server, and each person "builds a webpage" on their device and then posts go out, and you can control weather or not people who are your contacts can see the thing, OR if you want to broadcast to the whole web.
In fact I'm surprised it wasn't done like this in the first place.