Version: unspecified (using Devel) OS: Linux It would be great if one is able to synchronize the facebook, google, and other contacts with the face detection setup in digikam. Imagine no longer having to really tag pictures. Or just even having the information synchronized with those contact systems would make life a lot less of a hassle. Thanks, Tamer Reproducible: Didn't try
I'd like to have that in the Facebook plugin, too, and am considering implementing it.
Dirk, Following your comment #1, any news about a possible patch for this entry ? Gilles Caulier
I'd like to add that this is a two-way function. For one, being able to "seed" Digikam with e.g. tags in Facebook. Other possibility is updating Google contact photos from Digikam (as Picasa does already). I personally am more interested in the later at this time, but that's anecdotal. Question is, should these wishes be separated into different bugs?
Alenjandro, yes, please fill another bug... Gilles Caulier
On 12/14/11 18:04, Gilles Caulier wrote: > Dirk, > > Following your comment #1, any news about a possible patch for this entry ? > No news yet. I've become quite busy with work, in fact almost desperate at the moment. ;) So probably no news for another while. The path there would be first to do another API upgrade to the opengraph API. This possibly involves adding another library dependency to KIPI (or reimplementing opengraph support from scratch). Also the synchronisation might become as complicated as synchronisation between normal address books, because we'd need to keep track of changes to identities on both sides (contact renames, etc). And if I remember correctly "person" is a computer-global concept with the semantic desktop, so changes to contacts might originate in other applications as well. Semantic desktop doesn't work on my installation for some reason, so can't tell for sure. I have a good idea of what needs to be done and could support anyone interested.
Maybe ask for a developer at planetKDE? This one really it worth the try imho
Akonadi must be use here to be more generic. See bug #288977 Gilles Caulier *** This bug has been marked as a duplicate of bug 288977 ***
Fixed with bug #288977