ben_thatmustmelvster, we aren't building user stories for the web in general only for a particular purpose. By that logic the social API would be a gaming platform, CRM, video streaming service, inventory management, etc. There has to be some limit to what we want to focus on.
ben_thatmustno, i don't think it can or should handle such stories. anything that can send data can handle every user story ever if you sufficiently wrap it with implementations on both ends, i don't think showing that you can write binary data between clients using the social web is really useful to use
ben_thatmustFor example, I would consider live teleconferencing out of scope of the social API. Certainly you could probably write the binary data and share it across a social API in some odd method, but it would likely be a lot more efficient to use existing applications/other APIs. I don't think we want live streaming as a user story we should consider when designing the API.
melvstersure, every person will have their favourite user stories, but the underlying technology should be such that the user stories are possible, any working group will want to prioritize, but standards quality work should be scalable