<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: New section added to Mozealous.com</title>
	<atom:link href="http://www.mozealous.com/new-section-added-to-mozealouscom/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mozealous.com/new-section-added-to-mozealouscom/</link>
	<description>Articulate technology and tech usability.</description>
	<lastBuildDate>Fri, 06 Jan 2012 16:40:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dave Mozealous</title>
		<link>http://www.mozealous.com/new-section-added-to-mozealouscom/comment-page-1/#comment-636</link>
		<dc:creator>Dave Mozealous</dc:creator>
		<pubDate>Wed, 13 May 2009 13:05:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.mozealous.com/?p=230#comment-636</guid>
		<description>Sounds cool Sam.  All of what you are looking to do is possible with the AO API, and doesn&#039;t require much to modify my code to get what you are looking for.

&gt;is there a way to put an “expiration date’ with a user, so that after a certain period of time, say 1 year, their user name will not work?

Currently there is not an API function to set an expiration date, but it wouldn&#039;t be hard to setup a program, using the API to automatically remove access for the user.

Good luck.</description>
		<content:encoded><![CDATA[<p>Sounds cool Sam.  All of what you are looking to do is possible with the AO API, and doesn&#8217;t require much to modify my code to get what you are looking for.</p>
<p>&gt;is there a way to put an “expiration date’ with a user, so that after a certain period of time, say 1 year, their user name will not work?</p>
<p>Currently there is not an API function to set an expiration date, but it wouldn&#8217;t be hard to setup a program, using the API to automatically remove access for the user.</p>
<p>Good luck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Kamin</title>
		<link>http://www.mozealous.com/new-section-added-to-mozealouscom/comment-page-1/#comment-635</link>
		<dc:creator>Sam Kamin</dc:creator>
		<pubDate>Wed, 13 May 2009 10:25:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.mozealous.com/?p=230#comment-635</guid>
		<description>Hi Dave - this is very interesting.  I am in my 30 day free AO time.  This self-registration is interesting.  We want to pay for people to enter our potential AO site, but we also want some authentication.  When they self-register, we want to ensure that this person is actually a customer of ours.  Once authenticated, another window should come up as some kind of confirmation that they must agree to and states that they will be billed the $X.  If they confirm, we would want not only an email sent to them, but also to our Finance department as a way of letting them know to get a PO to the customer.  The customer can get in before paying, but they should understand that the PO will be sent.

Also - is there a way to put an &quot;expiration date&#039; with a user, so that after a certain period of time, say 1 year,  their user name will not work?

Thanks Dave,

Sam</description>
		<content:encoded><![CDATA[<p>Hi Dave &#8211; this is very interesting.  I am in my 30 day free AO time.  This self-registration is interesting.  We want to pay for people to enter our potential AO site, but we also want some authentication.  When they self-register, we want to ensure that this person is actually a customer of ours.  Once authenticated, another window should come up as some kind of confirmation that they must agree to and states that they will be billed the $X.  If they confirm, we would want not only an email sent to them, but also to our Finance department as a way of letting them know to get a PO to the customer.  The customer can get in before paying, but they should understand that the PO will be sent.</p>
<p>Also &#8211; is there a way to put an &#8220;expiration date&#8217; with a user, so that after a certain period of time, say 1 year,  their user name will not work?</p>
<p>Thanks Dave,</p>
<p>Sam</p>
]]></content:encoded>
	</item>
</channel>
</rss>

