QUOTE ("Samaels Ghost")
It seems to me that the complex mesh network of commlinks and nodes within densely urban areas would provide near free wireless access to all participating parties. Anyone with a wireless device in 2070 could use this ubiquitous mesh network to bypass their Matrix Service Providers' infrastructures.
Actually, this is exactly how it works. (Unwired, p. 42 under 'Getting the Hook Up') MSPs in the 2070's no longer simply provide access (as your personal 'link generates part of the network they use, it's probably counted as a trade-off - otherwise, they might have to pay you for the use of your node), they, as the name says, provide users with matrix services (software, storage, database management, etc.).
QUOTE ("Samaels Ghost")
I'm just curious whether the corps can charge for superfluous infrastructure? I see the money-grubbing corps pulling stunts like preventing other corps' comms from getting their traffic routed through their networking electronics, forcing consumers in areas dominated by one MSP or brand of comm to switch to that company's product or else get crappy connectivity.
I think the main reasons they don't do this is that the Corporate Court doesn't allow them to. I believe an open, neutral network was part of the Wireless Matrix Initiative.
As to 'why'... primarily because it's bad for business. As a mesh network, the wireless matrix relies on the individual user nodes as well as the backbone nexi to ensure network continuity and fast, reliable data routing. Blocking content from particular devices or certain sources would be counter-productive. Not only do you create vulnerabilities in the the network (hackers only have to write malicious code targeting one brand of device to affect a large portion of the network), and slowdown (your traffic can only pass through certain devices) but, more importantly, you keep your own content and services from reaching the widest possible consumer base (if you're blocking stuff, you competitors are blocking you, too). And there's also the matter of purchasing versus licensing. If people are buying their hardware from you, you no longer have the right to interfere with their use of it after the fact. If you want to try and sell a crippled product (the user knows they'll only be able to access Aztechnology-made media, say) or enforce a licensing-based model (they're not buying the hardware, only leasing it - so you can control it as you see fit), that's one thing - but market pressures will tend to favor the devices with the wider range of available content.
QUOTE ("")
There's a couple of things I can think of that might be interesting to explore. Instant mesh-network-routing is quickly passed over in Unwired. Its implications aren't very thoroughly explored, I think. Maybe I'm wrong.
It is largely glossed-over, as far as fine technical details go (seeing as it's a make-believe technology, this is only to be expected). But it is explained pretty well, I thought. Data packets pick up ID tags from each node they pass through. And responses are given priority routing through the same nodes on the way back. The MSPs keep massive databases of registered and active device IDs, so if a given node in a sequence is out of range by the time the data returns, it just passes through the next available device in a given area and then on to the next node in sequence. But given the processing speeds they're dealing with, the likelihood that all of the devices in a given route would be unavailable at a given moment are slim enough (and node density is high enough) that this system works.
There might not been too many implications of this to explore, because it goes on to explain that all this routing business is happening on a level that the end-user (metahuman or otherwise) doesn't have access to. It's either inexcessable because that's just part of the protocol, it occurs too quickly for manipulations to be feasible, or because it's too fundamental to the operation of the whole process. It seems the most you can do to affect it is setting your commlink mode (hidden mode probably disables the routing function, for example).