@mmn @heluecht@pirati.ca GNU Social and Friendica have APIs, "compatible" with Twitter REST API v.1.0, which is NOT current Twitter API for a couple of years. Moreover, Twitter removed documentation on that API from its site. So now we don't even have a golden source of "correct" implementation. And even more, StatusNet explicitly published it's extentions to that legacy API. I mean, there is no good reason to change existing GNU Social API for compatibility reasons.
As we mentioned already in other discussions, it would be much more beneficial for the "fediverse" to improve (read: change) API in another way: to have globally unique message and user identifiers etc. That way is mostly away from compatibility with Twitter API, which was designed for a centralized system.
@mariotaku
?!