search

appdotnet / api-spec

App.net API Documentation is on the web at https://developers.app.net. Source for these docs is in the new-docs branch here. Please use the issue tracker and submit pull requests! Help us build the real-time social service where users and developers come first, not advertisers.
https://developers.app.net
950 stars 98 forks source link

Unified interactions #261

Open scruffyfox opened 11 years ago

scruffyfox commented 11 years ago

(An extension of https://github.com/appdotnet/api-spec/issues/247)

Would be great to have a unified interactions stream which includes mentions, replies, reposts, stars, follows etc (like, dare I say it, Twitter does) as that would allow clients to use one stream instead of having to have 2 separate streams

Or prehaps a global "unified" stream endpoint with a comma separation filter on what to return which could replace the current interaction specific and mention specific stream end point.

Thoughts?

berg commented 11 years ago

Just to be clear, the two streams you're referring to are the mentions stream and the interactions feed which has everything else? We might be able to include aggregated mentions in the interactions feed if that's useful; in terms of my own common usage patterns, it didn't seem to be. How do you think this should work?

scruffyfox commented 11 years ago

mentions in the interactions stream is what i'm basically asking for, but thinking about future proofing, if you guys add a new type of interaction or something, it doesn't work, the single stream with a comma separated 'filter' would work and be future proof as you would just append the filter with the new interaction type and it would just work

berg commented 11 years ago

The filter thing makes sense (though you should just ignore any interaction type you don't understand) for efficiency. It shouldn't be too hard to do. I'll make sure it's on our list.