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.
oh .. the thing i forgot was:
---with fragmented sharing the throughput from a user is much less personal and much less meaningful and memorable. and of much lower quality, VS a person designing a webpage and talking about their actual passions and interests and taking the time to think about it.
versus the dynamic of --nostr-- which is just like going to a bar, and vying for attention, people tend to lose focus on themselves and focus on impressing others.
which imho is stupid. (it also results in much much higher webtraffic.) and this last point, is something the people really don't grasp and cannot be expected to grasp unless they are educated about network topology, albeit in a simple way.
well I pay for 10tb out...
but no if you do the rough figuring it kinda works like this:
]
- user uploads image.
-10-30 relays pull that image and store it.
so each jpg or png stored is roughly going to inflate 1,000-3,000%.
if you start running imagemagick if you aren't doing that already on your front-end, then that would be a great help.
but overall, the protocol is broken in the way it's designed,
and what will happen eventually is the only people that will be able to actually run relays successfully when nostr scales are literally big data operations with millions of dollars...
i am almost 95% certain this is inherently by design.
there's actually nothing great about the "decentralized architecture," as it is currently posited.
there goal of "publish to the web" in a social sense isn't really attainable, there is no logical reason the entire internet needs a permanent record of what someone publishes. ever.
the http protocol did this already fairly well, but then the last 15 years of "smart" encroachment and lack of technical folks making decent tools for people to create basic websites, made this all fall flat.
we need another thing like geocities, imho.
it's a much better way to share things than in real time and fragmented attentionspans.
--- fragmented attention sharing focuses on risk/reward/ego stroking, versus supplication and sharing of personal identity, goals, morality and ethics, and is short lived, and highly temporal.
anyway just some thoughts..
okay so i have a blog right? sometimes when i post a link on nostr for a blog, i get over 1,300 hits to that article. i don't know if it's pulling all the media ( could look at apache logs but havent gotten that drill down just yet)
it just appears things are growing.
part of the problem with object storage and "cloud compute" is you can't really access real server logs like you can with apache and a traditional environment.
such clues lead to not having to guess as to what is actually drawing the bandwidth, and from where.....
ps this is #[2] via an alt.
lol. you gotta be vaxed for most dayjobs around here.
i do this >> when people order, I have a dayjob.
if yall wanna zap me i dont have a dayjob and all zapps are appreciated :) lol <3
every few years, I find a valid reason to pull this song out.
This is one of those reasons.
https://www.youtube.com/watch?v=71PNZH1OaW0
The Dead Milkmen - Stuart
too difficult. just get a nip05 i dont think bots can do that yet :)
https://www.youtube.com/watch?v=DS0hSP-3U14
The Beta Band - dry the rain
it's a different client for nostr called more-speech. I wanted one i can use on the linux desktop, so im trying it out. it's new, but it's interesting. what you're looking at is the feed... but its everything the relays im connected to are picking up, versus a following list.
I'm trying to figure out how to add that, so I don't have to look at this tab instead, beacuse it's too confusing.
cc: #[2]
#[6]
nothin wrong with yours!
so far the ones i liked the most were #[8]
and #[4] .
:)
oh cool okay :)
:) interesting that they take bitcoin, thats rad. what city or region of the world you in ? (this is ringo) trying to learn a new client but concurrently trying to wrangle it into place using iris to copy npubs.
okay now to figure out how to get more speech to stop choking itself out by loading EVER frigging event that comes in on the relay..