<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Libnotifytastic</title>
	<atom:link href="http://blogs.gnome.org/hughsie/2009/01/19/libnotifytastic/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/hughsie/2009/01/19/libnotifytastic/</link>
	<description>Blog about geeky stuff</description>
	<lastBuildDate>Sun, 29 Jan 2012 09:38:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: hughsie</title>
		<link>http://blogs.gnome.org/hughsie/2009/01/19/libnotifytastic/comment-page-1/#comment-932</link>
		<dc:creator>hughsie</dc:creator>
		<pubDate>Tue, 20 Jan 2009 15:59:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=298#comment-932</guid>
		<description>New screenshot uploaded. In the worst case scenario (system restart required, messages present, critical updates remain) you&#039;ll see two icons. In normal usage you&#039;re see one icon where the most important thing is displayed and the others suppressed.

I agree the messages are not useful for most users, but some people need to see the output. Debian users in particular need to be able to see what configuration files were changed, as sometimes an automatic merge will not be performed. If something doesn&#039;t work correctly, and the user starts to debug, they do need to see the messages.

Cheers for the feedback, hopefully we can keep refining the design until we&#039;ve got something that keeps all of you happy :-)</description>
		<content:encoded><![CDATA[<p>New screenshot uploaded. In the worst case scenario (system restart required, messages present, critical updates remain) you&#8217;ll see two icons. In normal usage you&#8217;re see one icon where the most important thing is displayed and the others suppressed.</p>
<p>I agree the messages are not useful for most users, but some people need to see the output. Debian users in particular need to be able to see what configuration files were changed, as sometimes an automatic merge will not be performed. If something doesn&#8217;t work correctly, and the user starts to debug, they do need to see the messages.</p>
<p>Cheers for the feedback, hopefully we can keep refining the design until we&#8217;ve got something that keeps all of you happy <img src='http://blogs.gnome.org/hughsie/wp-content/mu-plugins/tango-smilies/tango/face-smile.png' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrys</title>
		<link>http://blogs.gnome.org/hughsie/2009/01/19/libnotifytastic/comment-page-1/#comment-931</link>
		<dc:creator>Patrys</dc:creator>
		<pubDate>Tue, 20 Jan 2009 09:31:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=298#comment-931</guid>
		<description>Adam:

That&#039;s exactly what I had in mind. An audit log similar to what Windows does with configurable verbosity for an admin.

No hacky details for users (like mirror errors or config merges). They don&#039;t care. And even if they did, they probably don&#039;t have enough skill and - most importantly - privileges to even look at said config file.

Let&#039;s keep the old notifications for stuff like &quot;new updates available&quot; or &quot;packages installed&quot; but I see no point in developing a whole new notification system just to strike down upon the innocent user with great vengeance.</description>
		<content:encoded><![CDATA[<p>Adam:</p>
<p>That&#8217;s exactly what I had in mind. An audit log similar to what Windows does with configurable verbosity for an admin.</p>
<p>No hacky details for users (like mirror errors or config merges). They don&#8217;t care. And even if they did, they probably don&#8217;t have enough skill and &#8211; most importantly &#8211; privileges to even look at said config file.</p>
<p>Let&#8217;s keep the old notifications for stuff like &#8220;new updates available&#8221; or &#8220;packages installed&#8221; but I see no point in developing a whole new notification system just to strike down upon the innocent user with great vengeance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Petaccia</title>
		<link>http://blogs.gnome.org/hughsie/2009/01/19/libnotifytastic/comment-page-1/#comment-930</link>
		<dc:creator>Adam Petaccia</dc:creator>
		<pubDate>Mon, 19 Jan 2009 20:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=298#comment-930</guid>
		<description>Why not just use the system log? If they&#039;re nonfatal then most users wont care, but a sysadmin can use Gnome&#039;s log viewer to check it out.</description>
		<content:encoded><![CDATA[<p>Why not just use the system log? If they&#8217;re nonfatal then most users wont care, but a sysadmin can use Gnome&#8217;s log viewer to check it out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: twilightomni</title>
		<link>http://blogs.gnome.org/hughsie/2009/01/19/libnotifytastic/comment-page-1/#comment-929</link>
		<dc:creator>twilightomni</dc:creator>
		<pubDate>Mon, 19 Jan 2009 19:46:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=298#comment-929</guid>
		<description>Aside from the possible question of duplicated functionality...

With this &quot;event viewer&quot;, PackageKit is beginning to show the dark interiors of the package management system that it was trying to shield users from in the first place.  

Use cases!  The _only_ role type that these messages would be useful for is a competent system administrator -- which isn&#039;t really one of your user profiles.  Even the &quot;hobbyist computer whiz&quot; will find this dumping-ground obtuse and a buzzword blackbox.

Handle with care for what messages are revealed.  PackageKit would ideally be able to probe the user for assistance with any repository and metadata problems in a way that allows you to heal the system, with a minimum of deluging-the-user-with-complexity.  That would probably mean you would never explicitly see the term &quot;invalid metadata for [really-weird-name-here] repository&quot;. :)

Of course that can all be polished, and I understand you&#039;re working on the interaction metaphor itself, as opposed to the content.</description>
		<content:encoded><![CDATA[<p>Aside from the possible question of duplicated functionality&#8230;</p>
<p>With this &#8220;event viewer&#8221;, PackageKit is beginning to show the dark interiors of the package management system that it was trying to shield users from in the first place.  </p>
<p>Use cases!  The _only_ role type that these messages would be useful for is a competent system administrator &#8212; which isn&#8217;t really one of your user profiles.  Even the &#8220;hobbyist computer whiz&#8221; will find this dumping-ground obtuse and a buzzword blackbox.</p>
<p>Handle with care for what messages are revealed.  PackageKit would ideally be able to probe the user for assistance with any repository and metadata problems in a way that allows you to heal the system, with a minimum of deluging-the-user-with-complexity.  That would probably mean you would never explicitly see the term &#8220;invalid metadata for [really-weird-name-here] repository&#8221;. <img src='http://blogs.gnome.org/hughsie/wp-content/mu-plugins/tango-smilies/tango/face-smile.png' alt=':)' class='wp-smiley' /> </p>
<p>Of course that can all be polished, and I understand you&#8217;re working on the interaction metaphor itself, as opposed to the content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Achim</title>
		<link>http://blogs.gnome.org/hughsie/2009/01/19/libnotifytastic/comment-page-1/#comment-928</link>
		<dc:creator>Achim</dc:creator>
		<pubDate>Mon, 19 Jan 2009 17:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=298#comment-928</guid>
		<description>I think the idea is not bad.

It could fit very well to the concept that Mark proposed.
http://www.markshuttleworth.com/archives/253

Regards
Achim</description>
		<content:encoded><![CDATA[<p>I think the idea is not bad.</p>
<p>It could fit very well to the concept that Mark proposed.<br />
<a href="http://www.markshuttleworth.com/archives/253" rel="nofollow">http://www.markshuttleworth.com/archives/253</a></p>
<p>Regards<br />
Achim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dylan McCall</title>
		<link>http://blogs.gnome.org/hughsie/2009/01/19/libnotifytastic/comment-page-1/#comment-927</link>
		<dc:creator>Dylan McCall</dc:creator>
		<pubDate>Mon, 19 Jan 2009 16:59:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=298#comment-927</guid>
		<description>It would be nice if accessing the notification area was done /with/ libnotify, instead of having two differnent APIs intended for the exact same concept that we have to fight over.</description>
		<content:encoded><![CDATA[<p>It would be nice if accessing the notification area was done /with/ libnotify, instead of having two differnent APIs intended for the exact same concept that we have to fight over.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Buck</title>
		<link>http://blogs.gnome.org/hughsie/2009/01/19/libnotifytastic/comment-page-1/#comment-926</link>
		<dc:creator>Joe Buck</dc:creator>
		<pubDate>Mon, 19 Jan 2009 16:25:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=298#comment-926</guid>
		<description>And the &quot;solution&quot; you suggest mixes together things that the user might care about, to things that the user should not care about and can&#039;t do anything about. Bad metadata? Load it again from a different mirror and don&#039;t bug the user. New packages available? Cool, but why provide that information as individual messages mixed in with messages the user doesn&#039;t care about? Configuration files were changed? What is the non-expert supposed to do about that?</description>
		<content:encoded><![CDATA[<p>And the &#8220;solution&#8221; you suggest mixes together things that the user might care about, to things that the user should not care about and can&#8217;t do anything about. Bad metadata? Load it again from a different mirror and don&#8217;t bug the user. New packages available? Cool, but why provide that information as individual messages mixed in with messages the user doesn&#8217;t care about? Configuration files were changed? What is the non-expert supposed to do about that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://blogs.gnome.org/hughsie/2009/01/19/libnotifytastic/comment-page-1/#comment-925</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Mon, 19 Jan 2009 16:06:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=298#comment-925</guid>
		<description>Is PackageKit using more than one TrayIcon?

pls not ;)</description>
		<content:encoded><![CDATA[<p>Is PackageKit using more than one TrayIcon?</p>
<p>pls not <img src='http://blogs.gnome.org/hughsie/wp-content/mu-plugins/tango-smilies/tango/face-wink.png' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vadim P.</title>
		<link>http://blogs.gnome.org/hughsie/2009/01/19/libnotifytastic/comment-page-1/#comment-924</link>
		<dc:creator>Vadim P.</dc:creator>
		<pubDate>Mon, 19 Jan 2009 15:44:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=298#comment-924</guid>
		<description>Yeah I hope this is a joke too. &quot;oh, 5 messages eh?&quot; *opens the dialog* &quot;um... okay, now what? I guess I just press this &#039;Close&#039; button and get on with my wasted 2 minutes&quot;</description>
		<content:encoded><![CDATA[<p>Yeah I hope this is a joke too. &#8220;oh, 5 messages eh?&#8221; *opens the dialog* &#8220;um&#8230; okay, now what? I guess I just press this &#8216;Close&#8217; button and get on with my wasted 2 minutes&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rawsausage</title>
		<link>http://blogs.gnome.org/hughsie/2009/01/19/libnotifytastic/comment-page-1/#comment-923</link>
		<dc:creator>rawsausage</dc:creator>
		<pubDate>Mon, 19 Jan 2009 15:38:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=298#comment-923</guid>
		<description>Spamming the user with irrelevant stuff the user does not have to ever be aware of.</description>
		<content:encoded><![CDATA[<p>Spamming the user with irrelevant stuff the user does not have to ever be aware of.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/hughsie/2009/01/19/libnotifytastic/feed/ ) in 0.20291 seconds, on Feb 11th, 2012 at 11:53 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 12th, 2012 at 12:53 am UTC -->
