Well I have an average connection for Europe and i could easily support two gigabyte blocks from home, eight megabyte blocks would not be a problem at all. This person in Florida needs to either get a new internet provider or update his client by the sounds of it. lol
Did you read my posts in this thread? I've had to drastically reduce the connectivity of my full node (latest Core release) running on it's own dedicated hardware (modern quad-core CPU, 16GB RAM, SSD) in order to keep the home network functional for other daily use demands.
My node will happily eat as much upload speed as I give it and I have top 10% home internet speeds (probably better). It can bring simple web surfing to a standstill if I let it.
Nodes don't just accept blocks. Most of my bandwidth use is on the upload side (sharing data with other peers)! Larger blocks will obviously have a direct impact on the amount of data shared.
Do you run a node or are you just guessing?
should bitcoins traffic limits be based on what 10% of typical home connection can handle?
maybe 20% ? maybe 50%? surly anything demanding 20-10% isn't going to impact number of full nodes.
in anycase i feel that there can be much improvement as to how data is shared across the network to dramatically decrease bandwidth use for full nodes, which should allow for proportionally bigger blocks.
I know someone that turns on his full node like once a week, just to download the lastest blocks and then turns it off again, so that when he makes a TX it doesn't take him long to sync up first. is this node useful? should ALL users be asked to run a full node?
Bitcoin traffic should be limited based on capacity of anonymous bandwidth growth.