Plugin Progress

I had a chance to do a lot more work on my watermark plugin this weekend and I made lots of progress. Most functions work, but I still need a few days of QA & testing before I can release it.

Success!
Uploaded with plasq‘s Skitch!

Black Star Rising tells why you should add your name and copyright notice when posting a photo, which is the reason I wrote this. I noticed that almost all of the pictures by the professionals from last week’s photowalk have a copyright notice, so I wanted to make it easier to do with Aperture.

links for 2008-06-27

Protecting your photos

After seeing how my blog posts have been republished without my permission, I realize that the same thing is likely to happen with my photos (and most likely already has happened). Most photographers add a visible watermark or copyright notice to identify their photos. Although Aperture can embed a copyright notice and author info in the EXIF data, it doesn’t have a way to add a visible identification.

One way to do it is to edit in Photoshop and add a text layer. As an alternative, I started to write an Aperture editing plugin that can add text to a photo. I hope to have it ready for public release next week.

Watermark
Uploaded with plasq‘s Skitch!

WordPress 2.6 to disable client access by default

Daniel Jaikut reports that WordPress 2.6 will disable the Atom & XMLRPC protocols by default. These APIs are used by applications such as MarsEdit to let you post from your desktop. If you want to use a desktop blogging app, you need to go into the settings and explicitly enable remote posting. Hopefully, upgrading an old WordPress site will keep it enabled.

The developers feel that those APIs “expose a potential to be a security risk“. As far as I know, none of the recent WordPress attacks have involved XMLRPC.

I almost never make a blog post through the web interface; I do all of my blogging with MarsEdit (which I’m now using to write this post). I’m sure the majority of serious bloggers use a desktop client such as MarsEdit or Ecto rather than the web interface, so this will be an inconvenience for all but the most casual users. Since many people will re-enable XMLRPC, any security improvement will be negated.

A better solution would be to require a client key, as Flickr does, which you need to explicitly allow before that client can post to your blog.