Unnecessary splits should be ignored.

For their searches, MyCoPortal has a great solution. It is the Taxonomic Thesaurus that gives you search results not only for the name you entered, but also for the synonyms of the name you searched for. MO should make a deal with MyCoPortal and build the Taxonomic Thesaurus into our MO system. I can imagine that to build up such Thesaurus and beef it up with names requires unique encyclopedic knowledge of the nomenclature of fungi. Would it be possible to get it from the MyCoPortal as a sealed unit and let it on them to make the updates?

Requiring everyone to agree that a name shouldn’t be used is far too strict. There are always going to be idiots clinging to patently wrong old names for terrible reasons.

The reasons for Armillaria tabescens are good, but the reasons for Desarmillaria tabescens are better, and letting multiple names float around is confusing. From my post on FB: “That’s how the genera are going to be treated in future literature. When you read a new paper next year you don’t want to have to figure out if the cool weird attribute it’s describing is about the hobby Armillaria or the mycologists’ Armillaria. And when some new Desarmillaria species is described without a corresponding Armillaria combination, you’re going to have to accept the genus anyway.” I’m sympathetic to questionable cases having multiple names accepted (Lepista nuda and Clitocybe nuda), but I’m not convinced there’s that much ambiguity here.

Anyway, there are much more egregious errors in other parts of MO so this is the last time I’ll deprecate “A. tabescens” (…for now…)

There is nothing wrong with this name so it should not be deprecated. Only names that everyone agrees should not be used should be deprecated. There are lots of examples of taxa with multiple valid names, and which one to use is a matter of personal preference and taxonomic philosophy.

This honey mushroom does not really care, how it is called. Follow the Interantional Code of Nomenclature of … and forget deprecation!

It wasn’t a mistake; they used it multiple times, obviously consciously. It’s not a fluke; these are different authors, a year later from the 2017 paper that established it as a genus.

Just because the new Armillaria paper made the mistake of using Desarmillaria doesn’t mean that we need to make the same error on MO.

Agreed, but the split was made and other Armillariologists have adopted the name. Because one synonym should be chosen as preferred and this is the direction taxonomists have chosen, MO should use Desarmillaria. I would love to see a publication explicitly rejecting Desarmillaria, and therefore reason to change it back on MO.

Desarmillaria was an unnecessary split.

A new Armillaria paper with entirely different authors uses the name without qualification; this makes it the current Armillariologist “consensus”.

http://www.tandfonline.com/...

There was no good reason to split Armillaria.

There is a paper, External Link , which concludes that the correct name for this species is Armillaria socialis (in my opinion, reasonably). But Mycobank and Spec.fungorum give these two as different species (last year they called the A. tabescens the correct name, I guess that is where the synonymy here came from). Should we make A. socialis the correct name (possibly leaving tabescens as valid too)?