Yes, I second&nbsp;Draicone,&nbsp;it&nbsp;should&nbsp;require&nbsp;an&nbsp;opt-in&nbsp;process&nbsp;of&nbsp;some&nbsp;description. <br><br><div><span class="gmail_quote">On 7/28/07, <b class="gmail_sendername"><a href="mailto:draicone@gmail.com">draicone@gmail.com</a></b>
 &lt;<a href="mailto:draicone@gmail.com">draicone@gmail.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
Any system like this should require opt-in. It isn&#39;t hard to code, and it avoids legal issues. Just require the user to make a dummy edit to their user page while logged in with a specific, self-explanatory edit summary, and check for it with the API, then maintain a database of verified users. Heck, we could even do this in a toolserver-wide process, with one opt-in system for all tools, and a centralised system with an API for checking if a user is verified. 
<br><br>--<br><span class="sg">Draicone<br></span><br>_______________________________________________<br>Toolserver-l mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:Toolserver-l@lists.wikimedia.org">
Toolserver-l@lists.wikimedia.org</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.wikimedia.org/mailman/listinfo/toolserver-l" target="_blank">http://lists.wikimedia.org/mailman/listinfo/toolserver-l
</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>Cheers, <br><br>Daniel Bryant<br><br><a href="http://en.wikipedia.org/wiki/User:Daniel">http://en.wikipedia.org/wiki/User:Daniel</a><br>Wikipedia: The Free Encyclopedia