This looks a bit optimistic or underestimating real life tradeoffs.
There can be an API, yes. But if you want to filter by positivity, you have to expect the company to actually implement that in the API. Otherwise, do you expect to get all billions of tweets over an API and then add positivity on top?
You can't have sustainability, performance and "open for everything" on one single API, there are tradeoffs and constraints involved. Even GraphQL needs certain fields to be filterable even before the API call returns, otherwise one can't just loop over all commits in GitHub universe without exhausting both consumer and provider systems!
Atleast that's what I think. Would be happy to be proven wrong.
I think these are good questions. But I also think there are good answers.
One solution is for my client to sentiment-analyze as a filter after the api-call and downrank that way (much like reddit/HN downrank controversials).
Maybe a more generic solution is to allow parties to "tag" twitter accounts. Clients could then make intelligent deductions based on tags (e.g. "political," "controversial," "satirical," "pg13").
I'm sure many other people have many other smart ideas.
There can be an API, yes. But if you want to filter by positivity, you have to expect the company to actually implement that in the API. Otherwise, do you expect to get all billions of tweets over an API and then add positivity on top?
You can't have sustainability, performance and "open for everything" on one single API, there are tradeoffs and constraints involved. Even GraphQL needs certain fields to be filterable even before the API call returns, otherwise one can't just loop over all commits in GitHub universe without exhausting both consumer and provider systems!
Atleast that's what I think. Would be happy to be proven wrong.