>>… display status (show,hide,starred,buried,etc.)
> Not quite sure what I would do with this. Perhaps be able to delete comments?
yeah, or for moderation (hide without deleting), or for featuring/downvoting comments.
>>If you wanted to “version” comments …
> Not sure I’m understanding why I would need a separate field just for edits?
Not exactly what I meant: just a “version number.”
For example, user *X* leaves a comment, then later edits it. The “edited” comment would actually be an entirely new record in the DB, with the same id (I was thinking a good Primary Key would be userID+publishTime), but a different version number. That way, you’d preserve the original comment in case you ever needed it, and it would still be easy to retrieve only the latest version:
Hey @traq. I’m on my iPhone writing this as I’m not home at the moment.
Basically I was taking my consumer and access keys/secrets, inputting them into the twitteroauth.php file in the Vendor folder. I might have placed into another file as well which was causing it to fail. The only thing you need to do to get it working is to place your Consumer key and secret into opauth-config (or whatever the filename is) inside the Example folder. It should then validate.