When I lookup a contact in Sandy by her name via Twitter, all I get as a response is "direct from s: #[number] First result: [Name]". I don't get the rest of the contacts details. The details show up fine in the web interface, but not via Twitter. What gives?

Everything was working a treat this morning. I'd email Sandy and she sent me reminders to my email and (via twitter) to my mobile. However, Twitter is not sending Sandy's reminder's to my phone anymore although the emails are still getting through. Are Twitter and Sandy fighting? What's up?

Direct twitter response sent updates for several months all at once. See below:

direct from s: #21 Reminder: Run a release (Tue, 3/25 1:00pm) @twitter @weekdays @workrelated
direct from s: #22 Reminder: Run a release (Wed, 3/26 1:00pm) @twitter @weekdays @workrelated
direct from s: #23 Reminder: Run a release (Thu, 3/27 1:00pm) @twitter @weekdays @workrelated
direct from s: #24 Reminder: Run a release (Fri, 3/28 1:00pm) @twitter @weekdays @workrelated
direct from s: #25 Reminder: Run a release (Mon, 3/31 1:00pm) @twitter @weekdays @workrelated
direct from s: #26 Reminder: Run a release (Tue, 4/1 1:00pm) @twitter @weekdays @workrelated
direct from s: #27 Reminder: Run a release (Wed, 4/2 1:00pm) @twitter @weekdays @workrelated
direct from s: #28 Reminder: Run a release (Thu, 4/3 1:00pm) @twitter @weekdays @workrelated
direct from s: #29 Reminder: Run a release (Fri, 4/4 1:00pm) @twitter @weekdays @workrelated
direct from s: #30 Reminder: Run a release (Mon, 4/7 1:00pm) @twitter @weekdays @workrelated
direct from s: #31 Reminder: Run a release (Tue, 4/8 1:00pm) @twitter @weekdays @workrelated
direct from s: #32 Reminder: Run a release (Wed, 4/9 1:00pm) @twitter @weekdays @workrelated
direct from s: #33 Reminder: Run a release (Thu, 4/10 1:00pm) @twitter @weekdays @workrelated
direct from s: #34 Reminder: Run a release (Fri, 4/11 1:00pm) @twitter @weekdays @workrelated
direct from s: #35 Reminder: Run a release (Mon, 4/14 1:00pm) @twitter @weekdays @workrelated
direct from s: #36 Reminder: Run a release (Tue, 4/15 1:00pm) @twitter @weekdays @workrelated
direct from s: #37 Reminder: Run a release (Wed, 4/16 1:00pm) @twitter @weekdays @workrelated
direct from s: #38 Reminder: Run a release (Thu, 4/17 1:00pm) @twitter @weekdays @workrelated
direct from s: #39 Reminder: Run a release (Fri, 4/18 1:00pm) @twitter @weekdays @workrelated
direct from s: #40 Reminder: Run a release (Mon, 4/21 1:00pm) @twitter @weekdays @workrelated
direct from s: #41 Reminder: Run a release (Tue, 4/22 1:00pm) @twitter @weekdays @workrelated
direct from s: #42 Reminder: Run a release (Wed, 4/23 1:00pm) @twitter @weekdays @workrelated
direct from s: #43 Reminder: Run a release (Thu, 4/24 1:00pm) @twitter @weekdays @workrelated
direct from s: #44 Reminder: Run a release (Fri, 4/25 1:00pm) @twitter @weekdays @workrelated
direct from s: #45 Reminder: Run a release (Mon, 4/28 1:00pm) @twitter @weekdays @workrelated
direct from s: #46 Reminder: Run a release (Tue, 4/29 1:00pm) @twitter @weekdays @workrelated
direct from s: #47 Reminder: Run a release (Wed, 4/30 1:00pm) @twitter @weekdays @workrelated
direct from s: #48 Reminder: Run a release (Thu, 5/1 1:00pm) @twitter @weekdays @workrelated
direct from s: #49 Reminder: Run a release (Fri, 5/2 1:00pm) @twitter @weekdays @workrelated
direct from s: #50 Reminder: Run a release (Mon, 5/5 1:00pm) @twitter @weekdays @workrelated
direct from s: #51 Reminder: Run a release (Tue, 5/6 1:00pm) @twitter @weekdays @workrelated
direct from s: #52 Reminder: Run a release (Wed, 5/7 1:00pm) @twitter @weekdays @workrelated
direct from s: #53 Reminder: Run a release (Thu, 5/8 1:00pm) @twitter @weekdays @workrelated
direct from s: #54 Reminder: Run a release (Fri, 5/9 1:00pm) @twitter @weekdays @workrelated
direct from s: #55 Reminder: Run a release (Mon, 5/12 1:00pm) @twitter @weekdays @workrelated
direct from s: #56 Reminder: Run a release (Tue, 5/13 1:00pm) @twitter @weekdays @workrelated
direct from s: #57 Reminder: Run a release (Wed, 5/14 1:00pm) @twitter @weekdays @workrelated
direct from s: #58 Reminder: Run a release (Thu, 5/15 1:00pm) @twitter @weekdays @workrelated
direct from s: #59 Reminder: Run a release (Fri, 5/16 1:00pm) @twitter @weekdays @workrelated
direct from s: #60 Reminder: Run a release (Mon, 5/19 1:00pm) @twitter @weekdays @workrelated
direct from s: #61 Reminder: Run a release (Tue, 5/20 1:00pm) @twitter @weekdays @workrelated
direct from s: #62 Reminder: Run a release (Wed, 5/21 1:00pm) @twitter @weekdays @workrelated
direct from s: #63 Reminder: Run a release (Thu, 5/22 1:00pm) @twitter @weekdays @workrelated
direct from s: #64 Reminder: Run a release (Fri, 5/23 1:00pm) @twitter @weekdays @workrelated
direct from s: #65 Reminder: Run a release (Mon, 5/26 1:00pm) @twitter @weekdays @workrelated
direct from s: #66 Reminder: Run a release (Tue, 5/27 1:00pm) @twitter @weekdays @workrelated
direct from s: #67 Reminder: Run a release (Wed, 5/28 1:00pm) @twitter @weekdays @workrelated
direct from s: #68 Reminder: Run a release (Thu, 5/29 1:00pm) @twitter @weekdays @workrelated
direct from s: #69 Reminder: Run a release (Fri, 5/30 1:00pm) @twitter @weekdays @workrelated
direct from s: #70 Reminder: Run a release (Mon, 6/2 1:00pm) @twitter @weekdays @workrelated
direct from s: #71 Reminder: Run a release (Tue, 6/3 1:00pm) @twitter @weekdays @workrelated
direct from s: #72 Reminder: Run a release (Wed, 6/4 1:00pm) @twitter @weekdays @workrelated
direct from s: #73 Reminder: Run a release (Thu, 6/5 1:00pm) @twitter @weekdays @workrelated
direct from s: #74 Reminder: Run a release (Fri, 6/6 1:00pm) @twitter @weekdays @workrelated
direct from s: #75 Reminder: Run a release (Mon, 6/9 1:00pm) @twitter @weekdays @workrelated
direct from s: #76 Reminder: Run a release (Tue, 6/10 1:00pm) @twitter @weekdays @workrelated
direct from s: #77 Reminder: Run a release (Wed, 6/11 1:00pm) @twitter @weekdays @workrelated
direct from s: #78 Reminder: Run a release (Thu, 6/12 1:00pm) @twitter @weekdays @workrelated
direct from s: #79 Reminder: Run a release (Fri, 6/13 1:00pm) @twitter @weekdays @workrelated
direct from s: #80 Reminder: Run a release (Mon, 6/16 1:00pm) @twitter @weekdays @workrelated
direct from s: #81 Reminder: Run a release (Tue, 6/17 1:00pm) @twitter @weekdays @workrelated
direct from s: #82 Reminder: Run a release (Wed, 6/18 1:00pm) @twitter @weekdays @workrelated
direct from s: #83 Reminder: Run a release (Thu, 6/19 1:00pm) @twitter @weekdays @workrelated
direct from s: #84 Reminder: Run a release (Fri, 6/20 1:00pm) @twitter @weekdays @workrelated
direct from s: #85 Reminder: Run a release (Mon, 6/23 1:00pm) @twitter @weekdays @workrelated
direct from s: #86 Reminder: Run a release (Tue, 6/24 1:00pm) @twitter @weekdays @workrelated
direct from s: #87 Reminder: Run a release (Wed, 6/25 1:00pm) @twitter @weekdays @workrelated
direct from s: #88 Reminder: Run a release (Thu, 6/26 1:00pm) @twitter @weekdays @workrelated
direct from s: #89 Reminder: Run a release (Fri, 6/27 1:00pm) @twitter @weekdays @workrelated
direct from s: #90 Reminder: Run a release (Mon, 6/30 1:00pm) @twitter @weekdays @workrelated
direct from s: #91 Reminder: Run a release (Tue, 7/1 1:00pm) @twitter @weekdays @workrelated
direct from s: #92 Reminder: Run a release (Wed, 7/2 1:00pm) @twitter @weekdays @workrelated
direct from s: #93 Reminder: Run a release (Thu, 7/3 1:00pm) @twitter @weekdays @workrelated
direct from s: #94 Reminder: Run a release (Fri, 7/4 1:00pm) @twitter @weekdays @workrelated
direct from s: #95 Reminder: Run a release (Mon, 7/7 1:00pm) @twitter @weekdays @workrelated
direct from s: #96 Reminder: Run a release (Tue, 7/8 1:00pm) @twitter @weekdays @workrelated
direct from s: #97 Reminder: Run a release (Wed, 7/9 1:00pm) @twitter @weekdays @workrelated
Sent at 12:07 PM on Monday

