nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj you speak matter of factly but those aren’t facts tho
Discussion
the cost of administration (aka consensus) is the problem, how do you prove it...
Right. So we’re in agreement? Good.
If the only issue is that the economic model of “pooled services” has yet to be proven. OK fine.
As long as the two solutions (as implementation possibilities) DO solve for the same problems in this space, then NIP bloat can be minimized. (Remember that one?)
i personally have been reorganising the whole structure in my code to fit an imperative programming model and it breaks down pretty nice for the most part... there is a few parts of my code that still use nip codes but i could think of reasonable names for them
nip1 is bloated as fuck, and i reject the numbering system, it's dumb, i think that it should be explained via short names, 1, 2, at most 3 words to express what a thing does
this makes it alot easier for people to understand and a lot easier to architect as a programmer
no, there is no way to make relaying cheaper to implement, the fact is that it's pretty cheap really, like, my test relay, over about 3 weeks now it's accumulated a whole 20mb of data, which includes all posts that make reference to mine, and i have some, idk, primal says i have 300 followers... so all their kind 0s are in there too most likely, but idk, those are probably the biggest individual events you find on the network
oh yeah, and that dates back 3 months of my activity too... so if you calculate on each user costing about 20mb/month of data you are looking at a pretty low cost to host 400 of them, i pay about 5 euros a month for a VPS that would handle that
i haven't worked out the payment system yet... currently working on a chat-bot based control system for admins and owners and i think it probably won't be much to add an interface in there to allow subscriptions, maybe a couple of weeks i'll have most of this implemented