jon|k's dashboard

ScottKoegler replied on July 14, 2008 19:41 to the idea "fireeagle integration" in Brightkite:

Pls count me in as well

A comment on the problem "When is pagination coming back?" in Twitter:

Yes, I can relate to that. I hope that with the improvements to the API limits, I can just stick to Twitbin (my preferred third party Twitter app) and won't have to check Summize for any @replies that I may have missed. 8-) – mdy, on July 10, 2008 05:36

A comment on the problem "When is pagination coming back?" in Twitter:

I have an account at ping.fm and use it fairly often, but it does me no good when I can't be sure I'll be able to see any replies or conversation around my tweets. – Alex Conner, on July 10, 2008 05:11

mdy replied on July 10, 2008 02:02 to the problem "When is pagination coming back?" in Twitter:

Oh, and I forgot to mention also that I've lately been using http://ping.fm to post tweets. Perhaps this might be interesting enough to get you out of your 'read-only' state, Alex. 8-)

It's a service that takes your update and posts it into multiple services in one go. Twitter and identi.ca are both supported.

The invite code for sign-ups routinely changes, but it is currently "dreamofping" in case you're interested.

mdy replied on July 10, 2008 01:32 to the problem "When is pagination coming back?" in Twitter:

Hi quepol and Alex.

FWIW, the API limit had been raised yesterday from 20 to 40, then later to 70.

As of now, the API limit is at 100. A thread in the Twitter Dev Google Group says the API limit of 100 is in test mode, which is why no official announcements have been made yet. But they're hoping to not go below 70 after the test.

Looks like their last two infra upgrades have given them enough capacity to do this. 8-)

Alex Conner replied on July 09, 2008 21:44 to the problem "When is pagination coming back?" in Twitter:

I've actually gone to being read only with Twitter by using a desktop RSS reader and subscribing to all of my friends feeds (that was NOT an easy task).

I'm currently hanging out at identi.ca until Twitter can get their stuffs together, or until identi.ca gains RSS support.

Twitter, you're racing someone with an advantage!

quepol replied on July 09, 2008 21:33 to the problem "When is pagination coming back?" in Twitter:

Alex - I, too, am still missing the Older button on my main account after weeks (months?) of it being grayed out. The only thing keeping Twitter alive for me is Socialthing. They must get updates via XMPP because you can get older updates. I have abandoned everything else (including the Twitter web site) because the API is useless with a 20 req/hr limit.

A comment on the problem "The "older" button is gone?" in Twitter:

I could go to page 2 yesterday but not past there and now I can't even do that. This is so frustrating. It's starting to make me mad. ARGH! – Earthchild, on July 06, 2008 05:02

Spam replied on July 05, 2008 20:10 to the problem "The "older" button is gone?" in Twitter:

Here's another thread with an even newer official response...

chuckstar76 replied on July 04, 2008 15:03 to the idea "fireeagle integration" in Brightkite:

Yes please to two-way updates between BrightKite and Fireeagle

Alex Conner replied on July 04, 2008 13:29 to the problem "When is pagination coming back?" in Twitter:

I have been without pagination for a month now, and it is making twitter completely useless for me. I am missing my friends tweets, so I may as well not even be using the system at all. Using summize, etc. is not an option because a number of my friends have their tweets protected, so I end up opening every one of their profiles to see if they have tweeted, then I have to sit and pound the web interface to keep updated. Seriously, taking away pagination is NOT helping DB load, at least not in my case.

The Twitter team needs to get some things accomplished, I have seen very little out of this company on the way of anything. The only thing you guys have done is throw more DB servers at the problem and turn off features. I can't even use a 3rd party client like Twhirl because the API is so jacked up.

jeppedy replied on June 27, 2008 16:00 to the idea "fireeagle integration" in Brightkite:

@brady Now that's what I was hoping for. "@FE Man, it's pouring here today! So much for my picnic" would mean a little more now. I say run with it!

A comment on the idea "fireeagle integration" in Brightkite:

Until FE addresses the push service problem we may allow people to check in at their FE location. For example you could text @FE to Brightkite and we would then use your FE location to check you in. Additionally we have discussed ways on the web/iPhone where it would be less manual. – Brady, on June 27, 2008 15:50

A comment on the idea "fireeagle integration" in Brightkite:

@jeppedy Exactly what I was going to suggest, for starters if you showed where fireeagle thought i was at the check in page that would be a huge value add. and that should be pretty trivial. – jebu, on June 27, 2008 15:30

A comment on the problem "The "older" button is gone?" in Twitter:

Please make the Older button work! – Murph, on June 26, 2008 11:26

Murph marked one of jon|k's replies in Twitter as useful. jon|k replied to the problem "The "older" button is gone?".

A comment on the idea "fireeagle integration" in Brightkite:

Brady, think more creatively. The only feature that needs the constant polling is the "Near Me" feature. Even if this is a heavily-used, gotta-have-it feature (is it?), you could still pull the current location upon status change rqst/place checkin rqst. This would meet the needs of most folks commenting here and get you to market in a day or two. Then, once you solve the scale issue, roll out the new solution. It's a couple of calls and a preference item for "use FE's location when changing status". Easy-Peasy... – jeppedy, on June 25, 2008 18:34

Brady replied on June 25, 2008 17:37 to the idea "fireeagle integration" in Brightkite:

We don't currently support pulling from FE because there is no scalable way to consume FE information...we'd have to poll the FE status for every FE user every few minutes...that's fine for a few people, but not for thousands of users.

We've working with the FE team to address this (probably through an XMPP-based push service).

Ken Kennedy replied on June 18, 2008 16:21 to the idea "fireeagle integration" in Brightkite:

+1 from me. This would be really, really cool.

jon|k started following the idea "fireeagle integration" in Brightkite.