MorrisonFilm: TinyDouche
I agree with this 110%. These are my exact sentiments. The troubling thing is that there is obviously something TinyGrab is not telling us.
The guys over at TinyGrab are running a clinic on how not to handle a crisis.
A few weeks ago, TinyGrab’s servers were apparently hacked, and because of that they released new, untested software that completely doesn’t work. This makes no sense. They claim that due to someone accessing and “corrupting the kernel” (really?) of their servers, they had to completely abandon TinyGrab 1.0’s server-side codebase, as well as completely invalidate the client applications immediately.
I’m not sure I understand why this was necessary at all. If your server gets hacked you undo the damage, repair the codebase from your repository, increase/modify security, patch any holes, and you’re back to the races. If your client application needs modifications because of changes to security on the server-side, issue an update through regular channels. This could be done and solved in relatively quick time, depending on how much code needed to be updated. You can even force users to reset their passwords if necessary.
Instead, TinyGrab threw a perfectly functional client app away entirely, they removed all of their 1.0 code on the server, and they released new 2.0 versions of their client applications which aren’t at all production ready. The Mac version of the app doesn’t support even half of the functionality of the 1.0 app, and the website is a complete shambles. Most people cannot log in (including myself), and it’s total garbage.
Here’s the ridiculous thing: I paid for the TinyGrab “premium” features (a one-time unlock fee) so that I could use FTP support and have my screenshots uploaded to my own server. Guess what feature is completely missing from TinyGrab 2.0? That’s right—FTP uploads. So when TinyGrab switched over to this new, shitty client app, they completely removed the only feature I use. Well, that’s helpful!
