photos – Climb to the Stars

Moving From Apple Photos to Adobe Lightroom Classic CC [en]

God have mercy on me. A few months ago I decided I was coming back to Lightroom. Now is the time to actually move my stuff out of Apple Photos and into Lightroom. It’s not so much emptying Apple Photos that concerns me as transferring albums, favorites, and editing over to Lightroom.

I had foreseen the headache, and so I am documenting what I’m doing here first of all for myself (because I might end up abandoning halfway through, as usual, and picking up six months later, having forgotten everything), and also for other poor souls out there who might be in the same situation.

First, the easy part: exporting from Apple Photos.

One thing I wanted to “export” was my albums. I went through each album I wanted to keep, selected all the photos in it, displayed information and added a keyword like “my cats album” to all the photos. Kludgy and a little tedious, but does the trick.
When viewing photos Apple lets you display “only edited” photos. This allowed me to export both the edited photo and the unmodified original for photos I had edited in Apple Photos. I then exported the unmodified originals of photographs I hadn’t touched in Apple Photos separately.
I exported these photos into three separate folders, without any subfolders: “Apple edited”, “Apple originals”, “Apple unedited”. I renamed the edited photos to avoid file name conflicts later on, but left the originals/unedited file names untouched, in the hope it would help Lightroom detect duplicates/updated photos later on.
For the original files, I told Apple Photos to write IPTC to XMP. This works great for RAW files (Lightroom grabs the metadata from the XMP sidecar) but not for JPG originals (who are not supposed to have a sidecar). After fumbling around I found my solution: a simple command-line command for exiftools. The person posting had pretty much the same problem as I did, and I just used the solution offered as-is. It throws some errors (when XMP files don’t have anything interesting in them, I think) but works fine.

Now for the real fun: importing into Lightroom.

For this, I used a temporary working catalog, rather than mess up my master catalog directly. I made the working catalog by exporting some photos as a catalog from the master catalog, and then removing those photos from the temporary catalog (not the files though, beware!)
I started with the edited photos, followed by their original files. I moved them into a month-based folder structure parallel to the one I use for my main library (in a folder called “Apple import”). Upon importing, I gave each batch a keyword to be able to figure out who was who later on (“appleedited” and “master of apple edited”).
I ran Find Duplicates 2 on those photos and it turned out quite a pile of them. Not that surprising. I decided to have a look, and saw that there were indeed a lot of “edited” photos that were so close to the original (or unimportant) that I wasn’t going to bother importing a bloated redundant JPG of those “edits”.
I proceeded to cull those “duplicates”. I started out by giving all those photos a keyword to recognise them later (see how I abuse keywords?). I then rejected all the “mess” (screenshots, photos of bank statements…) that comes with exporting photos from your phone.
I then went painstakingly (but as efficiently as possible) through the unflagged photos and used a label to identify those where I was indeed going to keep both the edited version and the master. I could have skipped this but I figure less bloat is better.
Amongst the unflagged and unlabeled photos with the “duplicate” keyword, I filtered for those with “edited” in the file name (remember how I renamed the edited photos upon export from Apple Photos? handy; I could also have used the keyword I attributed the edited versions upon export, come to think of it. Oh well.) I rejected all those edited photos I decided not to keep.
Similarly, I selected the originals for those photos and changed their keyword to indicate they were not a master photo for an edited version anymore. I also removed the duplicate tag and then cleaned up my mess of coloured labels.
I am not deleting any rejected photos until I get everybody back into my master catalog. Hopefully this will clean up a bit of the “smartphone mess”…or not.
I then proceeded to import the photos from Apple Photos which hadn’t been edited. Just 20k of them. It was loooooong.

Now… how to merge all this back into the master catalog without losing any information and without multiplying photos excessively… I’m not sure I have the solution, and I’m going to err on the side of not losing data. I can always hunt for duplicates later.

I picked a year where I had only a couple of hundred Apple photos, and exported a working catalog from the Apple import catalog for only that year. I then imported those photos into my master catalog, without moving the files. To my dismay Lightroom didn’t recognize any as duplicates or updated files. After looking at things manually it’s clear there are duplicates and I was very wise to not try and move the files to their right place in the catalog yet (filenames are identical!)

