<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>linking faces to addresses from turba</title> 
  <pubDate>Fri, 10 Apr 2026 15:00:36 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/8470</link> 
  <atom:link rel="self" type="application/rss+xml" title="linking faces to addresses from turba" href="https://bugs.horde.org/ticket/8470/rss" /> 
  <description>linking faces to addresses from turba</description> 
 
   
   
  <item> 
   <title>it would be really nice to have a option to link face names </title> 
   <description>it would be really nice to have a option to link face names to adresses from turba, so that when viewing a pic we can jump directly to the adress in turba to get more details from the person</description> 
   <pubDate>Fri, 31 Jul 2009 17:32:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8470#t55101</link> 
  </item> 
   
  <item> 
   <title>While this might work ok with a single, global address book,</title> 
   <description>While this might work ok with a single, global address book, I think this would be of limited value and would complicate an already complicated permissions issue when dealing with faces and personal and/or non-share enabled address book sources.



I&#039;d be willing to look at any patches, but I don&#039;t plan on implementing this.</description> 
   <pubDate>Fri, 31 Jul 2009 18:13:16 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8470#t55102</link> 
  </item> 
   
  <item> 
   <title>i understand that it might be complicated, but so we have ap</title> 
   <description>i understand that it might be complicated, but so we have apps that don&#039;t work really together and information must be looked up everytime on my one. the permission issue isn&#039;t the problem from my point of view. if someone doesn&#039;t have the permisson to read the information from turba then don&#039;t provide a link or detail information, and if available do it. every turba entry has its own id in database, so only linking this id to the pic would be enough, permissions must then only be checked when detail information are queried</description> 
   <pubDate>Sat, 01 Aug 2009 18:18:59 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8470#t55105</link> 
  </item> 
   
  <item> 
   <title>&gt; i understand that it might be complicated, but so we have </title> 
   <description>&gt; i understand that it might be complicated, but so we have apps that 

&gt; don&#039;t work really together and information must be looked up 

&gt; everytime on my one. 



I still don&#039;t see this as a mainstream use case, but that&#039;s just me.



&gt; the permission issue isn&#039;t the problem from my 

&gt; point of view. if someone doesn&#039;t have the permisson to read the 

&gt; information from turba then don&#039;t provide a link or detail 

&gt; information, and if available do it. every turba entry has its own id 

&gt; in database, so only linking this id to the pic would be enough, 



Yes, I&#039;m aware of how the data is stored and how to link the data. To be exact, we would need to store both a source identifier and the contact&#039;s uid. Also, depending on the type of source you&#039;re using in Turba (not everybody uses a SQL based source), it&#039;s possible that only the user tagging the face would ever be able to see the tag. The comment about the permissions was referring to issues internal to Ansel in how gallery permissions are stored. 



Linking the data is not the issue.  The issue is the overhead in performing the SQL queries in Ansel along with api calls for validation and permission checking for _each_and_every_ face. On an image view this may not be an issue, but for views that show multiple faces it can become a problem.

 

OTOH, I&#039;d be more apt to include this if we allow ONLY the owner of an image to link a face to a contact AND to allow ONLY the owner of an image to see the link.



No, it&#039;s not impossible, but IMO it&#039;s not worth either the overhead or the time to implement it.  Like I said, if you (or anyone else) provides a patch, I&#039;d be willing to look at it, and possibly add it as a feature that could be explicitly turned on.</description> 
   <pubDate>Sat, 01 Aug 2009 20:01:47 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8470#t55106</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
