RyanK's dashboard

RyanK replied on September 18, 2008 20:05 to the idea "Assigning different tags to the same application, collecting the info from different computers" in RescueTime:

I just sent off a message to support suggesting this idea! I would think its as easy as adding a default 'tag' to the preferences of the client, then all applications would get that tag.

I'm not sure if their data model can support that at the moment, as tags may be applied to a particular user for each app, rather then each use of that app for the user.

That's probably confusing to people, but I'm hoping there's a way that this can be setup!

RyanK started following the idea "Assigning different tags to the same application, collecting the info from different computers" in RescueTime.

RyanK started following the idea "What about supporting Linux?" in RescueTime.

A comment on the problem "Track bot hits API Limit for Direct Messages" in Twitter:

Nope, my reply above yours sums it up. Got an email Monday saying it was a bug in the whitelisting code and it would be going live Monday. Tuesday evening I sent another report saying I'm still seeing it blocked. Wednesday around noon pacific time, I got a reply saying that the fix has not yet gone live, but it should go in that same day.

About an hour ago, I sent another message reporting that it still being blocked. I have no other information as to what the holdup may be (perhaps a large change is being made which prevents smaller changes from going in... perhaps their deployment is complicated... i really don't know)

As soon as I hear anything, I'll send a tweet from @TweetTrak and keep this page updated.

I'm just hoping this gets resolved soon! – RyanK, on September 18, 2008 19:44

RyanK replied on September 18, 2008 18:49 to the problem "Track bot hits API Limit for Direct Messages" in Twitter:

Sadly, I was told that a problem was identified in the whitelisting code, and it was expected to be fixed on Monday. Apparently, we are just waiting for the code to be moved to production.

Wednesday, I was told that the change has not yet made it to the production servers, but it should be moved there yesterday.

Yet, today (Thursday), I am still hitting these limits. Over two weeks since I made the initial request, and this is is 13 days old now here.

I'm really disappointed, and feel like I've been stringing along my users by promising services that are unavailable more often then not... And for something like tracking, if it doesn't work 100%, you can't really rely on it, and then it becomes pointless.

I'm not blaming Crystal or Alex... I just want this issue to be transparent so that people know what's going on and why they are receiving notices intermittently.

RyanK replied on September 13, 2008 16:59 to the problem "Track bot hits API Limit for Direct Messages" in Twitter:

Just a quick update... 21 hours ago the second whitelist request with the server IP address was approved... haven't been able to send any DMs for the last 13 hours.

Supposedly, within the next 3 hours this new request should take effect, lifting all limits. I'm going to be out for much of the day, but will check how things are going later.

A comment on the question "when will "tracking" be back?" in Twitter:

yes.. you can.. however, most RSS readers only update once an hour.. TweetTrak, being designed for tracking, checks as often as once a minute...

There's of course many ways to use feeds and APIs... the search functionality itself has some shortcomings.. but we live with what we are given. – RyanK, on September 13, 2008 16:56

A comment on the question "when will "tracking" be back?" in Twitter:

Have a little bit of patience with TweetTrak... I've been working with Twitter for about a week to get whitelisted so that all direct messages get sent.

Currently, if it has hit the limit.. it won't be able to contact you. So, it will add or remove things you want to track, but won't be able to give you a confirmation.

There's a couple other annoyances that will be fixed soon.. so please have patience!

http://getsatisfaction.com/twitter/to... is the page with the whitelisting saga. – RyanK, on September 13, 2008 00:43

RyanK replied on September 11, 2008 17:45 to the problem "Track bot hits API Limit for Direct Messages" in Twitter:

Still not seeing any change in direct messages going through... it works for a few hours... is down for 2-8 hours... then works again for a little bit.

Is there any update on this yet?

A comment on the problem "Track bot hits API Limit for Direct Messages" in Twitter:

Just a quick update... worked for about 3-4 hours today, and has been blocking DMs for the last 32 minutes.. so whitelisting seems to have still not taken effect. – RyanK, on September 10, 2008 23:16

A comment on the problem "Track bot hits API Limit for Direct Messages" in Twitter:

worked fine for a few more hours but just hit the limit again. The email I received said that the limits no longer applied, so I presume that it somehow isn't in place yet. HALP! =) – RyanK, on September 10, 2008 03:26

A comment on the problem "Track bot hits API Limit for Direct Messages" in Twitter:

that delay is most likely from search.twitter.com being a little bit behind. I've seen it as far as 3-4 hour behind.. and I'm sure its been worse. Its normally fairly up to the moment.

Also, TweetTrak is gentle on twitter's services.. when it doesn't see a term for a while it checks less often (still at least once every 5 minutes with the first day... scales out to 6 hours after a few weeks... those values are subject to change) – RyanK, on September 10, 2008 03:25

RyanK replied on September 10, 2008 00:36 to the problem "Track bot hits API Limit for Direct Messages" in Twitter:

OK, its been working in spurts of about 4 hours, then stops for about 2.

A little over 24 hours ago I received a notice that the lifted whitelisting should take effect within 24 hours, but DMs are no longer going through.

On the plus side, I used to get a robot page when I would try to send a DM, however now I get a nice error message telling me I've sent too many DMs:



Am I being too anxious and just need some more patience? or has something gone wrong? Are there different whitelists for DMs and for other API calls? Hopefully this takes care of itself, but if someone needs to do something, then hopefully this helps notify someone.

Sorry if i'm being annoying.. lol

Ryan

RyanK set one of RyanK's replies as an official response to "how do i stop tracking keywords?" in TweetTrak

RyanK replied on September 09, 2008 23:26 to the question "how do i stop tracking keywords?" in TweetTrak:

Yes, there is an untrack command. If you were tracking @TweetTrak, then "untrack @TweetTrak" should remove it, and send you a message letting you know that its gone.

You can also send "untrackall" to quickly remove all your tracked terms, or "tracks" to get a list of what you're tracking.

And yes, the website is just a simple informational page atm, eventually you will be able to see what you're tracking and how active those terms are. That work will start once my stolen laptop gets replace in about a week or so.

Also, in the short term some Direct Messages are not going through as it appears as if TweetTrak is not yet fully whitelisted. It should be fine very soon though, but if you're not getting responses, that's why.

RyanK replied on September 08, 2008 23:43 to the problem "Track bot hits API Limit for Direct Messages" in Twitter:

Appears as if its been running now for about 3+ hours... I didn't get any confirmation back that I'm whitelisted now, but I'm going to assume all is well. If it appears as if I'm hitting a limit again, I'll be back! =)

Thanks all for your help... Twitter users everywhere (that have heard of TweetTrak that is) are rejoicing!

RyanK marked one of crystal's replies in Twitter as useful. crystal replied to the problem "Track bot hits API Limit for Direct Messages".

RyanK reported a problem in Twitter on September 05, 2008 22:50:

Track bot hits API Limit for Direct Messages

I am running a bot that provides tracking functionality by using the Search API and sending direct messages. Now that there are about 100 people using it and getting messages, Ive noticed over the last few days that several messages haven't been getting sent. I understand the need for limiting casual users DMs to curb spammers, but my bot is legitamate.

I reported this issue on the development list (it exposes the contents of a random DM when using the json interface) and have filed a request through help.twitter.com (issue 320434) to have the limit removed or drastically increased. The rate_limit_status API call doesn't indicate DM limit status.

Any help is appreciated!

RyanK replied on September 04, 2008 18:50 to the idea "Send Tracks to SMS or another Twitter account" in TweetTrak:

I've thought about adding other notification methods... email or IM are easy... SMS is a bit more difficult as I'd need to find a free SMS gateway. It may not be necessary as most cell phone providers (in the US at least) provide an email gateway.

I'm going to be adding an ignore feature (when I find time.. never enough time! =/) so that you won't get notified. I was thinking it would be more useful for ignoring updates from people you have device notifications on.

Would that be useful? I'm not sure about DM'ing a different screen name (it would have to also follow TweetTrak, and potential abuse). If you had the ignore feature and the email/IM/DM option.. would that be enough?

RyanK replied on September 03, 2008 15:52 to the discussion "Excited for TweetTrack and so should you!" in TweetTrak:

Thanks! I'm just glad to see it get used and meet needs of people!

Always glad to see people are happy with what I did! More things planned as well! =)