-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Proposal] Remove Question object #216
Comments
Probably true. As we discussed on IRC, StatusNet / GNU Social had a polling extension that people liked to use when I was using it. However, I don't think it's critical. Also, one side effect of when that plugin became introduced was my inbox would flood with poll responses, so remembering minor irritation surrounding that, maybe it's a-ok to remove. |
What timing! Twitter is now going to add poll support right as we're considering removing it. :) |
I'm still for removing it, The only user story supporting it has a few -1s and several 0's @cwebber just because one silo supports something, doesn't mean its something we need to support other than as an extension. |
I've received feedback that there are implementers interested in using Question. Given that, I'm going to withdraw this proposal. |
Which implementations? Can we cite/document this publicly? Ideally have they blogged about it? Also, "implementers interested in using Question" is a good justification for an extension rather than keeping it in the spec. Better to drop it and make those implementers speak up publicly on IRC / email / here in the issue. |
Feel free to open your own issue proposing that it be dropped. I'll make sure that all open proposal issues are suggested for the next call agenda. As for implementers, here's one in particular: https://lists.w3.org/Archives/Public/public-socialweb/2015Oct/0191.html Based on discussions with members of the WG who have voiced intent to implement AS2 and Question, I'm -1 on dropping it. |
The Question object can likely be better handled via an extension.
The text was updated successfully, but these errors were encountered: