Updates for OS X Mountain Lion


© Image by Apple, Inc.

OS X Mountain Lion

OS X Mountain Lion has hit the shelves on the Mac App Store and it’s off to a very good start.

So where are the updates for Yoink, ScreenFloat and flickery?

For all of my apps, I’ve submitted updates to the App Store at the beginning of July but they’re still “In Review” or worse, “Waiting for Review”. Here’s the run down of what’s working or not working on OS X Mountain Lion.


Yoink works perfectly fine in the currently available version (2.1.1). The upcoming update is a bugfix and minor feature release.
Nothing really changed for Yoink in OS X Mountain Lion that would break the app.


ScreenFloat has some minor issues. It works well, but you’ll notice that the “Launch ScreenFloat at Login” checkbox in the preferences is enabled although it shouldn’t be and will crash the app when clicked.

Another issue is with running ScreenFloat with the Dock icon enabled. Floating shots will not follow you to fullscreen apps or spaces. I’m currently looking into that. In the meantime, you can disable the Dock icon and it will work.


flickery is the most troubling. Not because of OS X Mountain Lion (some minor issues aside – like, the “Nearby” search doesn’t show up – it works well).

The troubling part is that flickr is shutting down their flickrAuth authorization mechanism by July 31st. Yes, that’s very soon and there’s no update out yet for flickery.
I’ve requested an expedited review by Apple for it and I hope they grant it.

If they don’t (and still, if they do, there’s a chance), it might take longer than July 31st for Apple to review the app. What that means is that authorizing flickery to work with your flickr account will not be possible. Also, although flickr doesn’t explicitly state this, it’s inferred that anything done over the flickr API with an old authorization token (an authorization token is what an app receives from flickr when the user authorizes the app to work with their flickr account) will not work anymore. So browsing, uploading, really anything you can do with flickery, will not work.

Please be aware that the upcoming update does include the new OAuth authorization and will make flickery work again with flickr. Until it is reviewed and released by Apple on the App Store, please have a little patience. I know it’s not ideal, but at this point, I’ve done all I can do.


aside from some minor issues with ScreenFloat and flickery, everything basically works on OS X Mountain Lion. For these issues, updates are currently “In Review” or “Waiting for Review” by Apple and should be released soon.

As for flickery, I’ve requested an expedited review and I urge you one more time to consider having a little patience 🙂 Trust me – it troubles me more than anyone.

Thank you for your time,
Take care,


[twitter-follow screen_name=’eternalstorms’ show_count=’yes’]

[twitter-follow screen_name=’flickeryapp’ show_count=’yes’]

[twitter-follow screen_name=’screenfloatapp’ show_count=’yes’]

[twitter-follow screen_name=’gimmesometune’ show_count=’yes’]

8 Comments, RSS

  1. Hi there. I’m looking for a new photo uploader for flickr because the unpredictability of iPhoto’s sync is a bit too scary for me. (It’s coping photos from flickr to my hard drive that I uploaded years before I started using iPhoto which is causing duplication on my hard drive.)

    Anyway, I read about flickery in this thread: http://www.flickr.com/groups/76164876@N00/discuss/72157623763615744/ and it sounds like it could be a solution, but I have two queries.

    1. I don’t know anything about the Apple review process or flickr’s authorisation mechanism, but is the issue you’ve described above just a matter of time before it’s resolved, or does it mean that now that July 31st has passed flickery just won’t work any more?

    2. If it does work, I’m curious about its ability to let you browse, organise and manage your existing flickr collection. Is this just a software interface for flickr’s website (making all the updates online), or is it actually downloading the images back to your hard drive (which I want to avoid)?

    Many thanks in advance for your help, sorry for my noobie questions!

  2. Mathos

    Ah okay, I thought it was troublesome, testing it right now, and will respond back if there are issues that I encounter.
    Kind regards, Mathos.

  3. I too am experiencing problems with Yoink. While it is running over a prolonged period of time, but not being used, it gradually eats up my CPU cylces until my system is completely frozen, requiring a forced restart. I’m running the most current version of Mountain Lion and the current available version of Yoink. I can’t use Yoink if this is the result. I can watch its CPU footprint gradually grow in the activity monitor. I noticed one other user had a similar problem, but only when apparently copying images from Firefox. I’m experiencing this without copying images from anywhere.

  4. Hi there! I’m at work browsing your blog from my new iphone 3gs! Just wanted to say I love reading your blog and look forward to all your posts! Carry on the outstanding work!