Since posting yesterday about my new Dropbox-based photo management system, I’ve gotten several repsonses like this one from @sgo on App.net:
The one thing I don’t like about managing photos that way is you’re paying for storage twice…Dropbox and your backup service.
I pay $10/month for a 100 GB Dropbox Pro account. My photos currently take up just shy of 38 GB of that space (which is actually 118 GB thanks to referrals). If I ever need to pay for the 200 GB plan, I have no problem doing so.
Daniel W on Twitter has Hazel working to do what my AppleScript was doing.
Genius stuff.
Update: Turns out, this too can be done with Hazel. My script isn’t necessary.
Earlier today, I wrote about how I’m using Dropbox as my photo management app. I closed with this:
This setup doesn’t harness PhotoStream, however, so I still have iPhoto setup to catch those images, just in case I don’t import something by mistake.
Turns out, importing images from Photo Stream into the folder Hazel watches to rename them can be automated, too. Here’s how I did it:
Viticci just wrote up a nice post outlining his move from iPhoto to Dropbox.
After reading it, I started to think about why I continue to suffer with use Aperture. I rarely use it edit my photos, and really prefer it over iPhoto just for the organization in to projects.
So, I’ve made the jump to join Mr. Smooth Hands on Dropbox.
I used Automator to export my library into a folder, with a sub-folder for each project. Automator named each file with the following scheme, based on file creation time:
Back in May, I wrote:
I’m keeping Evernote for PDFs and images I need offline. For the most part, these files are work-related, such as plans for the building that we’re currently constructing.
My notes, however, along with non-essential files, are back in Dropbox. It just feels … cleaner. Plus, I get to deal with plain text files, which is my preference on any platform.
Since then, I’ve been further tinkering with my Evernote setup, and this is where I’ve landed in the “Evernote or Dropbox” debate:
This is the best iPhone client for App.net yet. It’s fast, support multiple accounts and is better looking that most of the apps I’ve seen in beta.
$4.99 might seem steep, but remember, we all already paid ADN $50.
Good for Apple. Developers that try to confuse customers by using an icon of a better, well-known app on their own work should be punished.
Way to meet the needs of your Mac customers, Adobe.
Tweetbot developer Tapbots has announced that it has pulled its very popular alpha Mac app from release due to the new caps on maximum users that Twitter recently said it would begin enforcing. The developers have tried to work with Twitter to come up with a way to have the alpha not eat up the limited amount of slots available to them, but says that Twitter has been uncooperative.
Drafts 2.0 for iPhone and Drafts for iPad are out.
Building on the excellent 1.0, the new version of Drafts adds features like more font selection, more output options and a neat full-screen mode.
The most interesting feature is syncing, though. Using the Simperium engine, Drafts for iPad and iPhone can share text via the cloud. It’s crazy fast.
If you’re a Drafts user, buying the iPad version is a no-brainer. If you’re not using Drafts yet at all, shame on you. You really are missing out on a great little app.
Sounds like the perfect solution to use with Arq.
If you’re using RVM to manage Ruby on your Mac, and wish there was a GUI tool to do so, this might be right up your alley.
via Kevin Lipe