1 post tagged “planning”
The following is feedback I wrote up for Crush3r, my favorite event planning site ever (as I've said elsewhere). I decided to post it here instead of in their feedback form because I can format it for easier reading and also for the potential of the discussion that could ensue.
I would love to see more Twitter integration with your site via their direct messaging feature. A couple of use cases and ideas:
- Twitter direct messages should be a first class notification option on the settings page assuming a user has provided you with their twitter username and followed @crush3r. I seem to remember Dopplr's setup being a pretty good model. Most obvious example is getting direct messages when people reply to my invites.
- Twitter direct messages could also be used as a means of communication when you're away from the computer and need to know details of an upcoming party or interact with one.
Crush3r Twitter commands
The following are a list of possible commands sent via direct message to the crush3r account on Twitter (i.e. "d crush3r COMMAND ....."). In grand Unix style, things listed in caps are variables with alternating choices in parentheses and optional elements in square brackets. Everything should be evaluated case-insensitively.
- (off|on) - Silences or unsilences all Twitter notifications from Crush3r. That is, "off" should disable Twitter as a notifier for the user but keep the individual settings so that they can be restored.
- [un]mute [KEY] - Enables/disables notifications for the most proximate event or an event specified by KEY (described below).
- list - Returns a list of titles for the next three events that you've created or been invited to. Would probably need to send back three separate direct messages.
- info [KEY] - Returns title, time and location of an event
- link [KEY] - Returns a URL to an event invitation page
- creator [KEY] - Sends back info about the organizer of an event
- map [KEY] - Request for a link to the map for an event
- guests [KEY] - Sends a summary of the RSVPs for an event
- rsvp KEY RESPONSE - Enters your RSVP for an event specified by KEY (which is required here). RESPONSE could be, I don't know, yes, no, will try, be early, doubtful. You could match up the responses to the slider on the site but I'd hate to have to make people type those things as it would be prone to error. Maybe you could also accept values from -5 to 5 indicating least likely to most likely. d crush3r rsvp +5 would be simple and pretty awesome.
- comment KEY COMMENT - Adds the message COMMENT to the comment section of an event invitation specified by key (which is required here).
The KEY command attribute
The KEY command attribute mentioned above is an optional attribute that lets you interact with a specific event. Except in the cases where it is required due to the variability of the data which follows it, it can be omitted in which case the most proximate (i.e. soonest) event is assumed.
The KEY attribute could be one of a few things all of which can be and should be supported at the same time:
- The page ID that is contained in the URL (e.g. bsjwu2ksj in http://crush3r.com/page/bsjwu2ksj) (The most obvious yet least attractive option)
- The numeric index (1-based) representing the position of the event returned by the "list" command. So both "d crush3r info" and "d crush3r info 1" would send back info about the 1st event (i.e. the most proximate in chronology). "d crush3r info 2", the second, etc.
- A string which is contained (case insensitive as with everything) in one of the event names returned by the "list" command. The first invite (starting from first up to last) which matches is used so the string doesn't even have to be unique. If you have coming up (in order) "Jay's house party", "Jen's birthday" and "Book Reading at Kevin's house", you could use:
- d crush3r rsvp kevin +5
- d crush3r info birthday
- d crush3r guests house
The latter would match "Jay's house party" because it's the first event that contains the string "house".
Again, my greatest thanks to you all at the Crush3r team for all your hard work. I look forward to the potential of Crush3r and twitter together and would be happy to talk with you all more if you like or if you need help with the Twitter API.
