<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
	<title>Comments for Singpolyma</title>
	
	<link>https://singpolyma.net</link>
	<description />
	<lastBuildDate>Wed, 01 Jul 2009 21:23:37 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/singpolyma-comments" type="application/rss+xml" /><item>
		<title>Comment on rel=prev/next for WordPress by Stephen Paul Weber</title>
		<link>http://feedproxy.google.com/~r/singpolyma-comments/~3/nN-lCHQ7ppc/</link>
		<dc:creator>Stephen Paul Weber</dc:creator>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://singpolyma.net/?p=446#comment-155302</guid>
		<description>There's only been one release since I published this patch, and no, this patch has not yet been mainlined :)</description>
		<content:encoded><![CDATA[<p>There&#039;s only been one release since I published this patch, and no, this patch has not yet been mainlined <img src='https://singpolyma.net/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	<feedburner:origLink>https://singpolyma.net/2009/05/rel-prev-next-wordpress/comment-page-1/#comment-155302</feedburner:origLink></item>
	<item>
		<title>Comment on rel=prev/next for WordPress by Srinivas</title>
		<link>http://feedproxy.google.com/~r/singpolyma-comments/~3/_uhTEFtS0iA/</link>
		<dc:creator>Srinivas</dc:creator>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://singpolyma.net/?p=446#comment-155301</guid>
		<description>Has it been rectified in the newer versions of wordpress releases?</description>
		<content:encoded><![CDATA[<p>Has it been rectified in the newer versions of wordpress releases?</p>
]]></content:encoded>
	<feedburner:origLink>https://singpolyma.net/2009/05/rel-prev-next-wordpress/comment-page-1/#comment-155301</feedburner:origLink></item>
	<item>
		<title>Comment on Discovering OpenPGP Keys Over HTTP by Stephen Paul Weber</title>
		<link>http://feedproxy.google.com/~r/singpolyma-comments/~3/muGItVhgrmU/</link>
		<dc:creator>Stephen Paul Weber</dc:creator>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://singpolyma.net/?p=480#comment-155299</guid>
		<description>It seems that X.509 certs have no registered MIME type, or even a single standard file format.  It seems that PEM is just base64-encoded DER (with PGP-armour-style header/footer).  And that both PEM and DER are often served using application/x-x509-ca-cert or application/x-x509-user-cert</description>
		<content:encoded><![CDATA[<p>It seems that X.509 certs have no registered MIME type, or even a single standard file format.  It seems that PEM is just base64-encoded DER (with PGP-armour-style header/footer).  And that both PEM and DER are often served using application/x-x509-ca-cert or application/x-x509-user-cert</p>
]]></content:encoded>
	<feedburner:origLink>https://singpolyma.net/2009/06/discovering-openpgp-keys-over-http/comment-page-1/#comment-155299</feedburner:origLink></item>
	<item>
		<title>Comment on Customer Service Comparison by randy stewart</title>
		<link>http://feedproxy.google.com/~r/singpolyma-comments/~3/bgEoxIw-xwo/</link>
		<dc:creator>randy stewart</dc:creator>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://singpolyma.net/?p=468#comment-155297</guid>
		<description>Stephen-

Just to preface, the Boxbe Public Email service that you use is only used by a tiny percentage of our members.  While the service isn't orphaned, we don't expect to be doing a lot of development around it in the future.

Given that, I don't expect we'd be developing the feature that you describe in question 2.  If more of our users started to use the Public Email service, this may change.

For question 3, we may develop a "Boxbe for your Domain" in the future, but no specific plan to offer what you've suggested.  We'll keep the wildcard in mind, but I would imagine that processing all of the mail from *@&lt;a href="http://domain.com/" rel="nofollow"&gt;domain.com&lt;/a&gt; would be prohibitively expensive for us to filter as part of a free product offering. 

Additionally, in our experience, the signal to noise ratio there would be very, very low.

Cheers,
Randy Stewart </description>
		<content:encoded><![CDATA[<p>Stephen-</p>
<p>Just to preface, the Boxbe Public Email service that you use is only used by a tiny percentage of our members.  While the service isn&#039;t orphaned, we don&#039;t expect to be doing a lot of development around it in the future.</p>
<p>Given that, I don&#039;t expect we&#039;d be developing the feature that you describe in question 2.  If more of our users started to use the Public Email service, this may change.</p>
<p>For question 3, we may develop a &#034;Boxbe for your Domain&#034; in the future, but no specific plan to offer what you&#039;ve suggested.  We&#039;ll keep the wildcard in mind, but I would imagine that processing all of the mail from *@<a href="http://domain.com/" rel="nofollow">domain.com</a> would be prohibitively expensive for us to filter as part of a free product offering. </p>
<p>Additionally, in our experience, the signal to noise ratio there would be very, very low.</p>
<p>Cheers,<br />
Randy Stewart</p>
]]></content:encoded>
	<feedburner:origLink>https://singpolyma.net/2009/06/customer-service-comparison/comment-page-1/#comment-155297</feedburner:origLink></item>
	<item>
		<title>Comment on Facebook Trademark Threat by Alex Frakking</title>
		<link>http://feedproxy.google.com/~r/singpolyma-comments/~3/5SfmoppJZjQ/</link>
		<dc:creator>Alex Frakking</dc:creator>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid isPermaLink="false">https://singpolyma.net/?p=486#comment-155296</guid>
		<description>Looks like facebook trademarked "THE WALL" in the US (June 2006, no. 78920335). 

What else did they trademark? I only found 32, including:
FACE
POKE
32665 (texting number)
F
PARAKEY (a 2007 acquisition: http://www.techcrunch.com/2007/07/19/breaking-facebook-has-acquired-parakey/) - now abandoned
GIVE YOUR COMPUTER THE BIRD (related to above)
FANSUMER
FACEBOOK FOR GOOD
SOUNDBOARD

Of course these only apply in certain trademark classes, which generally involve social networking. So we don't all have to pry the "F" key off our keyboards... yet. ;)</description>
		<content:encoded><![CDATA[<p>Looks like facebook trademarked &#034;THE WALL&#034; in the US (June 2006, no. 78920335). </p>
<p>What else did they trademark? I only found 32, including:<br />
FACE<br />
POKE<br />
32665 (texting number)<br />
F<br />
PARAKEY (a 2007 acquisition: <a href="http://www.techcrunch.com/2007/07/19/breaking-facebook-has-acquired-parakey/)" rel="nofollow">http://www.techcrunch.com/2007/07/19/breaking-facebook-has-acquired-parakey/)</a> &#8211; now abandoned<br />
GIVE YOUR COMPUTER THE BIRD (related to above)<br />
FANSUMER<br />
FACEBOOK FOR GOOD<br />
SOUNDBOARD</p>
<p>Of course these only apply in certain trademark classes, which generally involve social networking. So we don&#039;t all have to pry the &#034;F&#034; key off our keyboards&#8230; yet. <img src='https://singpolyma.net/wordpress/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	<feedburner:origLink>https://singpolyma.net/2009/06/facebook-trademark-threat/comment-page-1/#comment-155296</feedburner:origLink></item>
</channel>
</rss>