I set Find Duplicates loose on all the photos for that year. As I’ve previously cleaned up my whole catalog of duplicates, and marked “fake duplicates” with a keyword that allows me to filter them out, I end up with a shortlist of duplicates between my newly imported photos and those that were already in the master catalog. The “edited” photos in the duplicates are not much of a problem, as they are strictly speaking “fake duplicates”. The master photographs are more of a problem: I’d like to retain the keywords from the new photo and whatever keywords/ratings were on the old photo. I can do that by manually synchronising metadata, but it’s super tedious.

For the time being I’ll just mark those duplicates “appledupes” until I can figure out what to do with them.

Next in line:

moving those photos into the “final” folders (will involve renaming the Apple photos)
trying a year with more photos.

Moments: Facebook effacera-t-il vos photos le 7 juillet? [fr]

[en] Archive of my weekly French-language "technology advice column".

Ma newsletter hebdomadaire “Demande à Steph” est archivée ici pour la postérité. Chaque semaine, un tuyau ou une explication touchant à la technologie numérique, ou une réponse à vos questions! Inscrivez-vous pour recevoir directement la prochaine édition. Voici l’archive originale.

Note: cette semaine, vu le caractère “actu” du sujet, je la reproduis ici immédiatement, mais normalement je fais ça avec beaucoup de retard!

Je vous rassure tout de suite, malgré les titres alarmistes que vous avez peut-être vus, Facebook ne va pas effacer toutes vos photos le 7 juillet si vous n’installez pas l’application Moments (ils n’ont pas le droit, c’est le jour de mon anniversaire!)

Voici ce qui se passe:

En 2012, Facebook ajoute un service de synchronisation automatique pour les photos de votre smartphone.
Vous l’avez peut-être activé à l’époque — l’idée étant que si les photos étaient déjà “dans Facebook” ce serait plus simple de les partager. Beaucoup de personnes l’ont activé et oublié. (Moi pas, je viens de vérifier.)
Les photos synchronisées ne sont pas publiques, elles sont dans un album nommé “Synced” ou “Synced from Phone” (en anglais).
Fin 2015, Facebook a tranquillement désactivé cette option de synchronisation, somme toute un peu désuète (on poste maintenant facilement les photos depuis son téléphone directement, cette espèce de “pré-publication” est inutile).
Les photos qui seront effacées le 7 juillet si vous n’utilisez pas encore Moments sont ces éventuelles photos synchronisées — en aucun cas les photos que vous avez partagées vous- même sur Facebook.

Si vous êtes concerné, vous recevrez (ou avez reçu) de Facebook une notification et un e-mail à ce sujet. Sinon, dormez tranquille.

Bon alors, c’est quoi cette application que Facebook veut nous “forcer” à utiliser? J’avoue que je n’en avais pas vraiment entendu parler, donc j’ai creusé (et installé) pour vous. C’est plutôt sympa, en fait.

Moments vient résoudre le problème de l’album collectif lors d’événements ou d’activités sociales. Dans une newsletter précédente, je vous ai montré comment utiliser Google Photos pour faire ça. Mais avouons-le, plus de personnes utilisent déjà activement Facebook que Google Photos, donc c’est un poil laborieux. C’est le même principe que les Albums Partagés iCloud, si vous baignez dans un environnement Apple.

Que fait exactement cette application? Un peu comme The Roll, dont je vous ai parlé il y a peu, Moments va d’abord guigner dans vos photos. L’application vous propose ensuite des albums que vous pouvez modifier (très similaire à l’Assistant de Google Photos, là). Jusqu’ici, tout est privé, rien ne quitte votre téléphone.

Vous pouvez ensuite choisir de partager un de ces albums (appelés “Moments”) avec des amis. Par exemple, Moments a bien détecté et regroupé mes photos de la récente Fête des Voisins. Du coup, j’ai partagé cet album avec les voisins et voisines avec qui je suis connectée sur Facebook. Ils pourront y ajouter leurs photos.

Toutes ces photos restent dans l’application Moments et ne vont pas se mélanger avec les photos que vous partagez (plus largement) sur Facebook. On est vraiment dans le partage privé.

Moralité de cette histoire: ne vous en faites pas pour vos photos, et essayez Moments!

