+
+
+
+No. When using EnvayaSMS, you connect it to your own web server. +The EnvayaSMS Android app does not connect to envaya.org or any third-party servers. +In particular, you do not need to register for envaya.org. +
+ ++For information about configuring a web server to connect to EnvayaSMS, see the API Reference page. +
+ ++We originally developed EnvayaSMS to enable civil society organizations in East Africa to interact with +envaya.org via SMS and MMS, such as by posting news updates and photos +to their website. +
++We realized that EnvayaSMS would be useful for any web service that needs to send and receive SMS/MMS, +and decided to make EnvayaSMS available for anyone building their own applications. +
++Development of EnvayaSMS is currently led by the envaya.org team, +but anyone is welcome to contribute to improve it. +
+ ++The source code for EnvayaSMS was originally based on KalSMS, an open-source project +started by Nir Yariv in 2010 that introduced the idea of a simple SMS gateway implemented entirely as an Android app. +EnvayaSMS is a complete rewrite that shares little code with KalSMS. +
+ ++EnvayaSMS builds upon the idea of KalSMS by adding many new features that would be necessary for anyone deploying an SMS gateway in the field, +such as sending more than 100 messages per hour, authenticating the phone to the server, and retrying forwarding messages after transient errors. +For a complete list of changes, see the History page. +
++EnvayaSMS's server API is incompatible with that of KalSMS. Anyone switching from KalSMS to EnvayaSMS must +update their server to use the new API described on the API Reference page. +
++ As of 2011, KalSMS is no longer actively developed, and new development will occur on the EnvayaSMS project. +
\ No newline at end of file diff --git a/.phrozn/entries/history.twig b/.phrozn/entries/history.twig index c1ab8a2..bbd1acf 100755 --- a/.phrozn/entries/history.twig +++ b/.phrozn/entries/history.twig @@ -53,12 +53,12 @@ Version 2.0-beta (2011/09/22)+No. When using EnvayaSMS, you connect it to your own web server. +The EnvayaSMS Android app does not connect to envaya.org or any third-party servers. +In particular, you do not need to register for envaya.org. +
+ ++For information about configuring a web server to connect to EnvayaSMS, see the API Reference page. +
+ ++We originally developed EnvayaSMS to enable civil society organizations in East Africa to interact with +envaya.org via SMS and MMS, such as by posting news updates and photos +to their website. +
++We realized that EnvayaSMS would be useful for any web service that needs to send and receive SMS/MMS, +and decided to make EnvayaSMS available for anyone building their own applications. +
++Development of EnvayaSMS is currently led by the envaya.org team, +but anyone is welcome to contribute to improve it. +
+ ++The source code for EnvayaSMS was originally based on KalSMS, an open-source project +started by Nir Yariv in 2010 that introduced the idea of a simple SMS gateway implemented entirely as an Android app. +EnvayaSMS is a complete rewrite that shares little code with KalSMS. +
+ ++EnvayaSMS builds upon the idea of KalSMS by adding many new features that would be necessary for anyone deploying an SMS gateway in the field, +such as sending more than 100 messages per hour, authenticating the phone to the server, and retrying forwarding messages after transient errors. +For a complete list of changes, see the History page. +
++EnvayaSMS's server API is incompatible with that of KalSMS. Anyone switching from KalSMS to EnvayaSMS must +update their server to use the new API described on the API Reference page. +
++ As of 2011, KalSMS is no longer actively developed, and new development will occur on the EnvayaSMS project. +