I'm pretty sure you've been on the developer meetings where they have talked about languages. Are you not a fan of some of those solutions mentioned there?
Do you have an API that would lead to me being in a topic page or a feed for a badge or maybe even community and then ask to see all Italian or Tagalog posts and instead of accessing 2000 posts via the api to simply filter and find only 1-2 you can instead query an API that would immediately and quickly populate the list and choose from the typical sorting mechanisms like the trenging algorithm or chronological?
Also i was thinking that having a dozen nodes providing hivemind API is helpful for decentralization and for ramping up to having lots more users...so it seems to me it would be nice to be in there.
Yes, I was part of the language discussion at the development meeting. That being said, I don't think a "solution" for hivemind has been proposed or planned.
I do not provide an API on top of HiveSQL because this will add an unnecessary extra layer. Add to that that such an API would be limited to what I think is OK for me, but not necessarily tailored to someone else's needs. This is already the problem you are having with Hivemind where you have to wait for someone to provide you with the API you want.
Any dev can create its own API or directly send a request that fits its wishes to HiveSQL. The one you are mentioning for Italian would take a few minutes to create, including filtering and sorting. I can assist you with this task.
Regarding decentralization, HiveSQL is of course not comparable to hivemind, but it no longer has to prove its reliability.
Nothing prevents you from creating a thin layer that allows you to switch from one solution to another if ever hivemind ever had to implement the features you need.