mleku on Nostr: the gossip model will have such a large amount of traffic it will use up relays VPS ...
the gossip model will have such a large amount of traffic it will use up relays VPS bandwidth allocations quickly and the delay with which the network synchronise would get longer with the log (2) of the number of users posting to it. keep in mind that this outbound traffic will also compete with users posting traffic as well.
even if you make that more efficient with a kademlia DHT based partition resistant broadcast, the thing is that relay users are not necessarily going to request all the content that is sent to them in this manner, and this is going to consume resources needlessly and ultimately slow down the synchrony of the network (time between publishing and all readers getting their subscriptions delivered), as well.
FOREST enables a publish/subscribe model to efficiently enumerate and request demanded notes from other relays, and not just notes, it can enable also media and other files, and not just the whole files, but pieces of them.
IPFS could achieve the same thing but its merkle trees are massive and people would jam them so full , and then it would also have the very same broadcast propagation inefficiency, and the same high cost of making missing piece requests.
the rockstar devs who think they are gods at the top of the trending feeds think that FOREST is the same as IPFS, they literally said as much and this is why they are shitting all over Robin and Colby's work, even resorting to straight up harassment and trolling.
it's not. it enables publish-subscribe efficiency without centralisation. think like fully open Kafka or Dynamo.
as a cloud dev you would be familiar with these things and why achieving them in a decentralised way is a big deal for Nostr.
even if you make that more efficient with a kademlia DHT based partition resistant broadcast, the thing is that relay users are not necessarily going to request all the content that is sent to them in this manner, and this is going to consume resources needlessly and ultimately slow down the synchrony of the network (time between publishing and all readers getting their subscriptions delivered), as well.
FOREST enables a publish/subscribe model to efficiently enumerate and request demanded notes from other relays, and not just notes, it can enable also media and other files, and not just the whole files, but pieces of them.
IPFS could achieve the same thing but its merkle trees are massive and people would jam them so full , and then it would also have the very same broadcast propagation inefficiency, and the same high cost of making missing piece requests.
the rockstar devs who think they are gods at the top of the trending feeds think that FOREST is the same as IPFS, they literally said as much and this is why they are shitting all over Robin and Colby's work, even resorting to straight up harassment and trolling.
it's not. it enables publish-subscribe efficiency without centralisation. think like fully open Kafka or Dynamo.
as a cloud dev you would be familiar with these things and why achieving them in a decentralised way is a big deal for Nostr.