If info (name/email/password) entered (manually or from cookie), check against database. If valid, and user is not blocked, submit entry to the 'edits' database, with corresponding user ID attached. If current IP has not been logged, log it. Check info against cookie: if no cookie, create; if mismatching cookie, delete and create new. If info mismatch against database, send error message. If user is blocked, send error message.
If no info entered (manually or from cookie), check IP against database. If IP attached to existing user, check if blocked. If user blocked, send error message. If not blocked, prompt for login. If login declined, create new user ID with IP address; attach new user ID to entry, and submit to 'edits' database. If IP not attached to existing user, create new user ID with IP address; attach new user ID to entry, and submit to 'edits' database. Create new cookie for user ID.
Am also thinking of overwriting cookies so they remain in the system.. deleting old, each time an entry is made, and replacing it with a new cookie, set to expire at a later date. User files will be editable (change name/email/password), once one is logged in (registration/login not required to use site.. info simply maintained on each user to keep people from abusing the site). The interesting thing will be users who do not enter information initially.. if they decide they want a name/email/password to post with.. how to change that, when they start with a blank user file? hrm..