<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
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:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>IPHere &#187; Learned</title> <atom:link href="https://www.iphere.com/tag/learned/feed" rel="self" type="application/rss+xml" /><link>https://www.iphere.com</link> <description>We show your current IP</description> <lastBuildDate>Wed, 03 Aug 2022 14:13:56 +0000</lastBuildDate> <language>en-US</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.6.1</generator> <item><title>Lessons Learned From N.Y. Times Hack Attack</title><link>https://www.iphere.com/lessons-learned-from-n-y-times-hack-attack</link> <comments>https://www.iphere.com/lessons-learned-from-n-y-times-hack-attack#comments</comments> <pubDate>Fri, 30 Aug 2013 14:13:19 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[Attack]]></category> <category><![CDATA[from]]></category> <category><![CDATA[Hack]]></category> <category><![CDATA[Learned]]></category> <category><![CDATA[Lessons]]></category> <category><![CDATA[N.Y.]]></category> <category><![CDATA[Times]]></category> <guid
isPermaLink="false">http://www.iphere.com/lessons-learned-from-n-y-times-hack-attack</guid> <description><![CDATA[What might The New York Times &#8212; and to a lesser extent, Twitter &#8212; have done differently to prevent Tuesday&#8217;s hack attack that disrupted access to their sites? The disruptions began after the Syrian Electronic Army (SEA), a group of hackers that back Syrian President Bashar al-Assad in the country&#8217;s civil war, hacked into the [&#8230;]]]></description> <wfw:commentRss>https://www.iphere.com/lessons-learned-from-n-y-times-hack-attack/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>3 Lessons Learned from Feds&#8217; Data Center Consolidation</title><link>https://www.iphere.com/3-lessons-learned-from-feds-data-center-consolidation</link> <comments>https://www.iphere.com/3-lessons-learned-from-feds-data-center-consolidation#comments</comments> <pubDate>Mon, 05 Aug 2013 20:13:25 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[center]]></category> <category><![CDATA[Consolidation]]></category> <category><![CDATA[data]]></category> <category><![CDATA[Feds']]></category> <category><![CDATA[from]]></category> <category><![CDATA[Learned]]></category> <category><![CDATA[Lessons]]></category> <guid
isPermaLink="false">http://www.iphere.com/3-lessons-learned-from-feds-data-center-consolidation</guid> <description><![CDATA[Three years after officials launched an initiative to reduce the number of federal data centers, the count has only increased. The fiasco offers lessons for IT executives managing their own consolidation plans. Network Computing]]></description> <wfw:commentRss>https://www.iphere.com/3-lessons-learned-from-feds-data-center-consolidation/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Lessons Learned from SNW 2013</title><link>https://www.iphere.com/lessons-learned-from-snw-2013</link> <comments>https://www.iphere.com/lessons-learned-from-snw-2013#comments</comments> <pubDate>Wed, 01 May 2013 08:12:42 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[2013]]></category> <category><![CDATA[from]]></category> <category><![CDATA[Learned]]></category> <category><![CDATA[Lessons]]></category> <guid
isPermaLink="false">http://www.iphere.com/lessons-learned-from-snw-2013</guid> <description><![CDATA[I picked up on two important trends at SNW 2013, including the role that IT can play as an internal broker for public cloud services, and the reasons enterprises are moving cautiously on emerging technology. Network Computing]]></description> <wfw:commentRss>https://www.iphere.com/lessons-learned-from-snw-2013/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>IBM Pulse 2013: Lessons Learned</title><link>https://www.iphere.com/ibm-pulse-2013-lessons-learned</link> <comments>https://www.iphere.com/ibm-pulse-2013-lessons-learned#comments</comments> <pubDate>Thu, 28 Mar 2013 02:12:43 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[2013]]></category> <category><![CDATA[Learned]]></category> <category><![CDATA[Lessons]]></category> <category><![CDATA[Pulse]]></category> <guid
isPermaLink="false">http://www.iphere.com/ibm-pulse-2013-lessons-learned</guid> <description><![CDATA[Three compelling themes emerged from IBM&#8217;s annual gathering: the continued diffusion of the data center, the need for open cloud standards and the rise of data-driven IT intelligence. Network Computing]]></description> <wfw:commentRss>https://www.iphere.com/ibm-pulse-2013-lessons-learned/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>3 Lessons Learned from Wireless Field Day</title><link>https://www.iphere.com/3-lessons-learned-from-wireless-field-day</link> <comments>https://www.iphere.com/3-lessons-learned-from-wireless-field-day#comments</comments> <pubDate>Tue, 19 Feb 2013 20:12:52 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[Field]]></category> <category><![CDATA[from]]></category> <category><![CDATA[Learned]]></category> <category><![CDATA[Lessons]]></category> <category><![CDATA[Wireless]]></category> <guid
isPermaLink="false">http://www.iphere.com/3-lessons-learned-from-wireless-field-day</guid> <description><![CDATA[WLAN location-based services are hot, wireless technology is getting more complex, and WLAN interoperability just isn&#8217;t going to happen. These are the three big ideas I took away from Wireless Field Day. Network Computing]]></description> <wfw:commentRss>https://www.iphere.com/3-lessons-learned-from-wireless-field-day/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Ubuntu Linux, Day 30: What I Learned from 30 Days With Ubuntu Linux</title><link>https://www.iphere.com/ubuntu-linux-day-30-what-i-learned-from-30-days-with-ubuntu-linux</link> <comments>https://www.iphere.com/ubuntu-linux-day-30-what-i-learned-from-30-days-with-ubuntu-linux#comments</comments> <pubDate>Fri, 01 Jul 2011 14:14:27 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[Days]]></category> <category><![CDATA[from]]></category> <category><![CDATA[Learned]]></category> <category><![CDATA[Linux]]></category> <category><![CDATA[Ubuntu]]></category> <guid
isPermaLink="false">http://www.iphere.com/ubuntu-linux-day-30-what-i-learned-from-30-days-with-ubuntu-linux</guid> <description><![CDATA[30 Days With Ubuntu Linux: Day 30 Ubuntu Linux was a pleasant surprise. If I had to sum up my 30 Days With Ubuntu Linux in a sentence, it would be &#8220;Ubuntu Linux is more than capable of being the primary desktop OS for most users, but the learning curve will have some bumps.&#8221; The [&#8230;]]]></description> <wfw:commentRss>https://www.iphere.com/ubuntu-linux-day-30-what-i-learned-from-30-days-with-ubuntu-linux/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>