Slashdot videos: Now with more Slashdot!
Where is the rest of the hardware teardown? All we are given is a single photo of a ribbon cable inside the phone, but none of
the shots of the chipset, PCBs, layout, etc.
More interesting still is the fact that the one (uninteresting) photo of the disassembly is named open13.jpg, implying that there
was an entire series of these shots, including juicy things like the processor, etc.
Why are these photos missing? Careless omission, or is something else going on here?
Just my $0.02.
This site is made to look like google's, but is LITTERED WITH ADS. The whois information reveals it's a third-party site.
The OFFICIAL chrome add-on site also does list an AdBlock extension, but something is fishy about it. When trying to install it, Chrome warns that "this extension is trying to access your data on api.flickr.com." What the hell?
We'll see if and how Google will try to combat these issues...
Of course, having a patent on this atrocious god-awful piece of work will effectively prevent other, less image-conscious vendors from doing similar things, which might mean (could it be?) less intrusive advertising on other platforms.
As for security, knowing your path to someone else isn't the issue. The issue is being able to manipulate that path (and others) at will. There are a number of hijacking, redirection, man-in-the-middle, etc attacks that rely on issues within the way IP packets are routed. In a circuit-switched system, like MPLS, the control plane basically lives in its own separate world and is essentially decoupled from the data plane (like with the phone network). That is, forwarding decisions are made based on an extra attribute connected to every packet (the so-called label ID) and not on some user-accessible field within the data itself. The only time that the user has access to this attribute is when specifying the "connection ID" associated with each outgoing packet, but that is strictly an agreement between the user and his serving router and has little relation to the upstream label tables.
The security benefit is that the routing mechanism is invisible to the end user. He needs to specify the destination and the rest of the connection is up to the network.
Of course, the other benefits are efficiency and traffic engineering. With the network being aware of the actual connections (unlike with TCP, where packets are essentially disjoint from a router's point of view), it is relatively easy to provide features like bandwidth reservation, QoS guarantees, etc. And the actual switching process for circuit switching is a lot more efficient. It is far easier for a router to perform a label lookup and then push/pop/swap labels than it is to carry out the longest prefix match lookup. In fact, such technology is already used internally by some ISPs, but it is not available globally or end-to-end.
The original design of the internet did not anticipate the need for isolated control, management, and data planes. There was just no reason to do it back then. But with 30 years of development and growth, things have changed...