Feb 2014 changes to make to Kinglet

• modify any necessary JSON returned by API

Features to Add

Delete Message

• ability to delete a message sent?
  • unsure about this. will not implement for now.

Approved List

• User A requests to be added to a user B's accepted or approved list in order for User A to message User B. It would then be up to User B to make the same request of User A. One action does not automatically enable the other.
• actions by User B when receiving the request:
  • accept
  • reject
• both response types can be changed later
• a user can send a request to be added to approve list only one time.
• the response is returned to the requesting user
• when User A messages User B, if A is not on B's accepted list, return error message with info:
  • telling A to send a request to B to be added to B's approved list
  • or remind A that A already requested to be added to B's approved list, and B rejected the request.

If User A wants to message himself, then no need to make such a request to himself.

Things to do to support the approved list feature:

• create database table
  • id - auto increment
    **
• create API commands.
  • will this be added to the "users" section of the API, or should a new section be created called "lists?"
  • request - to be added to a recipient's approved list - GET - /lists/request/mrx - send request to user mrx.
  • reject - the request - GET - /lists/reject/jr - reject request from user jr.
  • approve - the request - GET - /lists/approve/jr - approve the request from user jr.
  • show - the list of requests of requests received so that a user can change the reject/approve function - GET - /lists/requests - requests received

Should I create an action that allows a users to view all requests made? Not right now. Unsure if this needed. A user could simply try to make a new request, and the system will return the appropriate response.

#kinglet - #kinglettodo