correct me if I'm wrong but i don't think there is one single place developers can create APIs for. if anything, developers will be picking and choosing which "instance" they want to write for if willing. this is like having thousands of "twitter" clones all acting as their own environment. kind of like how we have thousands of wordpress sites out there.
That doesn't seem right. The API for an instance is going to be the Mastodon API, which will be the same for all instances. Each instance isn't going to be creating their own API - really, all Mastodon is is an API spec.
yes what i was saying is, i doubt you will be able to hit one mastodon API and get the tweets across all the federated instances. you will only retrieve the data of that single instance you are hitting. if that instance only has 1 user, then that will be all you are getting.
but please correct me if im wrong. i havent really dived too much into it.
essentially the api will return all toots from whatever timeline you're asking it for, e.g. if your instance is federated with 5 servers, you'll get your timeline from people tooting from these servers, I think the "public" timeline (can't remember the exact name) is all the toots from all federated instances you federate with. So it would be the same data as the browser has.
I think the biggest problem for the app developers is an interface that lists a lot of instances that you can search for which you identify most with (I think some use a centralised list someone has created somewhere). But that's a bad UX to jump into as a new user.
