No I haven't played around with that. I've attempted in the past but I ran into something that was keeping it from working the way I was doing things. I'll have to look into it again sometime soon.

Anyhow... Inactive projects can be cleaned up, that's no problem. A restructure to make things more well organized could work as well, but it would depend on what the other admins thought. Branching out is also an option, but again, I'm not sure how popular that would be. We do already have sections for no calc dev. Maybe that could just be restructured a bit?

Do I sense a volunteer to do the work of cleaning things up?

If the user has JS disabled the password will be sent as-presented to the server and will be handled there, the user still gets to log in.

Sounds good. So it's just more secure to leave JavaScript enabled on the site

This should serve as a big reminder for admins to be very careful with their login credentials. If possible, use two factor authentication. If not, consider changing your password every so often.

It appears probable that plaintext passwords were stolen as well, so be aware of that. My and geekboy's accounts elsewhere were both attempted compromised elsewhere. Change your password.

Edit: It's also worth pointing out that if plaintext passwords were stored or logged somewhere, you should NOT change your password to anything you use elsewhere, because nothing about password storage has changed.

We shouldn't have had any plaintext passwords. It looks like SMF doesn't salt+hash their passwords in a very secure way. Sorunome is looking into cleaning that up.

Luckily it looks like the damage was contained to Omnimaga's database itself and they didn't get at any of our other databases or anything. There is a lot of data they can sort through though and possibly some personal information.

I search source because I would ported to Ti 83 Premium CE

Porting to the CE would require a major overhaul. It would take less time to just rewrite it. Especially since we don't have the app signing keys for the CE and we'd have to rewrite it as a group of programs.

The only thing that I see wrong is a bunch of syntax mistakes, which I guess you didn't directly copy and paste this from some IDE. If you move the last line to the top though, there doesn't seem to be any errors. It works perfectly fine when I tested it on wabbit. Here's a file that should work for what you have.


Also, just some stuff, you should probably close your parenthesis since that doesn't make it faster or smaller, only improve readability, and use DispGraphClrDraw instead of them individually, makes it a lot faster.

Due to how limited memory is on a calculator, you would usually forgo readability for smaller size code. It's recommended in Axe and Basic to drop the tailing quotes/parenthesis and save space due to them being implicitly added by a newline. When posting the code for others to read it's totally fine to add them in, but when actually storing them on calculator, every extra byte of space is needed.