<?xml version="1.0" encoding="utf-8"?>

























	
	



	
	
	

	
		
		
		

		
		
			
			
			
			
		
	
	
	
	
	
	


<rss version="2.0">	
	<channel>
		<title>Radiant Core: complaint tag</title>
		<link>http://www.radiantcore.com/</link>
		<description>All of the Radiant Core posts tagged with complaint.</description>
		<language>en-ca</language>
		<copyright>Copyright 2006, Radiant Core Inc. All rights reserved.</copyright>
		<managingEditor>webmaster@radiantcore.com</managingEditor>
		<webMaster>webmaster@radiantcore.com</webMaster>
		
			
			
			
			
			
			
			
			

			
				
			
			<item>
				<title><![CDATA[Web2.0 Expo: Powerless]]></title>
				<author>Jay Goldman &lt;info@radiantcore.com&gt;</author>
				<link>http://www.radiantcore.com/blog/archives/16/04/2007/web20expopower</link>
				<guid isPermaLink="true">http://www.radiantcore.com/blog/archives/16/04/2007/web20expopower</guid>
				<comments>http://www.radiantcore.com/blog/archives/16/04/2007/web20expopower#comments</comments>
				<description><![CDATA[A full update on Web2.0 Expo, including photos, is on the way. In the meantime, a quick note to conference organizers at large: providing a 'power room' where we can all go to recharge our laptops doesn't cut it. If you're planning a conference full of people with laptops, you need lots and lots of power in every session room. The number one complaint among the attendees is dead batteries and frustration at paying a hefty fee for a three day conference and not being given power. The wifi is pretty lackluster too - but that's becoming the norm for conferences, especially ones with thousands of attendees. <br /><br />I know running these events is hard work and they're not cheap by any means, but please, please, please remember that the two most important food sources in this ecosystem are abundant wireless and power. An ecosystem without those inputs dies pretty quicly.<br />]]></description>
				<category>Trip Reports</category>
				<pubDate>Mon, 16 Apr 2007 17:14:00 GMT</pubDate>
			</item>
		
	</channel>
</rss>