The procedure is as follows:
First, burninate the tag, if there are currently questions tagged with it. If there aren't currently questions tagged with it, you probably don't need to blacklist it - but see Step #2.
Once the tag is gone - no longer used on any questions - decide if it needs to ...
I (successfully) tried to burninate it. Then an attempt was made to make it go away forever - but it's not optimal. So the idea came up to blacklist it.
Congrats on the new role, @Catija. I naturally have some reservations since I'm on the opposite side of the "welcoming" debate to you, and that remains the battle du jour - but I cautiously wish you luck.
I performed the following search on Bing:
stackoverflow input string not in a correct format site:stackoverflow.com
and got some useful links, with some not so useful summaries:
I did the same search on Google and that one seems to be working OK, but Bing hasn't had this problem before (...
That framing seems to me like it steamrolls a whole lot of important detail, @JourneymanGeek. You can take pretty much any human conflict ever and reduce it down to "both sides want the best outcome!"; the differences in what they think that means are what matter
But if people constantly frame it as us vs them there's never going to be common ground
Especially where the response to good news - that we are not down a cm and there's literally a dedicated team to handle stuff on qa is to bring up old battles
The procedure is as follows:
First, burninate the tag, if there are currently questions tagged with it. If there aren't currently questions tagged with it, you probably don't need to blacklist it - but see Step #2.
Once the tag is gone - no longer used on any questions - decide if it needs to ...
I performed the following search on Bing:
stackoverflow input string not in a correct format site:stackoverflow.com
and got some useful links, with some not so useful summaries:
I did the same search on Google and that one seems to be working OK, but Bing hasn't had this problem before (...