<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Searching for Users by Email</title>
	<link>http://leahculver.com/2008/03/28/searching-for-users-by-email/</link>
	<description>leahculver.com</description>
	<pubDate>Thu, 21 Aug 2008 23:17:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: Mick</title>
		<link>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1092</link>
		<dc:creator>Mick</dc:creator>
		<pubDate>Sat, 05 Apr 2008 17:54:41 +0000</pubDate>
		<guid>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1092</guid>
		<description>Hey Leah,

I think that since you have added authentication to the Pownce API  go ahead and allow an email search function, just make sure that it is from a registered account.  Beyond that I assume that you track API usage by account / API key.  So keep an eye on the largest users of the email search, as I'm sure you keep an eye on other API functions.  

As for on the site, again, make sure that it is a registered user that is preforming the search, and again keep track of extreme usage.

However I think that you have to respect the user's privacy, if they have there email set to friends only they cant be included in the search.  

That is just my 2 cents.  

Also it is great to see you blogging again, keep it up :)</description>
		<content:encoded><![CDATA[<p>Hey Leah,</p>
<p>I think that since you have added authentication to the Pownce API  go ahead and allow an email search function, just make sure that it is from a registered account.  Beyond that I assume that you track API usage by account / API key.  So keep an eye on the largest users of the email search, as I&#8217;m sure you keep an eye on other API functions.  </p>
<p>As for on the site, again, make sure that it is a registered user that is preforming the search, and again keep track of extreme usage.</p>
<p>However I think that you have to respect the user&#8217;s privacy, if they have there email set to friends only they cant be included in the search.  </p>
<p>That is just my 2 cents.  </p>
<p>Also it is great to see you blogging again, keep it up <img src='http://leahculver.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Cedilotte</title>
		<link>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1091</link>
		<dc:creator>Daniel Cedilotte</dc:creator>
		<pubDate>Fri, 04 Apr 2008 19:05:39 +0000</pubDate>
		<guid>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1091</guid>
		<description>Don't allow it. If I trust you with my emails, it's not for you to turn around and hand it to 90 million spammers on the other side. Don't add a search by emails.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t allow it. If I trust you with my emails, it&#8217;s not for you to turn around and hand it to 90 million spammers on the other side. Don&#8217;t add a search by emails.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andrew woods</title>
		<link>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1086</link>
		<dc:creator>andrew woods</dc:creator>
		<pubDate>Wed, 02 Apr 2008 03:20:33 +0000</pubDate>
		<guid>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1086</guid>
		<description>I agree with the majority in that it should never be displayed. However, I think it would be ok to to use it internally for matching addresses of existing pownce users, but only displaying the names of the friends that match. that way you get the best of both worlds. btw you would not expose this in the public api. this matching would be internal only. As a developer that's how I would do it.

hope that helps.</description>
		<content:encoded><![CDATA[<p>I agree with the majority in that it should never be displayed. However, I think it would be ok to to use it internally for matching addresses of existing pownce users, but only displaying the names of the friends that match. that way you get the best of both worlds. btw you would not expose this in the public api. this matching would be internal only. As a developer that&#8217;s how I would do it.</p>
<p>hope that helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Hallock</title>
		<link>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1085</link>
		<dc:creator>Andrew Hallock</dc:creator>
		<pubDate>Mon, 31 Mar 2008 20:55:29 +0000</pubDate>
		<guid>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1085</guid>
		<description>Published and search-able email addresses are two different things.  Simply add a new privacy setting for whether or not your profile can be searched by email address.  Turn it on by default, but let users know there's a new privacy setting.  And I agree with Curtis, you should be logged in to search.

You have most of your bases covered by providing the address importer mechanism for the major email providers - but a lot of people store their contacts in Outlook.</description>
		<content:encoded><![CDATA[<p>Published and search-able email addresses are two different things.  Simply add a new privacy setting for whether or not your profile can be searched by email address.  Turn it on by default, but let users know there&#8217;s a new privacy setting.  And I agree with Curtis, you should be logged in to search.</p>
<p>You have most of your bases covered by providing the address importer mechanism for the major email providers - but a lot of people store their contacts in Outlook.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek</title>
		<link>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1084</link>
		<dc:creator>Derek</dc:creator>
		<pubDate>Sun, 30 Mar 2008 18:42:14 +0000</pubDate>
		<guid>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1084</guid>
		<description>I haven't sat down to think about it for more than 10 minutes of reading the post &#38; comments, but I think you should open it up for anyone via the API/Website.  If someone has your email, there's a reason why they have it, and I don't think there's any harm in saying "user with email X has a pownce account &lt;a href rel="nofollow"&gt;here&lt;/a&gt;".  Beyond that, it is up to the pownce user to determine whether or not to make their pownce updates available to the world, or just their friends.

The reason for not sharing your email via the pownce website has nothing to do with not wanting people to find you via your email address.  Don't tie the two together.  

Going one direction it is using someone's pownce account to determine their unique identifier (email). Going the other direction it is someone using your unique identifier (email) to determine your pownce account.</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t sat down to think about it for more than 10 minutes of reading the post &amp; comments, but I think you should open it up for anyone via the API/Website.  If someone has your email, there&#8217;s a reason why they have it, and I don&#8217;t think there&#8217;s any harm in saying &#8220;user with email X has a pownce account <a href rel="nofollow">here</a>&#8220;.  Beyond that, it is up to the pownce user to determine whether or not to make their pownce updates available to the world, or just their friends.</p>
<p>The reason for not sharing your email via the pownce website has nothing to do with not wanting people to find you via your email address.  Don&#8217;t tie the two together.  </p>
<p>Going one direction it is using someone&#8217;s pownce account to determine their unique identifier (email). Going the other direction it is someone using your unique identifier (email) to determine your pownce account.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edward Slipszenko</title>
		<link>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1083</link>
		<dc:creator>Edward Slipszenko</dc:creator>
		<pubDate>Sun, 30 Mar 2008 18:38:07 +0000</pubDate>
		<guid>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1083</guid>
		<description>I don't think it should be done. Imagine if someone tried to get all the friends of the "Pownce" user (the one that is used for making announcements) and got all there email addresses listed? Is that not going to be possible still? Surely username is enough identification?</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think it should be done. Imagine if someone tried to get all the friends of the &#8220;Pownce&#8221; user (the one that is used for making announcements) and got all there email addresses listed? Is that not going to be possible still? Surely username is enough identification?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: j</title>
		<link>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1082</link>
		<dc:creator>j</dc:creator>
		<pubDate>Sat, 29 Mar 2008 22:33:26 +0000</pubDate>
		<guid>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1082</guid>
		<description>Go ahead allow it ;)

It's a great way for automated bots to find email addresses that will work.

@gecko68: "People who do not know your email address wouldn't know what to use". Please. If your email address is shorter than 20 characters, a bot will eventually find it.

Dictionary attacks, anyone?

Even the captcha idea is defeated by OCR, just observe how good bots are nowadays at beating captchas.</description>
		<content:encoded><![CDATA[<p>Go ahead allow it <img src='http://leahculver.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>It&#8217;s a great way for automated bots to find email addresses that will work.</p>
<p>@gecko68: &#8220;People who do not know your email address wouldn&#8217;t know what to use&#8221;. Please. If your email address is shorter than 20 characters, a bot will eventually find it.</p>
<p>Dictionary attacks, anyone?</p>
<p>Even the captcha idea is defeated by OCR, just observe how good bots are nowadays at beating captchas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Isaac</title>
		<link>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1081</link>
		<dc:creator>Isaac</dc:creator>
		<pubDate>Sat, 29 Mar 2008 19:22:09 +0000</pubDate>
		<guid>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1081</guid>
		<description>Because being searchable by your email address and publishing the address aren't exactly the same thing but both could potentially be privacy issues, I suggest that you create a new preference bit that allows users to decide if they want to be found by their email address.

Then insert a small header into every page on the site saying something like "Pownce has introduced the option to be searchable by your email address. Do you want others to be able to find you using you email address?" with Yes and No buttons.

Leave the default as "no" in their user record unless they click on that Yes button. Problem solved.

I don't see a realistic way to keep this out of the API but I guess that's up to you guys. I think people understand that if they allow something on a site it can also be done by applications and tools that work with that site.</description>
		<content:encoded><![CDATA[<p>Because being searchable by your email address and publishing the address aren&#8217;t exactly the same thing but both could potentially be privacy issues, I suggest that you create a new preference bit that allows users to decide if they want to be found by their email address.</p>
<p>Then insert a small header into every page on the site saying something like &#8220;Pownce has introduced the option to be searchable by your email address. Do you want others to be able to find you using you email address?&#8221; with Yes and No buttons.</p>
<p>Leave the default as &#8220;no&#8221; in their user record unless they click on that Yes button. Problem solved.</p>
<p>I don&#8217;t see a realistic way to keep this out of the API but I guess that&#8217;s up to you guys. I think people understand that if they allow something on a site it can also be done by applications and tools that work with that site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noah</title>
		<link>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1080</link>
		<dc:creator>Noah</dc:creator>
		<pubDate>Sat, 29 Mar 2008 18:05:21 +0000</pubDate>
		<guid>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1080</guid>
		<description>You should allow for a user to enter in the email, and then return a message saying if the email exists then the user will be notified of a friend request.</description>
		<content:encoded><![CDATA[<p>You should allow for a user to enter in the email, and then return a message saying if the email exists then the user will be notified of a friend request.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eldin</title>
		<link>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1079</link>
		<dc:creator>Eldin</dc:creator>
		<pubDate>Sat, 29 Mar 2008 17:56:54 +0000</pubDate>
		<guid>http://leahculver.com/2008/03/28/searching-for-users-by-email/#comment-1079</guid>
		<description>I agree with Auguafresca.
Pownce already has the Find Friends feature, which is already "good enough" feature when it comes to Importing from other places.</description>
		<content:encoded><![CDATA[<p>I agree with Auguafresca.<br />
Pownce already has the Find Friends feature, which is already &#8220;good enough&#8221; feature when it comes to Importing from other places.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