Addendum post-envoi (oui, les newsletters c’est bien, mais quand c’est parti, c’est parti): le problème avec notre méthode habituelle de “nous envoyer parmi” nos photos lors de rencontres, c’est qu’on se retrouve avec des photos d’autres personnes dans notre pellicule. Les vrais albums partagés évitent ce problème.

Facebook: Sharing or Showing Off? [en]

[fr] Une prise de conscience d'une part de l'effet négatif que peuvent avoir sur moi les publications positives de mes amis sur Facebook (je suis contente pour eux, mais en comparaison, suivant mon humeur, ça peut faire ressortir à mes yeux mon inadéquation), et d'autre part du fait que je contribue peut-être à cet effet chez les autres avec mes partages (de tout mon temps passé au chalet dans un cadre magnifique, mes voyages, la voile...).

A few months ago, I realised that certain posts that showed up in my timeline on Facebook didn’t make me feel very good.

another of my friends was writing a book
somebody else was hanging out with exciting “famous” people
yet another was pregnant
somebody had a new exciting professional gig

I felt happy for all these people, of course. Amongst my peers, I’ve been reasonably conservative about connecting with people on Facebook, and bar a few exceptions (that’s life), I’ve only friended people I like. So, when people I like are happy, or have a new exciting job, or are about to be parents, or lead exciting lives, I’m happy for them.

But during times when I’m not feeling too good about myself or my situation, or going through a tough spot, or suffering a bout of self-doubt, learning about these good things in my friends’ lives actually brings me down.

The explanation is quite simple: social comparison. We tend to do that. Some more than others. We compare ourselves to others. It’s a background process, really, and I personally have a lot of trouble turning it off or at least down.

I’m somebody who is on the whole positive/optimistic about the internet, the digital world, social media. I think it is overall a good thing. For us as a society, and for us as people. So I’ve always looked at articles like this one with a bit of skepticism.

What I see described in some of these “facebook envy articles” doesn’t really fit with what I observe on Facebook. They sometimes paint a picture where people are actively putting their best foot forward and showing off the highlights of their lives, and others spend their time actively stalking their friends lives, seething with envy. I’m exaggerating a bit, but you get the idea.

When I noticed that learning good news about my friends’ lives was bringing me down, it took me a while to realise I was experiencing some form of Facebook envy — because the mechanisms I could see didn’t fit with what I had been (half-heartedly) reading about.

I didn’t see my friends as bragging. They were just sharing stuff about their lives. And of course, people are more likely to share “Yay got the book deal!” than “ate a cheese sandwich for lunch”. Or maybe they also share the cheese sandwich, but more people are going to like the book deal and comment on it. And so Facebook’s algorithm is going to push it to the top and make it appear in my newsfeed, rather than the cheese sandwich.

I also didn’t see myself as actively trying to compare myself with others. This was just part of the “keeping passively in touch” role that Facebook plays for me. Catching up asynchronously, and probably also asymmetrically. But behind the scenes, social comparison was working overtime.

I learned to take time out. Leave Facebook for a while and go do something else. It didn’t spiral out of control. Yay me.

As I was becoming aware of what my friends’ posts was sometimes doing to me, I started having second thoughts about some of the things I was posting. You see, I have a chalet in the mountains, in a really picturesque area in the Alps. I go there quite often during winter, as I take a season ski pass. And I share photos.

What’s going on in my mind is not really “see how lucky I am”, but more “I’m aware how lucky I am and I want you to get to experience some of this too”. My intention is generous. It is to share so that others can benefit too.

But I’ve realised lately that this may not be the impact my posts have on others. My sometimes seemingly endless chalet and mountain photos might be for others what book deals and professional success in my newsfeed are to me.

People with families, or two weeks of holiday per year, or who live in parts of the world that make travel more difficult or simply don’t have the means to move from where they are might feel (rightly) envious of some aspects of my life. I travel quite a bit. Aside from the chalet, I have a boat on the lake, go to India regularly. My freelance life has drawbacks, but one of the advantages is have is that I have quite a bit of freedom with my time and where I am, as some parts of my work are location-independant. And I live in Switzerland, for heaven’s sake.

