<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for inode</title><link>http://disqus.com/by/inode/</link><description></description><atom:link href="http://disqus.com/inode/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 10 Feb 2009 18:59:27 -0000</lastBuildDate><item><title>Re: Unix time ... before 1970</title><link>http://nb.inode.co.nz/archives/2008/12/25/index.html?e2008-12-25T09_27_51.txt#comment-6151582</link><description>&lt;p&gt;And it's just saved me already :-) An accident with copy/paste saw a whole load of crap pasted into a root shell, with associated damage. "hg revert -r 3 --all" brought the system back to state again!&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">inode</dc:creator><pubDate>Tue, 10 Feb 2009 18:59:27 -0000</pubDate></item><item><title>Re: Wednesday Communications pt 1</title><link>http://nb.inode.co.nz/archives/2008/04/16/index.html?e2008-04-16T09_17_43.txt#comment-373995</link><description>&lt;p&gt;After I posted that, the Vodem never worked on that laptop again. Fantastic quality, eh. I've switched to a PCMCIA card instead, which works.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">inode</dc:creator><pubDate>Thu, 24 Apr 2008 05:19:55 -0000</pubDate></item><item><title>Re: Getting photos from the iPhone</title><link>http://nb.inode.co.nz/archives/2008/03/14/index.html?e2008-03-14T09_52_56.txt#comment-231940</link><description>&lt;p&gt;That's one part of the picture ... :-) the rest?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">inode</dc:creator><pubDate>Fri, 14 Mar 2008 22:57:57 -0000</pubDate></item><item><title>Re: iPhone kiwi-ise.co.nz moved ...</title><link>http://nb.inode.co.nz/archives/2008/03/14/index.html?e2008-03-14T00_47_55.txt#comment-229212</link><description>&lt;p&gt;Argh, I knew the parser would break on that, but hit submit too early. I'll fix it later. In the meantime,point AppTapp to &lt;a href="http://get.kiwi-ise.co.nz/" rel="nofollow noopener" target="_blank" title="http://get.kiwi-ise.co.nz/"&gt;http://get.kiwi-ise.co.nz/&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">inode</dc:creator><pubDate>Thu, 13 Mar 2008 21:42:38 -0000</pubDate></item><item><title>Re: 80x15 icons</title><link>https://disqus.com/home/discussion/webmasters/80x15_icons/#comment-10884</link><description>&lt;p&gt;Actually, my icon was more to act as a site-level generic link back to the disqus home page, not to act as a thread-specific marker :-)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">inode</dc:creator><pubDate>Sun, 11 Nov 2007 14:37:15 -0000</pubDate></item><item><title>Re: Integrating Disqus with Nanoblogger</title><link>http://nb.inode.co.nz/archives/2007/11/09/index.html?e2007-11-09T03_51_54.txt#comment-10231</link><description>&lt;p&gt;I guess if I knew nanoblogger slightly better I wouldn't have to hard-code the site URL into disqus_url :-) I'd still have to specify the location of embed.js and the noscript link, but they could be carried elsewhere ...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">inode</dc:creator><pubDate>Fri, 09 Nov 2007 00:39:31 -0000</pubDate></item><item><title>Re: A thread per-article from a blog?</title><link>https://disqus.com/home/discussion/disqus/a_thread_per_article_from_a_blog/#comment-10205</link><description>&lt;p&gt;Thanks for your help -- all working now!&lt;br&gt;&lt;a href="http://nb.inode.co.nz/archives/2007/11/09/index.html#e2007-11-09T03_51_54.txt" rel="nofollow noopener" target="_blank" title="http://nb.inode.co.nz/archives/2007/11/09/index.html#e2007-11-09T03_51_54.txt"&gt;http://nb.inode.co.nz/archi...&lt;/a&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">inode</dc:creator><pubDate>Thu, 08 Nov 2007 22:55:38 -0000</pubDate></item><item><title>Re: November 09, 2007 Archives | iNode: Nota Bene</title><link>http://nb.inode.co.nz/archives/2007/11/09/index.html?e2007-11-09T03_38_13.txt#comment-10196</link><description>&lt;p&gt;Meh. Once again I'm bitten by a bug in my markup parser -- I can't put !! at the end of a [link].&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">inode</dc:creator><pubDate>Thu, 08 Nov 2007 22:40:46 -0000</pubDate></item><item><title>Re: A thread per-article from a blog?</title><link>https://disqus.com/home/discussion/disqus/a_thread_per_article_from_a_blog/#comment-10178</link><description>&lt;p&gt;Yeah, some of the linking is odd -- it basically puts all blog entries from the same day on the same page, hence the anchoring to identify which one you want.&lt;/p&gt;&lt;p&gt;At this stage I think I'll have to 'ignore' this, certainly it isn't disqus' fault :-)&lt;/p&gt;&lt;p&gt;Thanks for that code snippet, now I know what to look for in embed.js I see the whole "if undefined" set of code :-) Some more stuff to play with! &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">inode</dc:creator><pubDate>Thu, 08 Nov 2007 21:29:53 -0000</pubDate></item><item><title>Re: A thread per-article from a blog?</title><link>https://disqus.com/home/discussion/disqus/a_thread_per_article_from_a_blog/#comment-10154</link><description>&lt;p&gt;The clue is a start, but a slightly targetted example would be better!&lt;/p&gt;&lt;p&gt;This is the blog template code at the moment :-&lt;/p&gt;&lt;p&gt;    &amp;lt; div class="posted"&amp;gt;&lt;br&gt;        &amp;lt; br /&amp;gt;$template_postedby &amp;lt; span class="item-creator"&amp;gt;$NB_EntryAuthor&amp;lt; /span&amp;gt;&lt;br&gt;$([ "$PERMALINKS" = "1" ] &amp;amp;&amp;amp; echo '| &amp;lt; a class="link" href="'${ARCHIVES_PATH}$NB_EntryPermalink'"&amp;gt;'$template_permlink'&amp;lt; /a&amp;gt;')&lt;br&gt;$([ ! -z "$NB_EntryCategories" ] &amp;amp;&amp;amp; echo "| $template_catlinks $NB_EntryCategories" |sed -e '{$ s/\,$//; }')&lt;br&gt;&amp;lt; div id="disqus_thread"&amp;gt;&amp;lt; /div&amp;gt;&amp;lt; script type="text/javascript" src="&lt;a href="http://disqus.com/forums/notabene/embed.js" rel="nofollow noopener" target="_blank" title="http://disqus.com/forums/notabene/embed.js"&gt;http://disqus.com/forums/no...&lt;/a&gt;"&amp;gt;&amp;lt; /script&amp;gt;&amp;lt; noscript&amp;gt;&amp;lt; a href="&lt;a href="http://notabene.disqus.com/?url=ref" rel="nofollow noopener" target="_blank" title="http://notabene.disqus.com/?url=ref"&gt;http://notabene.disqus.com/...&lt;/a&gt;"&amp;gt;View the forum thread.&amp;lt; /a&amp;gt;&amp;lt; /noscript&amp;gt;&lt;br&gt;    &amp;lt; /div&amp;gt;&lt;/p&gt;&lt;p&gt;So you can see that the URL of the article itself will be '${ARCHIVES_PATH}$NB_EntryPermalink'&lt;/p&gt;&lt;p&gt;However the Disqus code is purely generated by &amp;lt;script type="text/javascript" src="&lt;a href="http://disqus.com/forums/notabene/embed.js" rel="nofollow noopener" target="_blank" title="http://disqus.com/forums/notabene/embed.js"&gt;http://disqus.com/forums/no...&lt;/a&gt;"&amp;gt;&amp;lt;/script&amp;gt; and I don't know how to pass parameters into that (I'm not much of a javascript person)&lt;/p&gt;&lt;p&gt;I've grabbed that script, and it seems as if the implied link is coming via :-&lt;br&gt;var disqus_href = window.location.href;&lt;br&gt;This gets built up into disqus_url, which is passed into thread.js ...&lt;br&gt;disqus_script.src = '&lt;a href="http://disqus.com/forums/notabene/thread.js'" rel="nofollow noopener" target="_blank" title="http://disqus.com/forums/notabene/thread.js'"&gt;http://disqus.com/forums/no...&lt;/a&gt;&lt;br&gt;        + '?url='                       + encodeURI(disqus_url)&lt;/p&gt;&lt;p&gt;Do you think I should grab a local copy of embed.js and modify that, instead of using the one hosted on disqus? I don't think that's a good strategy as I'm sure to miss any development work that will go into that script over time ...&lt;/p&gt;&lt;p&gt;Or is there something else I've missed?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">inode</dc:creator><pubDate>Thu, 08 Nov 2007 20:22:48 -0000</pubDate></item><item><title>Re: November 05, 2007 Archives | iNode: Nota Bene</title><link>http://nb.inode.co.nz/archives/2007/11/05/index.html#comment-10134</link><description>&lt;p&gt;Thanks for that :-)&lt;br&gt;In practice I'm happy at the moment for the comment blocks to match the width of the articles, and they are well constrained by the containing div.&lt;/p&gt;&lt;p&gt;I'm sure to get into the css later on, to play with coloring and borders :-)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">inode</dc:creator><pubDate>Thu, 08 Nov 2007 18:48:55 -0000</pubDate></item><item><title>Re: November 05, 2007 Archives | iNode: Nota Bene</title><link>http://nb.inode.co.nz/archives/2007/11/05/index.html#comment-10119</link><description>&lt;p&gt;Comment from permalinked page (therefore different referrer)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">inode</dc:creator><pubDate>Thu, 08 Nov 2007 18:22:25 -0000</pubDate></item><item><title>Re: Password Security | rawiriblundell.com</title><link>http://www.rawiriblundell.com/?p=557#comment-2745844</link><description>&lt;p&gt;A decent enough set of recommendations. However your example of taking a long phrase and doing character substitution on it (Th3R4inIn$p41nF4llSM41nly0nTh3Pl41n ) doesn't add much entripy for random attack protection. It does help with over-the-shoulder or from-the-postit attacks.&lt;/p&gt;&lt;p&gt;Also have a look at Diceware &lt;a href="http://world.std.com/~reinhold/diceware.html" rel="nofollow noopener" target="_blank" title="http://world.std.com/~reinhold/diceware.html"&gt;http://world.std.com/~reinh...&lt;/a&gt; as they explain some of the maths, as well as present a system that I have used successfully (in different combinations) for years.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">inode</dc:creator><pubDate>Tue, 14 Aug 2007 19:25:46 -0000</pubDate></item></channel></rss>