<?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>Consider implementing privicons</title> 
  <pubDate>Fri, 10 Apr 2026 12:25:56 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/9149</link> 
  <atom:link rel="self" type="application/rss+xml" title="Consider implementing privicons" href="https://bugs.horde.org/ticket/9149/rss" /> 
  <description>Consider implementing privicons</description> 
 
   
   
  <item> 
   <title>http://www.ietf.org/id/draft-koenig-privicons-00.txt</title> 
   <description>http://www.ietf.org/id/draft-koenig-privicons-00.txt</description> 
   <pubDate>Tue, 27 Jul 2010 09:25:53 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9149#t59435</link> 
  </item> 
   
  <item> 
   <title>Better link: http://privicons.org/

Doesn&#039;t appear to be a</title> 
   <description>Better link: http://privicons.org/

Doesn&#039;t appear to be a whole bunch of momentum behind this, but implementing would be straightforward, at least with respect to adding the privicon information in a Header (Section 2.4 of the RFC draft).

On the other hand, putting privicon information in the message subject and/or body is just stupid, annoying, and confusing as hell.  Especially on a MUA that doesn&#039;t support privicons - the ASCII text icons mean absolutely nothing.</description> 
   <pubDate>Tue, 06 Dec 2011 06:27:09 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9149#t69320</link> 
  </item> 
   
  <item> 
   <title>0 traction on this.  Rejecting.</title> 
   <description>0 traction on this.  Rejecting.</description> 
   <pubDate>Wed, 13 Nov 2013 05:23:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9149#t81455</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
