@matigo Yep. I was also pretty darn busy at work, but I had to drop all my work and go to the dentist immediately.
Almost forgot to tell you… Today, while at work, I decided to eat a nut before I went to lunch. It was a pretty hard nut, so I had to use quite a lot of force to crack it in my mouth. Well, as you might guess, that didn't end well. I fractured one of my teeth, and had to go to the dentist. Luckily they had to just take the fractured piece out and fill the missing part of the tooth. Had the fracture been larger the whole tooth would have been pulled off.
@matigo Google is a source of all kinds of semi-proprietary (or semi-open, depending on how you see the world) ways to do simple things.
@matigo I see a lot of knee-jerkery from Android developers regarding the tools, but I'm with you, none of the development environments is superior. All of them are crap. Heck, all platforms are nothing but crap. It's all about what crap one is ready to tolerate when choosing the platform.
People hate Xcode, but the latest Android Studio's been seriously fucked up for me. The grass isn't green on this side of the fence either.
@phoneboy I still haven't completely understood what I need to do, but it seems that CloudFlare has pretty good tutorials.
// @matigo
@c Pretty much. I believe there was an idea behind that obfuscation, but in practice there's no need for it at all, especially because it caused this nasty bug.
Squashed a nasty bug by simply not obfuscating the variable that was used to create the directory for cached images. When the app was put into background, the app cleaned directories that were not related to any "active" magazines, causing that offline image directory to be wiped clean. When I removed the obfuscation, the clean-up code was able to associate the directory with an active magazine, thus keeping the cached images intact.
Damn it. Didn't mean to do that. Well, let it be there, just for the sake of showing my mistake. :-)