Our Track API evolved over time… Please make sure you refer to the track documentation for the current status
It’s been up for a few days… just enough time for us to iron anything that you could have gone wrong, but the version 2.0 of our track is live. Internally, we call it trackr, because it’s now Ruby (like red diamonds). It uses a handful of Redis, XMPP, Ruby and a few other awesome things. Please ask if you want more details on how it’s built. What does it bring?
Operands
The first thing is the end of the awesome bug which would create matches for “super hamster” when somebody subscribed to perham. It could have been a feature, but for now, we’ll stick to something more natural!
It brings the AND operator. Looking for info about the Apple Store, about San Francisco? That’s easy. You can also exclude terms. Apple-iphone-ipad-ipod should help you screen Apple’s ex-core business.
The OR is by essence quite easy : subscribe to 2 feeds matching whatever you need. For once, we’re pushing the complexity down to you, but we think it makes sense.
Scoping
We love geo stuff and can’t wait to see more feeds actually geo-tagged, so we’re paving the way : you can already start to geo-filter searches : want to know about wildfires around your place? Just give us a latitude and longitude, as well as a radius, and we’ll be happy to filter out anything that’s outside of this. The radius is in kilometers (metric system FTW!). Check this example.
Of course, there is more to be done, but check our documentation if you’d like to start tracking some data. We’re working on adding more stuff… and if you’re a crazy XPath expert and know how to build fast matching, I want to chat with you, because Superfeedr’s got work for you too.
Comments