<?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 for DailyStuff</title>
	<atom:link href="http://blog.dailystuff.nl/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dailystuff.nl</link>
	<description>toen Internet stil stond en weer doorging</description>
	<lastBuildDate>Sat, 04 Feb 2012 07:47:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>Comment on Censorship in China^WThe Netherlands by Blocking the piratebay &#124; DailyStuff</title>
		<link>http://blog.dailystuff.nl/2012/02/censorship-in-chinawthe-netherlands/comment-page-1/#comment-473</link>
		<dc:creator>Blocking the piratebay &#124; DailyStuff</dc:creator>
		<pubDate>Sat, 04 Feb 2012 07:47:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dailystuff.nl/?p=1135#comment-473</guid>
		<description>[...] a previous post it became clear that censorship in The Netherlands has started. Due to the nature of the Internet [...]</description>
		<content:encoded><![CDATA[<p>[...] a previous post it became clear that censorship in The Netherlands has started. Due to the nature of the Internet [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BtrFS and readonly snapshots by Brazen</title>
		<link>http://blog.dailystuff.nl/2012/01/btrfs-and-readonly-snapshots/comment-page-1/#comment-471</link>
		<dc:creator>Brazen</dc:creator>
		<pubDate>Fri, 03 Feb 2012 14:36:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dailystuff.nl/?p=1130#comment-471</guid>
		<description>Yep I noticed the Ubuntu issue, too.  Hopefully read-only snapshots and the usable fsck tool (supposed to be available this month) will make it in to 12.04.  With 12.04 being a LTS release, it would be nice to have these btrfs features available to servers over the next 2 years rather than having to wait for 14.04.</description>
		<content:encoded><![CDATA[<p>Yep I noticed the Ubuntu issue, too.  Hopefully read-only snapshots and the usable fsck tool (supposed to be available this month) will make it in to 12.04.  With 12.04 being a LTS release, it would be nice to have these btrfs features available to servers over the next 2 years rather than having to wait for 14.04.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BtrFS and readonly snapshots by Hans</title>
		<link>http://blog.dailystuff.nl/2012/01/btrfs-and-readonly-snapshots/comment-page-1/#comment-465</link>
		<dc:creator>Hans</dc:creator>
		<pubDate>Wed, 01 Feb 2012 08:49:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dailystuff.nl/?p=1130#comment-465</guid>
		<description>At the time Linux 3.2.0, but BtfFS userland was 0.19+20111105-2 and that is a very recent one. Ubuntu 11.10 still uses 0.19+20100601-3ubuntu3 which is from before March 2011. Debian, Ubuntu&#039;s upstream for this package, packaged the right version on &lt;a href=&quot;http://packages.qa.debian.org/b/btrfs-tools.html&quot; rel=&quot;nofollow&quot;&gt;2011-08-28&lt;/a&gt;. Ubuntu 12.04 still uses the old version, hopefully they update this package in the next sync with Debian Unstable.</description>
		<content:encoded><![CDATA[<p>At the time Linux 3.2.0, but BtfFS userland was 0.19+20111105-2 and that is a very recent one. Ubuntu 11.10 still uses 0.19+20100601-3ubuntu3 which is from before March 2011. Debian, Ubuntu&#8217;s upstream for this package, packaged the right version on <a href="http://packages.qa.debian.org/b/btrfs-tools.html" rel="nofollow">2011-08-28</a>. Ubuntu 12.04 still uses the old version, hopefully they update this package in the next sync with Debian Unstable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BtrFS and readonly snapshots by Stefan Lasiewski</title>
		<link>http://blog.dailystuff.nl/2012/01/btrfs-and-readonly-snapshots/comment-page-1/#comment-463</link>
		<dc:creator>Stefan Lasiewski</dc:creator>
		<pubDate>Wed, 01 Feb 2012 01:50:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dailystuff.nl/?p=1130#comment-463</guid>
		<description>What version are you running? On my Ubuntu 11.10 system (running Kernel 3.0.0 and Btrfs v.019, the `-r` flag is not valid:

    btrfs subvolume snapshot -r /u1 /u1/.snapshot/test
    ERROR: &#039;subvolume snapshot&#039; requires 2 arg(s)

But according to the BTRFS wiki, read-only snapshots have been supported since Linux 2.6.38 (March 2011).

[1]: https://btrfs.wiki.kernel.org/#News</description>
		<content:encoded><![CDATA[<p>What version are you running? On my Ubuntu 11.10 system (running Kernel 3.0.0 and Btrfs v.019, the `-r` flag is not valid:</p>
<p>    btrfs subvolume snapshot -r /u1 /u1/.snapshot/test<br />
    ERROR: &#8216;subvolume snapshot&#8217; requires 2 arg(s)</p>
<p>But according to the BTRFS wiki, read-only snapshots have been supported since Linux 2.6.38 (March 2011).</p>
<p>[1]: <a href="https://btrfs.wiki.kernel.org/#News" rel="nofollow">https://btrfs.wiki.kernel.org/#News</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on First steps with BtrFS by BtrFS and readonly snapshots &#124; DailyStuff</title>
		<link>http://blog.dailystuff.nl/2012/01/first-steps-with-btrfs/comment-page-1/#comment-451</link>
		<dc:creator>BtrFS and readonly snapshots &#124; DailyStuff</dc:creator>
		<pubDate>Sat, 21 Jan 2012 07:31:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dailystuff.nl/?p=1128#comment-451</guid>
		<description>[...] a previous posting I started with BtrFS and as mentioned BtrFS supports snapshotting. With this you can create a point [...]</description>
		<content:encoded><![CDATA[<p>[...] a previous posting I started with BtrFS and as mentioned BtrFS supports snapshotting. With this you can create a point [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Faulty RSS-feeds by Hans</title>
		<link>http://blog.dailystuff.nl/2011/12/faulty-rss-feeds/comment-page-1/#comment-433</link>
		<dc:creator>Hans</dc:creator>
		<pubDate>Sun, 15 Jan 2012 21:29:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dailystuff.nl/?p=1120#comment-433</guid>
		<description>&lt;a href=&quot;#comment-431&quot; rel=&quot;nofollow&quot;&gt;@Daniel &lt;/a&gt; Developers shouldn&#039;t read access logs or maybe they should as most plugins stop giving you a redirect when you identify youself as FeedBurner ;-) Then again, FeedBurner is more then only statistics. They offload your feed in trade for statistics, but what a lot of webmasters forget is that it is forbidden to export personal data overseas for countries within the EU for example. In most cases IP-addresses are included as being personal data as it can be related and retraced to a person. A least that is in The Netherlands an issue.

But again, developers really should start doing output validation. Making sure it is valide and safe. How many comment feeds are being offered thru FeedBurner and most of them are not sufficient checked. WordPress developers where informed years ago about this years ago and didn&#039;t pay attention until an exploit was posted by some one. With SOPA around the corner things can become interesting to put it mildly ;-)</description>
		<content:encoded><![CDATA[<p><a href="#comment-431" rel="nofollow">@Daniel </a> Developers shouldn&#8217;t read access logs or maybe they should as most plugins stop giving you a redirect when you identify youself as FeedBurner <img src='http://blog.dailystuff.nl/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  Then again, FeedBurner is more then only statistics. They offload your feed in trade for statistics, but what a lot of webmasters forget is that it is forbidden to export personal data overseas for countries within the EU for example. In most cases IP-addresses are included as being personal data as it can be related and retraced to a person. A least that is in The Netherlands an issue.</p>
<p>But again, developers really should start doing output validation. Making sure it is valide and safe. How many comment feeds are being offered thru FeedBurner and most of them are not sufficient checked. WordPress developers where informed years ago about this years ago and didn&#8217;t pay attention until an exploit was posted by some one. With SOPA around the corner things can become interesting to put it mildly <img src='http://blog.dailystuff.nl/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Another company switching to XMPP by Hans</title>
		<link>http://blog.dailystuff.nl/2011/12/another-company-switching-to-xmpp/comment-page-1/#comment-432</link>
		<dc:creator>Hans</dc:creator>
		<pubDate>Sun, 15 Jan 2012 21:16:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dailystuff.nl/?p=1115#comment-432</guid>
		<description>&lt;a href=&quot;#comment-430&quot; rel=&quot;nofollow&quot;&gt;@Daniel &lt;/a&gt; True, but as for now the access for instant messaging is being standardized and this allows people to switch providers without any additional software changes on the client side. The problem Microsoft is having, they allowed third party e-mailaddresses on there platform as logon ID this needs to be sorted out before they could be part the XMPP Federation. But again, Google needed about 6 months to become part of the XMPP Federation. And AOL and Facebook are also still closed networks. Like you said, we can only hope, but for now XMPP for accessing instant messaging is becoming the norm.</description>
		<content:encoded><![CDATA[<p><a href="#comment-430" rel="nofollow">@Daniel </a> True, but as for now the access for instant messaging is being standardized and this allows people to switch providers without any additional software changes on the client side. The problem Microsoft is having, they allowed third party e-mailaddresses on there platform as logon ID this needs to be sorted out before they could be part the XMPP Federation. But again, Google needed about 6 months to become part of the XMPP Federation. And AOL and Facebook are also still closed networks. Like you said, we can only hope, but for now XMPP for accessing instant messaging is becoming the norm.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Faulty RSS-feeds by Daniel</title>
		<link>http://blog.dailystuff.nl/2011/12/faulty-rss-feeds/comment-page-1/#comment-431</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Sun, 15 Jan 2012 20:48:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dailystuff.nl/?p=1120#comment-431</guid>
		<description>FeedBurner does statistics. Developers don’t know how to or do not want to spend time reading their servers’ access logs which would have provided almost all the same data.</description>
		<content:encoded><![CDATA[<p>FeedBurner does statistics. Developers don’t know how to or do not want to spend time reading their servers’ access logs which would have provided almost all the same data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Another company switching to XMPP by Daniel</title>
		<link>http://blog.dailystuff.nl/2011/12/another-company-switching-to-xmpp/comment-page-1/#comment-430</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Sun, 15 Jan 2012 20:46:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dailystuff.nl/?p=1115#comment-430</guid>
		<description>Unfortunately, the Live team at Microsoft did not announce support for XMPP Federation. Which would have meant that it’s service would be interoperable with other XMPP service providers. They will, hopefully, allow for this kind of openness in the future.</description>
		<content:encoded><![CDATA[<p>Unfortunately, the Live team at Microsoft did not announce support for XMPP Federation. Which would have meant that it’s service would be interoperable with other XMPP service providers. They will, hopefully, allow for this kind of openness in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on World IPv6 Day by IPv6 voor mailverkeer &#124; DailyStuff</title>
		<link>http://blog.dailystuff.nl/2011/06/world-ipv6-day/comment-page-1/#comment-322</link>
		<dc:creator>IPv6 voor mailverkeer &#124; DailyStuff</dc:creator>
		<pubDate>Sun, 12 Jun 2011 12:24:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dailystuff.nl/?p=1092#comment-322</guid>
		<description>[...] woensdag was het World IPv6 Day en in navolging daarvan werden een aantal maildomeinen voorzien een AAAA-record in DNS naast het [...]</description>
		<content:encoded><![CDATA[<p>[...] woensdag was het World IPv6 Day en in navolging daarvan werden een aantal maildomeinen voorzien een AAAA-record in DNS naast het [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