Sandy says I am not following her on Twitter, but I am:

> You're not "following" me on Twitter yet. Please go to http://twitter.com/s and click "follow," then try again.

Of note is that I changed my Twitter username. However, I double-checked that the new username I entered into Sandy was correct, and that I was following @s from my new account.

I have a contact in my list called "Chincoteague Island Vacations." I sent the following instruction via email:
l chincoteague contacts
and Sandy returned an email with the contact information I wanted. In other words, it worked perfectly.

Then, just to make sure I could get the same information via mobile if necessary, I used Twitter to DM Sandy with the exact same text. It didn't work. I got the standard "does not compute" response ("Hello! To remember/remind: 'd s r take a break in 15 min'; To update: 'd s u 1 @done'; For more: iwantsandy.com/examples").

Shouldn't the responses to lookups (and to everything) be the same whether one uses email or Twitter?

Until yesterday (5/7/08), Sandy understood pretty much everything I sent her using Twitter. Now, she seems extra picky and I can't get her to understand some of my requests. Here are a couple examples (I put curly braces around my messages to set them apart - they weren't used at the time):

1. I sent {d s r help Dad L with his brochure @todo @all} and Sandy replied with her standard "don't understand" response (Hi! To remember/remind: "d s r take a break in 15 min"; To update: "d s u 1 @done"; For more: iwantsandy.com/examples). I tried {d s r "help Dad L with his brochure" @todo @all} and she responded the same.

