That would actually be cool. We have a couple issue patterns with the interface between front and backend that leads to our frontend guys always misinterpreting the reason their API call are failing. Wound be cool to annotate “this error message is usually caused by another error message in <this controller>. Please check for this before assuming…”

It's part of a bigger vision, a sort of general-purpose digital spraypaint, where you don't need write access to the data in order to annotate it and we use patterns in the data itself to index the annotations such that you can direct any bitstream into the app and ask:

> do any of my peers have annotations on any of this?

But I think the way to get there is to make a variety of purpose built apps which all follow the same pattern, and I figure annotations on logs is one of the first ones I'll do. It has been slow going though, holidays and weekends, so it'll be a while.