freunde.ma-nic.de
!developers In the last release, the old API became worse again. The api/friendica/notification is not existing anymore despite being in the documentation. The API /conversation/show have in_reply_to_I'd which make not sense. In the API /statuses/friends_timeline the news have three user objects which are all the same, even for reposts. For posts with embedded content the images are not in the attachments as was the case in earlier versions.
All this leads me to the conclusion, that these APIs are not in the developers focus, are not tested afterbchanges and degrade over time.
Are App developers required to use the Mastodon API?
Cheers, Marco
Further update: Most issues should be resolved now, please have a look here: github.com/friendica/friendica…
Concerning the bookmark functionality, please have a look at the endpoints of the Mastodon API. There we have the endpoints POST /api/v1/statuses/:id/bookmark and POST /api/v1/statuses/:id/unbookmark. The API endpoints are now interchangeable concerning the item id.
Please have in mind that you have to remove and re-add the account since the item id has changed.
In the last version we transformed the coding for the Twitter API and rebuilt them in the new class structure. I tested each endpoint as far as it was possible, but of course problems can occur.
Please report any issues.
Concerning the future: Currently the Mastodon- and the Twitter-API are using different id values for the items. This will eventually change. Then it will make sense to use all API flavours in a wild mix. It is not planned to deprecate the Twitter API. The opposite is true. It should be now possible to register via OAuth and to use any part of the API.