Tag Archives: CASUAL


Notice: force_ssl_login is deprecated since version 4.4! Use force_ssl_admin() instead. in /var/www/vhosts/casual-dev.com/httpdocs/wp-includes/functions.php on line 3573

CASUAL Features – Full Disclosure


Notice: force_ssl_login is deprecated since version 4.4! Use force_ssl_admin() instead. in /var/www/vhosts/casual-dev.com/httpdocs/wp-includes/functions.php on line 3573

Notice: force_ssl_login is deprecated since version 4.4! Use force_ssl_admin() instead. in /var/www/vhosts/casual-dev.com/httpdocs/wp-includes/functions.php on line 3573

Notice: force_ssl_login is deprecated since version 4.4! Use force_ssl_admin() instead. in /var/www/vhosts/casual-dev.com/httpdocs/wp-includes/functions.php on line 3573

Notice: force_ssl_login is deprecated since version 4.4! Use force_ssl_admin() instead. in /var/www/vhosts/casual-dev.com/httpdocs/wp-includes/functions.php on line 3573

Notice: force_ssl_login is deprecated since version 4.4! Use force_ssl_admin() instead. in /var/www/vhosts/casual-dev.com/httpdocs/wp-includes/functions.php on line 3573

We at CASUAL-Dev try to keep things in the open. Our releases are open source, and we maintain a hands-off approach to releasing software. This ensures consistency. We have hundreds of thousands of users, and we use tools built into the software to manage this. There are some things that could be a potential privacy concern, or otherwise undocumented features that should be publicly disclosed though. That’s what this post is about.

Open Source
First off, we aren’t hiding anything. The CASUAL project is a totally Open Source and Open Build project. We strictly adhere to GPLv3 standards and maintain our releases on this site and http://goo.im/devs/AdamOutler. Anything downloaded from these sources is guaranteed to be created 100% in the open.

It all starts at the android-casual.googlecode.com Subversion server. Upon receiving a commit, GoogleCode notifies our Jenkins server that a new version of code is available. This triggers a build of Project CASUAL. A successful build of Project CASUAL causes several things to happen, including testing, building CASUALs with GUIs, uploading to various servers, and the rest of the jobs you see on this page http://jenkins.casual-dev.com/view/All/. Certain software, like JOdin3, is only built when a button is pressed.

In the event that we are contracted to write or work with others to write Closed Source software, the GPLv3 Copyright is waived and legal documentation is provided and kept on record here at CASUAL-Dev. Various parts may be added and removed from the software. We won’t disclose this information to our users, and you will never encounter any such software from the sources listed above (public WiFi networks under ARP spoofing attacks excluded). Everything on this site is built in the open. The only information we don’t share is our private code signing keys and log in credentials. We cannot share these keys for obvious reasons. However, we can point you at our Code Signing Certificate Provider, Certum.

Error Reporting

CASUAL features a “pastebin” or “report error” button in almost all forms. The point of this is to encourage users to use Pastebin rather than spam a 10 kilobyte log on the forums or Google+. This feature is really useful for determining problems in CASUAL. However, most users simply never report problems. In order to fix the problems, or even be aware of them, we need feedback. In order to compensate for a lack of user reporting, certain forms of CASUAL examine their own logs for keywords (like “error” or “failed”) upon shutdown. If these keywords are found, the CASUAL may send off an anonymous log to Pastebin. This all depends on the version of CASUAL, if it’s running in jar form, if it’s a known CASUAL developer (we don’t want our debugging logs.. If your computer username is Adam or Jeremy, we won’t be getting logs from you) , and the keywords we are monitoring. The “Anonymous Log” contains only an error report. User information is stripped out. The user’s name is replaced with “CASUALUSER,” and the user’s home folder is replaced with “USERHOME.” We use this data to search for and fix recurring problems. Currently, the only Anonymous Log Reporting that occurs is in the traditional CASUAL Java Desktop application. This way, we are generally aware of any problems and can stay on top of things.

If you’d like to read these logs, check out the CASUAL-automated pastebin here:http://pastebin.com/u/CASUAL-automated

Hit Counting
When CASUAL loads up, it searches for a CASPAC. And from within the CASPAC, it loads a script. The CASPAC is a package that can stand alone in ZIP or .CASPAC form, as well as serve as the contents of the CASUAL /SCRIPTS/ folder inside a JAR. Upon loading a Script, the UniqueID or other arbitrary factor is used to increment a counter at http://counter.casual-dev.com/?UniqueID.

Conclusion
As a CASUAL user, you should know that we use this information to improve your experience. As a CASUAL script developer, you can use this information to track usage and error statistics and make improvements. These statistics are considered vital information for this project, and we can make corrections using it. We strive to maintain the anonymity of our users and clients. If there is a problem with our methods, please raise a concern. CASUAL is in its infancy and will continue to grow over the years.

Share on Google+Share on FacebookTweet about this on TwitterShare on Reddit

Notice: force_ssl_login is deprecated since version 4.4! Use force_ssl_admin() instead. in /var/www/vhosts/casual-dev.com/httpdocs/wp-includes/functions.php on line 3573

Notice: force_ssl_login is deprecated since version 4.4! Use force_ssl_admin() instead. in /var/www/vhosts/casual-dev.com/httpdocs/wp-includes/functions.php on line 3573