The only reason I can think of is if he (or a library used by him) utilises
just one string to hold the base URL.
Some compiled libraries might also come with URLs hardcoded.
Not a major bother, but possibly inconvenient as he notes.
On Fri, Nov 27, 2009 at 12:30 AM, Rich wrote:
> I can't unde
I can't understand why it would be difficult to develop your app using
api.twitter.com/1 instead of twitter.com, it's just a minor url change
and will make your app as future proof as you can get until v1 is
deprecated.
Sorry if I'm missing some big reason why.
On Nov 26, 3:45 pm, Raffi Krikorian