<?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: The Events of Failday</title>
	<atom:link href="http://trilema.com/2013/the-events-of-failday/feed/" rel="self" type="application/rss+xml" />
	<link>http://trilema.com/2013/the-events-of-failday/</link>
	<description>Moving targets for a fast crowd.</description>
	<pubDate>Thu, 14 May 2026 10:25:51 +0000</pubDate>
	<generator>http://polimedia.us</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: A Review of the Bitcoin Category on trilema.com &#171; Ossa Sepia</title>
		<link>http://trilema.com/2013/the-events-of-failday/#comment-148085</link>
		<dc:creator>A Review of the Bitcoin Category on trilema.com &#171; Ossa Sepia</dc:creator>
		<pubDate>Fri, 27 Mar 2020 19:33:04 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=46713#comment-148085</guid>
		<description>[...] the correct and incorrect ways to do business and business communications in Bitcoin, illustrated with examples and counterexamples. [...]</description>
		<content:encoded><![CDATA[<p>[...] the correct and incorrect ways to do business and business communications in Bitcoin, illustrated with examples and counterexamples. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MPEx breach - post mortem on Trilema - A blog by Mircea Popescu.</title>
		<link>http://trilema.com/2013/the-events-of-failday/#comment-139402</link>
		<dc:creator>MPEx breach - post mortem on Trilema - A blog by Mircea Popescu.</dc:creator>
		<pubDate>Mon, 06 Jan 2020 23:56:57 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=46713#comment-139402</guid>
		<description>[...] the possibility of technical breach shall be and should be the least of your concerns. Mind that BitInstant lost a few hundred BTC in a social engineering attack last year, mind that Lavabit ended up closed [...]</description>
		<content:encoded><![CDATA[<p>[...] the possibility of technical breach shall be and should be the least of your concerns. Mind that BitInstant lost a few hundred BTC in a social engineering attack last year, mind that Lavabit ended up closed [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
