On Mon, Dec 28, 2015 at 1:09 AM, Luca Matteis <[email protected]> wrote:
> On Sun, Dec 27, 2015 at 6:41 PM, Miguel Freitas <[email protected]> > wrote: > > Then post is automatically refreshed between nodes, for about 2 months. > > Interesting. Is that handled by the DHT algorithm (say Kademlia)? > > No. afaict the only refresh implemented in standard bittorrent's DHT is to keep the routing tables fresh, not the contents. > I was wondering how well it all performs against spam attacks. For > instance I could literally spam the network with millions of spam > tweets and then the network would be trying to serve those millions of > tweets for 2 months. Does that hurt the network? Can the network > handle that? > Well, first thing to consider is the size of the network. The larger the twister network the more resilient. With current size, some attacks that wouldn't make a different might be noticeable. That said, the DHT refresh is also limited in both duration and bandwidth used. So when bandwidth limit is reached, some requests are dropped. But everything is probabilistic, 8 nodes are supposed to be able handle requests for any given DHT resource... skipping some refreshes due to your spam attack would be enough to put legit contents to expire? I don't know. Give it a try ;-) regards, Miguel -- You received this message because you are subscribed to the Google Groups "twister-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
