<?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>the Guppie Life &#187; Reputation Management</title>
	<atom:link href="http://guppielife.com/category/reputation-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://guppielife.com</link>
	<description>Adventures of a Gay Yuppie</description>
	<lastBuildDate>Thu, 15 Jan 2009 04:57:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Don&#8217;t Let Interlopers Muddle Your Message</title>
		<link>http://guppielife.com/2008/08/13/dont-let-interlopers-muddle-your-message/</link>
		<comments>http://guppielife.com/2008/08/13/dont-let-interlopers-muddle-your-message/#comments</comments>
		<pubDate>Wed, 13 Aug 2008 11:00:11 +0000</pubDate>
		<dc:creator>AJ</dc:creator>
				<category><![CDATA[Reputation Management]]></category>

		<guid isPermaLink="false">http://guppielife.com/?p=223</guid>
		<description><![CDATA[<!-- encryptx:  /  --><!-- linktext:  /  -->I was mean to someone tonight, but it all worked out and I made a new blogger friend instead.
He&#8217;s Jun Loayza from Living the Startup Life. I noticed him after one of his posts came up on the Brazen Careerist homepage.

When I clicked over to his blog to leave a comment, I was pretty shocked [...]<p>From <a href="http://guppielife.com">the Guppie Life</a><br/><br/><a href="http://guppielife.com/2008/08/13/dont-let-interlopers-muddle-your-message/">Don&#8217;t Let Interlopers Muddle Your Message</a></p>
]]></description>
			<content:encoded><![CDATA[<!-- encryptx:  /  --><!-- linktext:  /  --><p>I was mean to someone tonight, but it all worked out and I made a new blogger friend instead.</p>
<p>He&#8217;s Jun Loayza from <a href="http://www.junloayza.com/">Living the Startup Life</a>. I noticed him after one of his posts came up on the <a href="http://www.brazencareerist.com/">Brazen Careerist</a> homepage.</p>
<p><a href="http://www.brazencareerist.com/2008/08/12/in-my-experience-sex-is-probably-overrated/"><img src="http://guppielife.com/blog/wp-content/uploads/2008/08/picture-2.png" alt="Brazen Careerist - Edited title" title="Brazen Careerist title" width="499" height="272" class="size-full wp-image-224" style="border: 1px solid;" /></a></p>
<p>When I clicked over to his blog to leave a comment, I was pretty shocked by his original title.</p>
<p><a href="http://www.junloayza.com/2008/08/sex-is-overrated/"><img src="http://guppielife.com/blog/wp-content/uploads/2008/08/picture-1.png" alt="Living the Startup Life - Original title" title="Living the Startup Life - Original title" width="500" height="234" class="size-full wp-image-225" style="border: 1px solid;"/></a></p>
<p>The editor for the Brazen Careerist network (<a href="http://guppielife.com/2008/04/30/brazen-careerist-blogger-network/">of which I am a member</a>) decided that &#8220;In My Experience, Sex is Probably Overrated&#8221; was a stronger title than the original &#8220;Sex is Overrated.&#8221;</p>
<p>Really, Brazen Careerist editor? Really?</p>
<p>For one thing  (and correct me if I&#8217;m wrong, gentle readers), &#8220;in my experience&#8221; is already implied. The Brazen Careerist is a network of personal bloggers. Just about any post on the network could theoretically be prefixed with &#8220;in my experience,&#8221; but that adds no meaning or value. It only adds extra wordiness to an otherwise eye-popping, attention-grabbing title.</p>
<p>But the bigger crime is the &#8220;Probably.&#8221; What a surefire way to sound like you lack confidence! In the edited title, it sounds like Jun is unsure of his central thesis when in fact he is opinionated and articulate.</p>
<p>However, <strong>this isn&#8217;t an attack</strong> on the Brazen Careerist editor(s). (<em>Even though they never feature my witty, witty posts&#8230; grrr.</em>) I&#8217;m sure they&#8217;ve got a lot of blog posts to deal with and didn&#8217;t give this title much thought at all.</p>
<p>This is a <strong>life lesson</strong>. Really.</p>
<p><strong>The lesson is this:</strong> Other people do not care about you. Not as much as you do. At the end of the day, you&#8217;re the one who looks dull when your article/report/blog gets edited into mediocrity.</p>
<p>Is this particular an example a big deal? No&#8230; well, not to me. But <em>that&#8217;s the point:</em> Maybe it&#8217;s a big deal to Jun. What if this blog post had been his personal shining moment of glory?</p>
<p>I run into similar scenarios nearly everyday at work, where I help our clients develop websites. There are generally two types of client.</p>
<ol>
<li>The &#8220;you deal with it&#8221; client</li>
<li>The take-charge control freak</li>
</ol>
<p>Guess which one ends up with the awesome website?</p>
<p>It&#8217;s the control freaks, of course, but not necessarily because they have undiagnosed OCD. They&#8217;re the ones that <em>care</em> about how I&#8217;m crafting their online reputation. They&#8217;re the ones that argue with me about their sites. </p>
<p>It&#8217;s not that I purposefully don&#8217;t try as hard for the lackadaisical clients. I try to build everyone the best website possible&mdash;but the client&#8217;s business is not my business. I can&#8217;t possibly know their businesses like they do.</p>
<p>It&#8217;s the same with you and the middle-men with which you choose to associate. Every time you join an organization, get a new client, or start a new job, you&#8217;re handing over the keys to a little piece of your personal reputation.</p>
<p>Sometimes it&#8217;s not such a big deal. Sometimes it is. Either way, it&#8217;s <em>your</em> butt on the line when interlopers muddle your own personal brand.</p>
<p>From <a href="http://guppielife.com">the Guppie Life</a><br/><br/><a href="http://guppielife.com/2008/08/13/dont-let-interlopers-muddle-your-message/">Don&#8217;t Let Interlopers Muddle Your Message</a></p>
<img src="http://guppielife.com/blog/?ak_action=api_record_view&id=223&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://guppielife.com/2008/08/13/dont-let-interlopers-muddle-your-message/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>PRWeek Makes Public Relations Disaster, Violates User Privacy</title>
		<link>http://guppielife.com/2008/01/30/prweek-makes-public-relations-disaster-violates-user-privacy/</link>
		<comments>http://guppielife.com/2008/01/30/prweek-makes-public-relations-disaster-violates-user-privacy/#comments</comments>
		<pubDate>Thu, 31 Jan 2008 04:23:32 +0000</pubDate>
		<dc:creator>AJ</dc:creator>
				<category><![CDATA[Reputation Management]]></category>

		<guid isPermaLink="false">http://guppielife.com/2008/01/30/prweek-makes-public-relations-disaster-violates-user-privacy/</guid>
		<description><![CDATA[<!-- encryptx:  /  --><!-- linktext:  /  -->Over the course of the past two days, I have received over 200 emails from PRWeekJobs.com urging me to &#8220;Upload Your Resume at the New PRWeekjobs.com for a Chance to win an iPod.&#8221;
As if the email overload wasn&#8217;t enough of an annoyance, each email contained the actual email address and password for the PRWeek account [...]<p>From <a href="http://guppielife.com">the Guppie Life</a><br/><br/><a href="http://guppielife.com/2008/01/30/prweek-makes-public-relations-disaster-violates-user-privacy/">PRWeek Makes Public Relations Disaster, Violates User Privacy</a></p>
]]></description>
			<content:encoded><![CDATA[<!-- encryptx:  /  --><!-- linktext:  /  --><p>Over the course of the past two days, I have received over 200 emails from PRWeekJobs.com urging me to &#8220;Upload Your Resume at the New PRWeekjobs.com for a Chance to win an iPod.&#8221;</p>
<p>As if the email overload wasn&#8217;t enough of an annoyance, each email contained the actual email address and <em>password</em> for the PRWeek account of the intended recipient. These email addresses and passwords were sent to hundreds of other strangers with PRWeek.com accounts. </p>
<p>I personally did not receive an email containing my own email and password, but I have no way of knowing if my own personal information was sent to others.</p>
<p>That is an utter disaster and a colossal security risk, considering that many people use the same email address and password for dozens of internet accounts.</p>
<p>PRWeek&#8217;s response? A <a href="http://www.prweekus.com/Adicio-issues-formal-apology-regarding-PRWeek-e-mail-problem/article/104713/">lame apology on the PRWeek website</a> from Adicio, the company apparently responsible for the technical glitch, and a similarly lame email from the editor of PRWeek:</p>
<blockquote><p>
From the desk of Julia Hood, Editor-in-Chief of PRWeek</p>
<p>Date: January 30, 2008</p>
<p>I am writing to personally apologize for the error that caused your PRWeekjobs.com user name and password information to be distributed externally. I am also sorry if you received our job site email multiple times and that your email address was cc&#8217;d to other respondents.</p>
<p>I want to provide you with background on how this happened; what we have been doing to fix the situation; and what action you may be able to take to limit the extent of this inconvenience. The error originated with our vendor, Adicio, via a technical error, during their work on our behalf with an automated software migration package. When this problem was discovered, just minutes after the project began, Adicio immediately took mitigating action ceasing the transmission and disabling all user names and passwords. This problem impacted a limited portion of registrants to a PRWeek service. Adicio&#8217;s explanation and apology is currently on our website:<br />
http://www.prweekus.com/Adicio-issues-formal-apology-regarding-PRWeek-e-mail-problem/article/104713/</p>
<p>Unfortunately, I know that some of you may still be receiving emails. If that is the case, it is likely that these emails are being bottlenecked at your ISP. Please refer to the list below for obtaining advice on how to stop this from happening in your individual system.</p>
<p>- Contact your ISP and request they remove the spam emails<br />
  awaiting delivery from you (the top ISP contact details<br />
  are included below). PRWeek is also alerting ISPs of this<br />
  problem<br />
- If your company owns an email server, contact your Systems<br />
  Administrator and request that they block the specific<br />
  email address in its Spam filter<br />
- Block the senders email address on your system<br />
- For peace of mind, change the passwords for other online<br />
  services you use for which you have been using the same<br />
  password</p>
<p>I know you have been inconvenienced and, even more importantly, are concerned about the privacy of your information. This error may have also shaken your confidence in working and engaging with PRWeek. Again, I offer my sincere apology, as well as my promise to you that we will do everything possible to ensure that this never happens again. I realize it will take time for us to earn your trust again, but we value our dialogue with you and hope it will continue and that we can move past this very unfortunate occurrence. </p>
<p>Please feel free to contact me directly with further questions and concerns. My information is at the bottom of this email.</p>
<p>Best Regards,<br />
Julia Hood<br />
Editor-in-Chief, PRWeek<br />
114 W. 26th Street<br />
New York, NY 10001<br />
P: 646-638-6031<br />
mailto:&#74;ulia.ho&#111;d&#64;p&#114;w&#101;e&#107;.&#99;&#111;&#109;
</p></blockquote>
<p>Well, gee. They feel <em>really bad</em> about this mix-up. They explained how to stop receiving the emails, but only 2 days after I began receiving them in the first place. Worse yet, PRWeek didn&#8217;t mention how they intend to make this right. To me, the most immediate and automatic response should have been a few years&#8217; of free subscriptions and some sort of credit report monitoring (in case the email and passwords also granted access to bank or credit card accounts). Honestly, I don&#8217;t think monetary compensation is entirely unreasonable, and I wouldn&#8217;t be surprised if they&#8217;re faced with a lawsuit.</p>
<p>Luckily for me, the password associated with my PRWeek account was unique. </p>
<p>But what can <strong>you</strong> learn from this PRWeek privacy debacle?</p>
<ul>
<li>Use a dedicated email when signing up for new accounts with various websites. The email address should be nonsensical and should not contain personally identifying information. I&#8217;d be in a lot of trouble if I had signed up for PRWeek with &#8220;&#102;irs&#116;na&#109;&#101;&#46;&#108;astnam&#101;&#64;&#109;yc&#111;&#109;pany&#46;&#99;&#111;m.&#8221; Instead I used something along the lines of &#8220;r&#97;&#110;d&#111;&#109;&#45;&#119;o&#114;&#100;s-&#97;&#110;&#100;&#45;n&#117;&#109;&#98;&#101;rs&#64;g&#109;&#97;&#105;&#108;&#46;&#99;o&#109;.&#8221;</li>
<li>Use a different password for each account. I know it&#8217;s a pain, but so is having your online accounts hacked.</li>
<li>Don&#8217;t give out personal information without a valid reason, even if the company seems reputable. However, keep in mind that even honest people make mistakes.</li>
<li>Don&#8217;t piss off people who blog ;)</li>
</ul>
<p>From <a href="http://guppielife.com">the Guppie Life</a><br/><br/><a href="http://guppielife.com/2008/01/30/prweek-makes-public-relations-disaster-violates-user-privacy/">PRWeek Makes Public Relations Disaster, Violates User Privacy</a></p>
<img src="http://guppielife.com/blog/?ak_action=api_record_view&id=47&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://guppielife.com/2008/01/30/prweek-makes-public-relations-disaster-violates-user-privacy/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
