More reasons for Gatorpeeps
by Stii
Finally we can talk about Gatorpeeps officially! We’ve been rather quiet about it, primarily since we needed to finish a few things and stress test it before we punted it.
We had our fair share of “Blegh, another Twitter clone…” and we expected it. The thing is, we love twitter! Always have, always will.
So why did we clone it then? Simple. Some of the reasons Justin already covered over here, but I’d like to add that Afrigator was in need of something social networky. We needed to add a communication dimension and as everybody knows, there is no better way to do that other than Twitter. Yes, we could have leveraged off the Twitter API. That is true, but the Twitter API is not without it’s limitations.
Besides that, we also have a few other ideas, such as Twitter recently killed SMS functionality in Africa, and it left a huge gaping gap in that market.
We did not leverage off some Open Source app like Laconi.ca or Jaiku. We wanted to initially, but due to the fact that we want to seamlessly integrate Gatorpeeps with Afrigator and add a bunch of unique features, we thought it best to rather develop our own flavor into the mix. For those interested, it is backed up by the brilliant Kohana PHP framework :). Was it the best idea? The right thing to do? Time will tell.
Now the real work starts. Now we need to do all these promised features and integration… Fun times!

The biggest issue I have with the Twitter API is the aggressive rate limiting. We have now progressed to the point that we cannot do calls from Google App Engine or apparently even some of the more popular shared hosts.
However, speaking about the API, what might be quite handy is a Twitter “look-alike” API for Gatorpeeps similar to what Laconica did. Then we can start making our existing Twitter mashups work with Gatorpeeps without too much effort.
Hi Charl, it exists at http://afrigator.com/api/... I just have not got round to documenting it as there is a few minor things we haven’t implemented yet. :( That is, btw, how we do the Twhirl integration.
Sounds good – I need to ping you sometime when I’m back in South Africa then I can start scratching around or even setting up some community documentation. :)
Btw, awesome blog theme, and great use of semi-transparency!