6

I was editing a question today and discovered an accidental mis-tagging by the user:

Create .listing file using use Net::SFTP::Foreign

The original tag was for , a tag which exists for the Ruby Net::SFTP module from the Net:SSH library.

What the OP was after was the non-existent tag for the pure Python implementation, also conveniently named Net::SFTP, which according to this wiki is a full SFTP client written in Perl with lots of bells and whistles.

Oh dear, a search for [net-sftp] -[ruby] -[ruby-on-rails] leads to more questions mis-taggingly using the Ruby one, but also at least one question in search of the PHP implementation of a Net::SFTP library.

Obviously, what this world needs more than another intervention in the Middle East is more tags - but how to taxonomize all these identically named tools?

  • 2
    Related: How to handle tags with multiple meanings? – gnat Sep 17 '13 at 8:56
  • 2
    Thanks @gnat, I noticed from on example there that they seem to have remedied by putting a disclaimer style message in the tag itself: smf, which then leads users to the specific/new disambiguous tag. In this case, where there are multiple, might it be effective to create one for each variation needing specific tags, re-tagging the existing and then putting such a message in the original? Hopefully the tag auto-suggestion would suggest the correct net-sftp-php or net-sftp-perl based on the question's context... still seems complicated though – ljs.dev Sep 17 '13 at 9:06
  • 1
    how about [net-sftp] with a language tag? – Robert Harvey Sep 17 '13 at 15:16
  • I think it's a way to go and I'll volunteer to rewrite the tag wiki. Do I have the peoples' blessing? – ljs.dev Sep 20 '13 at 15:04

You must log in to answer this question.

Browse other questions tagged .