WeChat ID
aaronpk_tv
#w3c
-
-1 Seems doable with creating and updating posts and handling replies, but not sure how this specific case fits into a social API -
-1 Out of scope for first version
-
-1 Out of scope
-
-1 Out of scope for a social API, we are not making a ticketing system or CRM
-
-1 Agreed with Ben that it's simliar to polls, and seems out of scope for version 1
-
-1 duplicate/not clear
-
-1 Out of scope for the first version, I have no plans to implement
-
+1 I have implemented this except for deleting comments
-
+1 Already implemented. This sounds like RSVP'ing for an event. I have implemented sending and receiving RSVP posts on my site since June 2013.
-
-1 This seems doable with comments on a post, and if it requires something more, I have no plans to implement.
-
-1 This seems able to be accomplished by comments on a post.
-
-1 What new part of the API does this require?
-
+0 The private content that I create on my website also provides the list of people it was shared with, so that if someone were to copy it to their system they would have the original audience restrictions along with the post as well. However I am giving it +0 because I'm okay with not seeing this in the first version.
-
-1 The story is too complex, I don't see the primary goal of the story, so it feels out of scope.
-
0 Not sure what is unique about this story.
-
+0 This seems like it's already covered by the ability to share a list of "friends" with applications.
-
+1 I have already implemented publishing my weight from my bathroom scale http://aaronparecki.com/metrics/weight
-
-1 Unclear what the actual goals or concrete implementation would be.
-
-1 This seems like a duplicate
-
-1 As much as I love location-based tech and live-updating GPS trails, I don't see how this fits into a social web API, much less the first version of one. A lot of this communication could take place with public or private group messages as well.
