Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
QoS is policy as applied to traffic (queue priority, CBR, CIR, DBR, etc). Traffic-Shaping is applying bandwidth policy to particular types of traffic. While they're very closely related, there's a different. In-App QoS or Traffic-Shaping is part of the paricular app and shouldn't be tagged as the others (unless the question related to their interaction of course).
We're not the government, we don't have to assume innocence until proven guilty. If the questioner doesn't like it, they're free to find another website. This is a professional site before technicalities, process and procedure is at least as important as technical capability.
@Gilles, I fail to see how keeping away from legally questionable topics is morally or practically "wrong". I don't 100% agree with Erik, but disagree that we should get lawyers involved to determine the legality of a question before closing it. Who's being impractical now?!
I'd like to see the a small addition to the FAQ under the kind of questions not to ask, bullet 6: "the answer involves circumventing licensing, corporate/network policy, or applicable laws".
@John, I like the design, simple and elegant, and definitely inline with current trends in monochromatic design. And besides that, you're not a Mod, you don't get one anyway. =P
@growse, OT for this question but edits should bump the question so the community is aware of what users are doing. Users are highly discouraged from doing mass edits/retags like that, and even more so during the work week. Devs can mass retag without bumping; if that is needed for a tag post in mSF and they'll take care of it. Back OT, as Jeff suggests, unless one version is substantially different from another, it should not have a version tag.
