maybe we could use comm's system

did a little brainstorming in planning, we might need a separate system for translating short-lived strings in a smaller time window

Resolving, will reopen if the crash appears again in HockeyApp

I can see the code that changed it, unfortunately I'm not seeing a large difference in memory usage. NSCache (infamously) omits any guarantee that it will evict objects once the count limit is exceeded. And after browsing many POTD and several articles, I should have easily hit 50 images and started to see things level off. Resolving that the work was done, but it's unclear if there was any significant improvement.

@JMinor need access to Google doc w/ screenshots

some formatting tweaks and updated the "Feedback" instructions. Also, our "feedback" mechanism is really, really buried. At the very least we should make it a button in Settings (instead of a link at the bottom of the "About" page).

More like a performance enhancement

so in the app store, the app would just pick one

@JMinor @Josve05a this isn't a crash, it's an assertion since normally (when there's only one image "displayed"), we only expect to get one visible image. however, in this case we could just pick the left-most (or right-most in RTL?) or disable chrome interaction entirely while scrolling

Also, strangely fitting how that title stays at the top of the list... Damn robots

Aww I actually clicked on that one :-(