Stuff needs to stop assuming "on wifi" = "I can use as much network bw as I like".
-
Show this thread
-
Better heuristic: ping something nearby, don't initiate any unrequested network access if > 50 ms.
1 reply 0 retweets 0 likesShow this thread -
Also use single large ping packet's latency to conservatively estimate available bw.
2 replies 0 retweets 0 likesShow this thread -
Replying to @RichFelker
is there a standard implementation for this for my hypothetical network-using app that doesn't want to reinvent congestion control itself?
1 reply 0 retweets 0 likes -
Replying to @__vlqc
I don't think so, and I don't think it makes sense if you're actually making good user-facing use of the bandwidth.
1 reply 0 retweets 0 likes -
Replying to @RichFelker @__vlqc
But if you're doing junk like downloading updates or package lists in the background, or worse uploading/syncing media to "the cloud"...
1 reply 0 retweets 0 likes
...then you really should be making an effort to determine if that's going to be detrimental to the network you're on.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.