msbhvn

Please do it, I'm very biased but I think there would be lots of interest in seeing all that explained in one place in a coherant fashion (you will likely sharpen your own understanding in the process and have the perfect resource for when you next need to revisit these topics).

Woah, read the timeline at the top of this. The fire happened the very day the government ordered onsite inspection was supposed to start due to Chinese/NK hacking.

To paraphrase Bob Metcalf, “I don’t know what will come after Ethernet, but it will be called Ethernet.”

In Peru debit cards don’t have names on them. So you just go to a branch and they take an unused one off the stack and assign and hand it to you. 5 mins, any branch, no appt. Quite convenient. Credit cards do have your name printed on and those you pick up at a branch when they arrive.

I guess the US considers the printed name to be more important for debit cards.

Seems like they provide an autossh+GUI subscription service that maintains reverse port forwards? If you do not have a public ssh host to connect to then this is an option.

Things being how they are and the app being Chinese, I guess I would need more convincing on why I should trust them first.

I did read it, guess I just got too caught up in the title to brush it off (looks like some others here also wondered about that).

Anyway, uTP looks cool, LEDBAT sounds very interesting and BitTorrent is of course, completely awesome. I just don't think TCP sucks. I'm constantly surprised at how well it works for how simple most of it is and how complicated and intractable the rest is.

Just to be clear, "TCP Sucks", despite successfully running the majority of the global Internet traffic. "TCP Sucks" so bad we're basically going to copy a lot of it: window based congestion control, SACK, timestamps, ability to add new options, etc. "TCP Sucks" because it is not perfect and has an issue, an issue that requires router / switch upgrades. We're going to fix that by breaking backward compatibility with _tons_ of applications and requiring an OS update on _every_ client and/or application. All this assuming our relatively new and unproven thing is as good as TCP in all other ways and fixes this issue of TCP perfectly.

Hmmm. Me thinks that TCP does not suck so much.

So Apple gets attacked for not allowing their OS to run on non-Apple hw and Google gets attacked for allowing their OS to run on non-Google hardware? (I realize they're actually being criticized for now having their own device here, but just another perspective). I guess you could just not have your own hardware, since that's working so well for WinMo.