If you do a search for your feed you will see the number of readers.
Right now the API is limited to developers building user facing apps. Offering a long term API to other kinds of developers is not a commitment we are ready to make.
The analytics we mentioned in that tweet will be free.
What's the issue with using the same user-agent method that's a standard with other feed-readers? Seems like you're doing extra work so that blog authors can also do extra work.
Finding the right balance between DOM and MVC is not easy - yet remains critical if you want to capture the flexibility of the DOM and the update capabilities of MVC. It is great to see Jeremy/BriteSnow pushing the limits and capturing some of the best practices.
Right now the API is limited to developers building user facing apps. Offering a long term API to other kinds of developers is not a commitment we are ready to make.
The analytics we mentioned in that tweet will be free.