Of course, I try to share the good things about my life, because I’m aware I’m privileged, and I don’t want to spend my time whining or complaining. I do complain, but about the small things, usually. Like people saying “blog” to mean “blog post”. The big things that bring me down are also much more difficult to talk about, and so I don’t often mention them. But I’m generally happy with my life and that is what I try to express.

I don’t experience what I do on Facebook as “self-promotion”. Every now and again I “do self-promotion”. I write a post that really has to do with my professional area of expertise, or I share information about something I’m working on. But that’s far from the majority of my postings. Most of the time, it’s really just “oh, look at this, I want you to enjoy it too!”

Now, however, I’m more and more aware of the part I may be playing in fuelling other people’s social comparison blues. Am I going to post yet another photo of how beautiful the mountains are from the chalet balcony? Or showing that I’m sailing on the lake? Or that I’m hanging out with the cats again?

I don’t know if I’m going through a realisation that will change what I post about or not. But it’s definitely changing how I think and feel, to some extent.

What about you? Do you get “bad feelings” seeing what your friends are upto? And do you think about what “bad feelings” you may unwittingly be eliciting amongst your friends through your postings?

And what is the solution to this?

Photo Sync: Figuring Out Lightroom Mobile and iCloud Photo Library [en]

[fr] En train de me dépatouiller avec la nouvelle application Photos d'Apple et la version mobile de Lightroom. Pas encore tout à fait là (la connexion internet un peu lente et le grand nombre de photos n'aident pas).

In the background of my many days of “doing nothing” here in Kolkata, I’ve been trying to wrap my brain around how sync works for both iCloud Photo Library and Lightroom for mobile, particularly as I’m in the process of giving up on Google Photos. Agreed, it’s not exactly the same part of the workflow (getting photos onto my computer archive vs. getting them online/backing them up). But you know how my thought processes work by now, don’t you? 😉

Apple’s iCloud Photo Library seems to be working pretty well. The photos and videos sync, deleting one somewhere deletes copies elsewhere. It’s really clear they are “stored in the cloud” and you can download the full versions if you want. The copies are stored in one of these “Document Packages” which you can open like a folder (right-click!) — I’ve even created a shortcut to the 2015 folder in “Masters” so I can access the photos through Finder if needed. Added advantage, as it’s the native OSX way of doing things, photos show up in the “Photos category” when browsing for files to import into Lightroom, for example.

So, simply using iCloud Photo Library would be a way to get my photos into Lightroom without having to physically connect my devices to the computer.

But… Lightroom has its own system for this, so if it works, wouldn’t it be even better? So far, it’s not working as seamlessly as the Apple system. First of all, because I sync everything on my iDevices with iCloud photo library, Lightroom for mobile seems to import a copy of each photo from each device. Although there is an OK plugin to find duplicates in your Lightroom library, wouldn’t a workflow that doesn’t create them in the first place be better?

Two things that I wasn’t sure about, but I now know:

photos from your iPad/iPhone are added to the Creative Cloud and Lightroom Desktop full-sized; photos from Lightroom Desktop shared to iPad/iPhone through Creative Cloud are shared through their smart previews
the photos synced from your iDevices are made available in a folder on your hard drive, so you can easily drag-and-drop them into your normal archive folders.

I’m running a few tests to see what happens to photos I delete. The photos app seems the best place for quick-and-dirty sorting (if only because when taking photos I’m directly in that app). What I am thinking of doing is turning on Lightroom syncing only from either the iPad or the iPhone, to avoid duplicates. The iPad, probably.

But does that mean I need to open Photos, wait for everything to sync, and then open Lightroom mobile to do it? So far it seems that it’s the way it works — Photos doesn’t seem to be uploading anything in the background from my iDevices, and Lightroom definitely isn’t. This is good when you want to save bandwidth, but less good when your various photo containers are up-to-date and you want things to “just work” invisibly, behind the scenes.

As I’ve been saying for a while, I’m really looking for the day this stuff “just works”.

Hello From Kolkata [en]

[fr] En Inde. Des trucs (très) en vrac. Un podcast en français dans les liens.

I’m in India. For a month.

