[wp-hackers] a pay per view wordpress plugin

David Chait davebytes at comcast.net
Tue Jun 27 17:06:27 GMT 2006

What you refer to at the end there is what I outlined in my earlier email as 
the 'more secure' system...  But no extra 'ACL' really, just store the 
'purchased' access codes in the user's metadata, which would require users 
to register to use your system.  Whether the access codes are per-post or 
for a 'category' of posts is (somewhat) up to the need/use of the system.

The 'less secure' system can still be done easily, it's just less secure. 
(see my earlier email for the various incarnations I outlined.. ;) ).


----- Original Message ----- 
From: "Nathan White" <changereality at gmail.com>
To: <wp-hackers at lists.automattic.com>
Sent: Tuesday, June 27, 2006 12:54 PM
Subject: Re: [wp-hackers] a pay per view wordpress plugin

| >
| > Before Step one i need a kind of reference code for each post, for
| > example the user will have to send the sms to
| > http://www.smsconnect.com/ with a specific code (in order to receive a
| > specific unlock code for the desired post).
| I personally feel that you should be using some type of ACL to manage this
| project, because then you would have room to grow. Then you can assign
| members based on subscription types to different groups or topics. Then 
| could have a drop down list or a hierarchical checkbox list just like the
| categories for a post. Then you don't have to worry about the code
| assignment or memorization. In this system each user would have there own
| unique code. This way you could lock out a user even if they have a code 
| there is more security and less change of a system compromise. You could
| have the code be assigned when the user creates there account. Or it could
| be as simple as the phone number they are SMSing from.

More information about the wp-hackers mailing list