For now @psychobunny suggested to store JSON data in the post content. This will work if the post data is filtered for client display, and read for updates when sent to the server. This can be used to maintain a separate index of objects described in posts. For example, geolocations can be indexed in its own database for optimized queries. A post might have multiple associated geolocations, or several GeoJSON "shapes".
Im doing my best to get the word out. Eventually ill have a bit more time to take a crack at theming. A bit more api to accommodate featured and favorited threads and you could really turn this into a massive-community-propagated-blog. That would put you over just about any web software out there.