App.net API Documentation is on the web at https://developers.app.net. Source for these docs is in the new-docs branch here. Please use the issue tracker and submit pull requests! Help us build the real-time social service where users and developers come first, not advertisers.
But Twitter has always had only one web interface with only one permanent URL. I'm guessing App.net won't live at alpha.app.net forever. And even if it does, parsing post IDs out of URLs is kind of painful. I'm wondering if we can come up with something better.
A few ideas, some of them solving more of these issues than others:
We could introduce a funny-character syntax, e.g. ^240352307617861632.
The API could parse the post ID out of URLs and include them in the link entities.
We could try to get people to use some sort of URI format, e.g. uri:appnet:post/240352307617861632.
You could settle on a permalink format for us to use very, very soon and officially communicate how to parse it.
I don't really know of a perfect solution here; I'd just like to start thinking about this, because it's a place where Twitter is kind of a pain and App.net could do better.
On Twitter, when we post a tweet that refers to a specific other tweet, we use its URL—for instance, https://twitter.com/architechies/status/240352307617861632.
But Twitter has always had only one web interface with only one permanent URL. I'm guessing App.net won't live at alpha.app.net forever. And even if it does, parsing post IDs out of URLs is kind of painful. I'm wondering if we can come up with something better.
A few ideas, some of them solving more of these issues than others:
I don't really know of a perfect solution here; I'd just like to start thinking about this, because it's a place where Twitter is kind of a pain and App.net could do better.