Non-commercial versus commercial usage

david wrote:

Progress is already being made in this area... A commercial stand-alone version of CoovaAAA is in the works. We are also committed in keeping the free CoovaAAA service up and running. As such, we will have to review the usage policy and load of the servers.

I'm thinking that perhaps you are considering restricting free CoovaAAA to non-commercial use.
If so you might consider implementing a feature that would permit the user of an "access code" to view both their usage details and a summary of the account overall usage details. This would assist them determining whether the account is being used for commercial purposes.

Re: Non-commercial versus commercial usage

For those that are wondering about the definition of "non-commercial" take a look at the following link: http://www.acma.gov.au/WEB/STANDARD/pc=PC_1766.
In the "Household Usage" topic (http://coova.org/phpBB3/viewtopic.php?f=7&t=430) I start by indicating that I came to Coova after experiencing Meraki. For a long time I was puzzled by design of their system in that it monitors running totals rather than cumulative totals for data transfers and does not include the ability to interrupt users sessions. Meraki offer Carrier Edition, which addresses both of these issues but you need at least 100 nodes to qualify for it. I think I now understand why.
Although the above link refers to Australian law, I suspect it applies to democracies generally. It has been said that democracy is the process by which we get ourselves organized to perform capitalism. There is a lot of capital tied up in data networks and you need laws like this to regulate things.
I see Coova as a champion of non-commercial networks (the commercial market is getting very crowded). I'm glad that David has stated that he will continue to provide free CoovaAAA, but I suspect he will welcome suggestions on how he can avoid free CoovaAAA being exploited by purely commercial interests.

Re: Non-commercial versus commercial usage

I second the motion on this idea.

I'm thinking this could be implemented by allowing an access code user to login to the CoovaAAA portal using his access code and being able to view his usage details.