Wikimedia:Wikiauthbot-*/sr should be moved to Wikimedia:Wikiauthbot-*/sr-ec

Subject says it. The */sr messages are not editable, telling users to edit */sr-ec instead. I'm not being allowed to rename them either.

I don't know if there is any other project still using */sr; the search features don't seem to make it easy to find out.

Actually "/sr-ec" is an old legacy bogus code used ONLY on some Wikimedia sites, it should be "/sr-cyrl". Many things even in Wikimedia wikis are using "sr-cyrl" instead, as much as possible, but the conversion is not terminated. Then ""/sr" is still correct because it is the default script used most of the time. The creation of Serbian in the 1990's was a nightmare to manage (including the management of numerous ISO codes for country divisions used as legacy language variants in BCP47), whereas the deletion of "/sh" in ISO 639 (but not BCP47) was a severe error. Unfortunately at that time, ISO 639 was a complete mess, ISO 15924 did not even exist at that time, as well as ISO 639-3 with the concept of macrolanguages, and we were operating with an antique version of BCP 47.

Since RFC 4646 and ISO 639-3 all is clear, but "sr-ec" and "sr-el" (complete inventions by some uninformed Wikimedia users that did not care about existing standards at that time that stated that "EC" at that place would indicate the Ecuador country; same remark about "EL" which was exceptionnaly reserved in ISO 3166-1 for use in the European Union documentation for referencing Greece instead of using "GR") should no longer be used at all and should have been fully migrated by Wikimedia to use standards since many years (but apparently no one cared because there was no demand to use "sr-ec" and "sr-el" according to standard (Serbian having no demonstrated usage in Ecuador, it may be used in Greece but with no specific regional variant found in European Union documents using the "EL" code for that, so there was never any emergency to change that... except adding unnecessary complications in i18n support libraries and databases and invalidating some security tools or indexing tools that want full BCP47 conformance).