2. I sent {d s r write letter to ruby about her sunshine and exuberance @todo @all @computer} and Sandy would simply NOT GET IT, even if I surrounded the main part in quotes like I did above. I played around with this for several tries, and oddly Sandy would understand {d s r write letter to ruby about her pens and pencils @todo @all @computer}! That is exactly the same except for the two content words. It makes no sense.

In both cases, I had no idea what the problem was and gave up trying to ask Sandy to remind me about it. It's very frustrating.

I use Sandy with Twitter, since I'm abroad and don't have mobile support. However, regardless whether I tweet Sandy via mobile or Twitter webpage, I don't receive the list items, just list name and tag. Everything else works fine. Although I get email confirmation of list items, I'd love to get the list items to Twitter.

Additionally, yesterday it took 10 hours for Sandy to respond to my tweets (got bunch of confirmations overnight) Was Sandy just busy with some Valentine's rendezvous or do others have this problem?

I've tried to get Twitter and Sandy to play nice together, but it's just not happening. I went through the guide to making this happen, almost no success.

I can get Sandy to follow me and me to follow her. I got the confirmation Tweet very quickly. I get the test Tweets almost instantly. But that is where things end.

I've tried copy and paste-ing the examples. All I'm seeing is that my message was sent when I use Pidgin from my GTalk account. But when I send the same message from the Twitter website I am told that the user doesn't exist.

