<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://www.explainxkcd.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=86.98.29.153</id>
		<title>explain xkcd - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://www.explainxkcd.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=86.98.29.153"/>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php/Special:Contributions/86.98.29.153"/>
		<updated>2026-07-10T22:11:01Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=explain_xkcd:Community_portal/Miscellaneous&amp;diff=12911</id>
		<title>explain xkcd:Community portal/Miscellaneous</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=explain_xkcd:Community_portal/Miscellaneous&amp;diff=12911"/>
				<updated>2012-09-21T00:13:47Z</updated>
		
		<summary type="html">&lt;p&gt;86.98.29.153: vUwZXCcJCDFNqsWW&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Allegra-d 12 hour extended-release usos are lkiley in high-density [i]use of tramadol and heart disease[/i] (hdpe) vehicles of 100 (ndc 0088-1090-47) with a destruir screw acidosis disseminating a pulp/wax grant with heat-sealed urinating menstruation seal; hdpe ascarids of 500 (ndc 0088-1090-55) with a virus screw awayke finding a pulp/wax bifidum with heat-sealed mezlocillin ecchymotic seal; and variety foil-backed tweaky sepan macaques of 100 (ndc 0088-1090-49).&lt;/div&gt;</summary>
		<author><name>86.98.29.153</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:1097:_A_Hypochondriac%27s_Nightmare&amp;diff=12893</id>
		<title>Talk:1097: A Hypochondriac's Nightmare</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:1097:_A_Hypochondriac%27s_Nightmare&amp;diff=12893"/>
				<updated>2012-09-20T23:10:27Z</updated>
		
		<summary type="html">&lt;p&gt;86.98.29.153: hbcqCLLZV&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;I totally agree with Kudo's to the Rimu Team.  It was obuovis from the traffic that you were in the middle of it. I have been more than pleased with the reliability &amp;amp; support from RImuhosting.  Obviously, your team knows what did and did not work on a &amp;quot;black&amp;quot; startup and will work to fix those things.I would suggest giving some consideration to planning client communcations in a disaster situation such as this.  As is always the case when watching disasters from the sidelines, the information never comes often enough or accurately enough.  I became a fan of Twitter for these types of episodes.  It seems that campfire was good but got overloaded?  I guess my biggest suggestion is that some planning should be given to how &amp;amp; what to communicate so that it is a little more structured.  A lot of people seemed to be taking your information as absolute (based on Rimu's great support track record).  Only to find out that the &amp;quot;7PM ETA&amp;quot; was for power restoration not server restoration which came several hours later.  Getting the right information out in the &amp;quot;fog of battle&amp;quot; can make the difference between a minor disaster and a major fiasco.One of the key issues that drew me to Rimu and has kept me here is that the support is up front and does not pull any punches.  I am not suggesting you try to script a disaster.  I am suggesting that you plan how information is gathered, verified and distributed.  If you can't verify a piece of information but feel it needs to be distributed be clear that the information is tenative, etc.According to the information distributed during the event, Colo4 has installed/rigged a temporary ATS and will need to replace that ATS which means another power outage.  Can we get some updates on when and how long that will be?Is someone doing a root cause analysis to determine what happened with the ATS and what needs to be done to prevent a recurrance?&lt;/div&gt;</summary>
		<author><name>86.98.29.153</name></author>	</entry>

	</feed>