I did it again: didn’t blog immediately about something I wanted to blog about (the rather frightful things I learned about the anti-GMO movement, if you want to know) because of the havoc it wreaked on my facebook wall when I started sharing what I was reading. And as I didn’t blog about that, I didn’t blog about the next thing. And the next.

And before I know it I’m leaving for India in two weeks, have students to teach and blogs to grade, and don’t know where to start to write a new blog post.

The weather in Kolkata is OK. The trip to come was exhausting: 20 hours for the flights, add on a bit before and after. I didn’t sleep on the Paris-Mumbai leg because it was “too early”, and spent my four hours of layover in Mumbai domestic airport in a right zombie state. Needless to say there is nowhere there to lie down or curl up, aside from the floor. I particularly appreciated having to go to the domestic airport for my Mumbai-Kolkata flight only to be ferried back to the international airport while boarding, because “Jet Airways flights all leave from the international airport”. But I laughed.

It was a pleasant trip overall. Nearly no queue at immigration. Pleasant interactions with people. And oh my, has Mumbai airport come a long way since my first arrival here over 16 years ago. It was… organized. I followed the signs, followed instructions, just went along with the flow. I’ve grown up too, I guess.

I slept over 12 hours last night. I can’t remember when I did that last. I walked less than 500 steps today, bed to couch and back. I’ve (re)connected with the family pets: Coco the African Grey Parrot, (ex-)Maus the chihuahua-papillon-jack-russel-staffie mix (I can never remember his new Indian name), and the remaining cat, which I’ve decided to call “Minette”, who “gave birth” to two empty amniotic sacs yesterday and is frantically meowing all over the place. Looking for non-existent kittens, or missing her brother, who escaped about a week ago? Hopefully she will calm down soon.

I plan to play about with Periscope while I’m here. Everyday life in India seems like a great opportunity to try out live interactive video. Do follow me if you don’t want to miss the fun.

Oh, and don’t panic about the whole “meat causes cancer” thing.

Some random things, listened to recently, and brought to the surface by conversations:

Making Sex Offenders Pay — And Pay And Pay And Pay (Freakonomics Radio)
Saïd, 10 ans après (Sur Les Docks) — an ex-con, 10 years after, and how hard reinsertion is, when you’re faced with the choice between sleeping outside, unable to get a job, and committing another offense so that you can go back to prison; extremely moving story
You Eat What You Are, Part I and Part II (Freakonomics Radio again)
When The Boats Arrive (Planet Money) — what happens to the economy when immigrants arrive? it grows, simply; migrant workers need jobs, of course, but they also very quickly start spending, growing the economy and creating the need for more jobs; the number of available jobs at a given place is not a rigid fixed number

Yep, random, I warned you.

I can now do the Rubik’s cube and have installed Catan on my iDevices, if ever you want to play.

I’ve activated iCloud Photo Library even though I use Lightroom for my “serious” photos. Like the author of the article I just linked to, my iPhone almost never is connected to my Mac anymore. And the photos I need to illustrate blog posts are often photos I’ve just taken with my phone. I end up uploading them to Flickr through the app.

It seems the “photos ecosystem” is slowly getting there, but not quite yet. I’ve just spent a while hunting through my post archives, and I can’t believe I never wrote anything about using Google auto-backup for my photos. At some point I decided to go “all in”, subscribed to 1TB of Google storage, and uploaded my 10+ years of photos there. I loved how it intelligently organized my photos. Well, you know, all the stuff that Google Photos does.

Why am I using the past tense? Because of this: seems automatic upload of a whole bunch of RAW formats has quietly stopped. This is bad. Basically, this paid service is not doing what I chose it for anymore. I hope against reason this will be fixed, but I’m afraid I might be disappointed.

One thing I was not wild about with Google Photos was the inability to spot and process duplicates. And duplication of photos when sharing.

Flickr now has automatic upload and organising. Do I want to try that? Although I dump a lot of stuff in Flickr, I’ve been slack about processing and uploading photos lately. I’m hesitant. Do I want to drown my current albums and photostream in everything I snap? Almost tempted.

I think that’s enough random for now. It’s 10.30 pm and I’m starving, off to the kitchen.

Bol d'Or Mirabaud 2013 avec le Farrniente [fr]

[en] YouTube video and Storify of my three days sailing on the lake with the Farrniente for the Bol d'Or.

