| NETI@home IS NOT SPYWARE |
| FOR RESEARCH PURPOSES ONLY |
| Home | | | Download/Installation/Uninstallation | | | Use | | | Research | | | Privacy | | | Screenshots | | | Support |
English  |
Chinese  |
Hopefully, most of your questions will be answered here. However, if you need further assistance, please contact the NETI@home team, and remember to include useful information such as the version of NETI@home you're running, your OS, and all other information that you can (a log of the error if possible, etc.).
The log file is not created until your client reports back to the NETI@home server, which occurs after you have had approximately 300 Internet connections. While this number may seem large, it was chosen to reduce the amount of traffic to the NETI@home server and you would actually be surprised to realize how quickly you can have 300 Internet connections ("flows"). The decision to create the log file only when the server is contacted was made to demonstrate that user privacy is protected -- the log file contains exactly the same data that is sent to the NETI@home server. However, I realize that the log file viewer could fail a little more gracefully, and make the above explanation a little more clear. Rest assured that this will be included in NETI@home in the very near future.
The use of firewalls and/or NATs does not seem to affect NETI@home and we are able to determine both your local IP (ie 192.168.0.x) and your external IP, if your privacy setting allows.
It appears that a patch for the Windows operating systems has removed the jview and wjview programs, do to a recent lawsuit. As a solution, try downloading Java from Sun here.
NETI is an acronym for "NETwork Intelligence" where intelligence is used in the information-gathering sense.
The creators of NETI@home are huge fans of the SETI@home project, as well as many other distributed applications. NETI@home was certainly named after SETI@home with much respect. In fact, SETI@home and most other distributed apps use spare CPU cycles, unlike NETI@home which must process while there is network activity. While such benchmarking and other testing has not been formally completed, we do suspect that the use of NETI@home would not significantly interfere with the use of SETI@home or similar apps.
NETI@home IS NOT SPYWARE
Website design and development provided by Charles Simpson (Robby).
Layout Copyright © 2003-2006 Charles Simpson (Robby). All rights reserved.