Um, what? I don't think I can follow someone who doesn't exist.

There are no replies and no direct messages from Sandy on the Twitter site.

I really don't know what else to tell you so that I can have this working right, but I'll be happy to answer any questions that could help lead to the solution.

Hi,
Really thought I had found a site that would do everything I wanted but find that when I ask her for e.g. my ToDo list via Twitter I just get my first item - how unhelpful is that :-(

Personally I would like each list item to come through as a different Twitter, that way I can easily reply and knock them off the list as I do them and still have a running list of those outstanding. I realise there's a 160 character limit but doubt anyone will have a list item of longer than that!!

Why can't I get Sandy to send me my Twitter confirmation code?

Hi,

After changing my Sandy's email address, Twitter direct message requests seem broken.. )-:

(she doesn't even respond)

I tried turning twitter off and on again... no luck.

S

When trying to send a new reminder via Twitter, for example "d s r Remind to whatever today @todo @high", when adding a "@high" tag, the message won't get picked up by Sandy.

I was using @high, @med, @low tags to set priority—the @low and @med went through twitter just fine, but @high just throws me back a message from Sandy that I'm guessing is the Sandy-version of an error—the "Hello! To remember/remind: ...." response.

I've tried moving the @high before @todo, but that didn't change anything. If I drop @high, it works.

Also tried sending it through without the @high, then doing a "d s u #4 @high", which didn't work either. Adding some other random tag (say, @cheese) does work.

I don't see in the documentation that @high is a reserved tag—help? Thanks.

When signing up for twitter/sandy integration, Sandy sent a confirmation code via twitter. When I pasted the code into Sandy's configuration screen, Sandy told me that the code wasn't valid -- but it was! it simply had a few trailing spaces. I think that the string should be trimmed before being checked to get rid of this problem.

I've set the "Would you like me to send you reminder tweets?" to off in my Settings but it has no effect. It might have something to do that I've sent the reminders through Direct Message in Twitter and not by email (which I never use anyways).

This is actually only my secondary problem. My original intent was to turn of the Twitter confirmations (not actual reminders) but there's no such an option to be found. Because I deliver my tweets to my mobile, these confirmations (for me at least) are just spam.

I created a reminder via twitter with a time and date, but wanted the reminder interval to be the day before instead of the usual 15 minutes.

I went to the website, selected the reminder and chose edit. (At this point the reminder looks fine - Tuesday 8th January at 09:45 GMT).

I changed the reminder interval and saved and the task ended up at 5:45pm PST (which makes no sense).

I tried to change the date back, but the reminder got moved to 1st August 2008 this time with a EST timezone.

My settings are Europe - London and DD/MM/YYYY (changing to US format dates helps a little, but I really don't want to change to a US timezone).

Lately I have noticed that "lookup" queries sent via email (or twitter) returns the query message (e.g. "l nomatches" returns "#1 <right> l nomatches" as its only result). This appears to only happen for searches which return no results -- those which return results seem to work fine.</right>

I have tried to use lookup via twitter. I've got other commands working, but whenever I use lookup, I get back a message about how to use the service, rather than the results o the lookup.

I'm not sure how common my setup is, but I'm using Google Talk on my Blackberry 8700r to Twitter to Sandy. The problem is that despite having SMS reminders and confirmations turned off, I'm getting SMS confirmations in response to Tweets.

As well, when I do lookups via the same setup, they also are coming via SMS (and sometimes email) rather than Twitter.

Anyone else seeing this?

Via Twitter, I sent Sandy a message along these lines:

d s r do so-and-so next Monday at 8a

Sandy replied:

I got do so-and-so (Mon., 1/21/2008 8:00am)

But that time is two hours ago. Shouldn't the word "next" have indicated to Sandy that the reminder is not for today, and certainly is not for a time in the past?

Sandy has emailed me my two daily reminders today, but the accompanying tweets never came through. I just sent a tweet to Twitter and it went through, so I was wondering if there was a problem with the API today.