C’était mon troisième Bol d’Or, le week-end dernier. Genève-Bouveret-Genève à la voile. Ça va pas forcément vite (29h de course pour le Farrniente) mais ça donne un peu le même sentiment de satisfaction qu’une longue randonnée en montagne: tout ce chemin parcouru sans source d’énergie extérieure!

J’ai posté quelques photos et séquences vidéo en cours de route, jusqu’à ce que mon iPhone rende l’âme (malgré le chargeur de secours que j’ai vidé aussi). Grâce à Storify, voici donc le Bol d’Or 2013 du Farrniente presque comme si vous y étiez. J’ai pris pas mal de photos que je dois encore trier (avec celles des éditions 2009 et 2012!) et en attendant de faire mieux, j’ai collé bout à bout les séquences vidéo pour en faire le film d’une quinzaine de minutes que vous pouvez voir ici:

Moins pénible peut-être que la vidéo, le Storify mentionné plus haut (et il paraît que les liens vers les vidéos dans Facebook marchent quand même, même si on n’a pas de compte Facebook!):

[View the story “Bol d’Or Mirabaud 2013 sur le Farrniente” on Storify]

J’ai profité de l’engouement provoqué par la possibilité de suivre le Farrniente live durant la course pour créer une page Facebook pour le bateau. Click click!

Photos Online on Flickr, Facebook, and Google+ With Lightroom [en]

[fr] Comment je fais pour publier mes photos sur Flickr, Facebook et Google+ depuis Lightroom, avec les plugins de Jeffrey Friedl.

I like Lightroom a lot and have been using it for a few years now to manage my photos. I don’t do a lot of processing/retouching, and it fills my needs perfectly:

I can organize my photos on my hard drive the way I want (monthly, then “events” if needed)
It doesn’t touch the original photos (non-destructive editing)
I can retouch, crop, and do the stuff I deem necessary to improve my photos
I can batch-rename photos according to pretty much any template I want
I can upload photos to Flickr, Facebook, and Google+ directly from Lightroom.

I’ve been using Jeffrey’s Flickr plugin for a while now. The neat thing about Lightroom is that when you “publish” photos somewhere rather than “export” them, Lightroom maintains a relationship between the published photo and the one in your catalog. This means that if six months later you go over it again, crop it differently, or retouch it again, Lightroom can update the photo on Flickr for you.

Of course, you don’t have to: you can make a virtual copy of your photo in Lightroom and work on that one, without impacting the published photo; and you’re also the one who hits the publish button to update the photo on Flickr. It doesn’t happen completely automagically.

The only problem with this is for the person who has included one of the updated Flickr photos in a blog post. Updating changes the photo file name at Flickr, and breaks the insert. Thankfully, there’s a plugin for that.

I love my Flickr account and it contains pretty much all my (published) photos. I can’t deny, however, that a lot of my online social activity happens on Facebook, and that it’s a great environment for photos to circulate. Unfortunately Facebook has really crappy photo library management, so I’ve limited myself to uploading the odd album of photos every now and again. I needed a more sustainable process which didn’t involve exporting photos from Lightroom to my hard drive and uploading them manually.

Enter Jeffrey’s Facebook plugin. As Facebook sucks, however, you shouldn’t really use the publish relationship to update photos that you’ve changed since you uploaded them to Facebook. Initially, as all I wanted to do was simplify my export-upload procedure, I used the “export” capability of the plugin. That means that instead of creating a “publish service” I created an “export preset” (File menu) to send photos directly to Facebook. Once sent, they’re sent, and live their lives on their own.

What’s nice is that I can also export photos like that directly to my pages (Tounsi and Quintus will appreciate).

Jeffrey also has a plugin for PicasaWeb, which for all practical matters pretty much means Google+ (Google Plus). Google Plus seems better at handling photo updates, so I set it up as a “publish service”.

I realized that I could use “smart publish collections” to make things simpler. My sets are already defined on Flickr. For example, I have this set of chalet photos, and I just want to reproduce it on Google+ (and Facebook). With a smart album or collection, I can tell Lightroom to “just publish those photos which are in that Flickr set”. Easy! This made me set up Facebook as a publish service too.

