When I say "get", what does it mean to you? A GET request? To retrieve something? To query a database? To call the get method on a C# property? appears to encompass all of those and more. We should either burn it or split it up.

However, splitting it up would just result it . For the SQL query, we already have . Ultimately, most should questions should be retagged .

Its tag wiki suggests that it is for the HTTP GET protocol, however, there are quesions tagged with that don't fit that description. A manual retag might be the only solution with ~375 questions tagged with it. There are also some that have both the tags. The fact that you need two to describe the question shows that they really should be changed to .

As suggested by RiaD, maybe use . We could maybe burn and replace it with ?

  • 19
    I would name it http-get – RiaD Jul 20 '13 at 20:46
  • 1
    Questions are constantly being tagged with it. Look at sorted by recents. At this moment, there is one from an hour ago, one from 4 hours ago, 7 hours ago... I think we shouldn't just burn it, but ban it. – Cole Johnson Jul 21 '13 at 3:10
  • 1
    See also the poor, oft-abused set tag (this question was tagged both get and set). – michaelb958--GoFundMonica Jul 21 '13 at 6:50
  • 2
    @michaelb958 those poor little tags! They never did anything wrong and yet they're being abused by new users! It's unethical! – Cole Johnson Jul 21 '13 at 6:52
  • @ColeJohnson I was thinking about a Meta post dedicated to those two unfortunate tags, but this question covers some of it already. – michaelb958--GoFundMonica Jul 21 '13 at 6:55
  • 1
    Both http_post and http-get should be made into http-request instead. – hjpotter92 Jul 23 '13 at 20:03
  • 2
    reflagged? I like that word. – TRiG Jul 23 '13 at 20:05
  • Generally, when there's lots of work to do, it's best left to people with edit privileges, to give the mods a break. It's fine to flag the mods for one or two things here and there, but if there's a whole series of 'em, don't. – TRiG Jul 23 '13 at 20:40
  • 6
    Both [http-post] and [http-get] are existing tags, so we should definitely retag to those. – Old Checkmark Jul 23 '13 at 20:45
  • 1
    @hjpotter92, there are enough nuances to GET and POST in the context of various languages and platforms to support keeping their own tags, IMO... just barely. – Charles Jul 23 '13 at 23:05
  • @Charles can you elaborate? – Cole Johnson Sep 27 '13 at 0:42
  • @ColeJohnson, while the rules for parsing GET and POST are identical everywhere, how each platform handles accessing those values is different. There's enough of a difference here that keeping them as separate but similarly named things is worth it, IMO. – Charles Sep 27 '13 at 4:27
  • @Charles feel free to make that an answer. – Cole Johnson Sep 28 '13 at 19:07