ToothlessRebel writes: "I have been reading, and thinking prior to that, about thin-client computing and applying to more every day usage of computers. In both a question to those running the infamous LAN centers, and an exercise in computing experiments, what sort of limitations are there on these thin clients? They typically seem to run an embedded OS designed to get most of its information from a sever. How much computing do these devices do? Does graphical processing limits these devices, or because they are displaying whatever 'the brain' sends, can that be done server side? Suppose your school ran thin clients as its public terminals, for power concerns or whatever reasons, must you use specific versions of everyday applications like Mozilla Firefox, or would the server just have to handle perhaps hundreds of seperate Firefox processes?
VORNAN-20 writes: Yesterday's item here about Comcast screwing around with P2P traffic brings up an idea. Is it time to change the P2P standard to encrypt all traffic? I think that almost any current PC would have no problem handling the extra load, and really, Comcast or any ISP has no business knowing what you are sending in the first place. I am not a network guy but I think that this is doable. If azureus, ktorrent, etc were all to come out with an "encrypt all packets using " option maybe this could be managed quickly and cleanly. It would be best to move quickly before all of the ISPs catch on to this. Come on developers, liberate us from the network meanies!!