Changes

#* If your feature relies or uses networking to talk to some kind of centralized server, then it's probably going to get overloaded after your feature gains adoption in our large user base.

#* If your feature relies or uses networking to talk to some kind of centralized server, then it's probably going to get overloaded after your feature gains adoption in our large user base.

#* Deployers are likely to disable this part of your feature due to the painfully high latencies and costs of internet connections throughout the developing world.

#* Deployers are likely to disable this part of your feature due to the painfully high latencies and costs of internet connections throughout the developing world.

#* If networking is a core part of your feature then make sure it is replicable, e.g. on the OLPC XS school server. Make sure that this process is fully documented with support channels available. For reasons of cost, latency or simply lack of connectivity, many deployments will replicate the global infrastructure you have set up and use your feature exclusively on a LAN level.

#* If networking is a core part of your feature then make sure it is replicable, e.g. on the OLPC XS school server. Make sure that this process is fully documented with support channels available. For reasons of cost, latency or simply lack of connectivity, many deployments will replicate the global infrastructure you have set up and use your feature exclusively on a LAN level. If this is too difficult then they simply will not use your feature.

== How do I propose a feature idea, even if I can't build it myself? ==

== How do I propose a feature idea, even if I can't build it myself? ==