"Valve's attempt at a console-killer"? Really? No, this is Valve's panicked reaction to what had been the Xbox One's planned digital game sharing, which MS had to temporarily shelve while they re-wrote how the Xbox One handles disc-based games. If you don't remember, the Xbox One was originally going to let any console owner set 10 people to be members of their family sharing plan. Those "family" members (MS stated that they didn't have to be family), could then check out any game out of the owner's library at any time.
Here's the difference between the two plans:
Steam: If the owner of a shared game wants to play any game in their library, any person playing the shared game will be booted, even if the owner wants to play a different game than the one being shared. You are accessing a shared account, not a shared game. Also, Steam knows this immediately. The person accessing the shared library "will be given a few minutes to either purchase the game or quit playing." You can infer from this that shared gaming will not support offline mode... I.E., Always-on internet access is required to access a shared library.
Xbox One: The system treated shared games as a temporary license transfer. The library wasn't shared; individual games were. Your friend could play the game you lended to them without interrupting your play of any other game on in your library. To handle this license sharing, the Xbox One would, once per day, detect the status of the games and licenses on a console. Despite the constant FUD, the Xbox One *never* required an always-on connection. The requirement was for the console to be connected to the Internet at least once a day while the system did a license check for lended games.
So yeah, you can call this a great accomplishment by Valve and their "console-killer" if you want. You can hail the greatness Valve. But you have to ask yourself, why when Microsoft did it, were they burnt the stake and when Valve does it they're uplifted as a savior?
Exede user here. Here's my typical experience with my satellite connection:
My main issue with Exede is that it's DNS is flaky and sometimes requires me to cycle my network connection to fix. Even worse, it uses a proxy to hijack all port 53 DNS requests, so you can't choose an alternate server with the standard port. Netalyzr's log info on this:
UDP access to remote DNS servers (port 53) appears to pass through a firewall or proxy. The client was unable to transmit a non-DNS traffic on this UDP port, but was able to transmit a legitimate DNS request, suggesting that a proxy, NAT, or firewall intercepted and blocked the deliberately invalid request. A DNS proxy or firewall caused the client's direct DNS request to arrive from another IP address. Instead of your IP address, the request came from [Redacted]. A DNS proxy or firewall generated a new request rather than passing the client's request unmodified.
But other than that, it's still a *vast* improvement over the dial up I had for 15 years.
Credit ... is the only enduring testimonial to man's confidence in man. -- James Blish