3
This is pretty much a follow-up to this meta announcement by SE. Ideally that announcement would have resolved the issue, but the language in it was vague and evasive, and there have been no clarifications by SE in the 2.5 weeks since it was posted.
The trigger for this issue was a report that o...