I love Jeffrey’s plugins because they are very well-maintained (up-to-date). There is some clunkiness in places because he really pushes beyond the limits of what Lightroom was designed for, but if you’re willing to see the odd error message or use the odd workaround, that should bother you too much. The clunkiness is amply made up for by the extensive documentation you will find both on Jeffrey’s site and in the plugins.

One such workaround is required to create a smart publish collection: because of a Lightroom bug, you have to edit the publish service and add the collection from there. But thankfully Jeffrey is really good at documenting stuff and telling you what to do and how, so you just have to follow the instructions on the screen. Basically you create a smart album or set in the “edit publish service” screen, then once it’s done edit that album to set your “smart” criteria.

Two useful things to know:

images uploaded to Google+ don’t count against your storage limit if they are smaller than 2048x2048px;
setting jpeg export quality in Lightroom to more than 75 isn’t very useful, in most cases, and just makes file size huge, slowing down your uploads considerably.

Finally, Jeffrey’s plugins are donationware. He spends a lot of time on them, and if you find them useful, you should definitely chip in.

Cats Online: Quintus and Tounsi [en]

[fr] Photos et vidéos de chats 🙂

Being a proper cat lady and an expert in social media I of course make sure my cats’ online presence is at least decent. Twitter doesn’t work too well because we only have one phone for the three of us, and I get to use it most of the time. On Facebook, I have thankfully (for my friends) joined a francophone “cat people” group where I post most of the kitty photos I take. Quintus and Tounsi do have their own presence on Facebook, though it’s spotty at best. (Do please like them, it’s good for their egos.)

During the last module of the social media and online communities course I direct, Thierry Weber came to give a couple of hours of training on YouTube and online video. I “played student” for the occasion, which inspired me to tinker a bit more with video in the future. I actually did some “videoblogging” early on, and was a rabid user of the initial Seesmic, but never really got into YouTube. Probably because I joined it early on (my username is “steph“, that should tell you) when it was still really crappy. (Which is why I used to post more to DailyMotion or Viddler.) I’ve also always found messing around with video formats and codecs and upload size a real nightmare, but now it’s much easier. With an iPhone and a programme like iExplorer to get the videos off it (warning: you have to pay), I’m actually looking forward to making some videos while I’m in India next month. Oh yeah: video editing… not so much for me. I shoot short sequences, throw them online, and that’s it.

So, without further ado, cat photos (Tounsi and Quintus) and videos from the last days.

Enjoy!

Memories of Safran [en]

[fr] Souvenirs de Safran.

Safran was put to sleep on Thursday. I’m still very sad, though I’m not end-of-the-world devastated like when Bagha died. Tounsi seems OK, but of course it’s hard to say. I’m upset, our routines have changed because Safran isn’t there. He doesn’t seem to be pining or going around looking for Safran, in any case.

Safran was with me for just a little over two months, and I feel the need to put in writing the memories I have of him — the good ones, mainly — I think part of me is afraid I’m going to move on and settle down in my life with my remaining cat and forget little Safran. I won’t, of course, but memories do fade away. Prepare for some rambling and a pile of kitty photographs.

Continue reading “Memories of Safran [en]“

A Plugin to Compensate for Flickr Broken Embed Suckage? [en]

[fr] Quand on met à jour une photo dans Flickr, Flickr change le nom du fichier. Idée de plugin WordPress pour faire la chasse aux liens cassés.

A few days ago I started noticing this kind of thing in my posts:

The explanation? I’ve used my week of holiday-at-home to fool around quite a bit in Lightroom. Lightroom publishes my photos directly to Flickr. When I change a published photos, Lightroom updates it. But Flickr changes the file name when you republish a photo. And that breaks embeds.

(And yeah, Lightroom replaces the whole photo even if you’ve just edited metadata.)

To make things worse, my browser cache shows me all my photos, even the missing ones. So I don’t see which ones are missing.

Idea! A plugin that would crawl through all the embedded Flickr images in a blog, and make sure that all the photos display correctly. Produce a list of the posts and photos that need updating. Or even better, do it automatically (even if the link to the displayed photo is broken, the link to the photo page still works, and it should be trivial to get the updated embed code and replace it in the post.)

Anybody?