microsoft / winget-cli

WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
https://learn.microsoft.com/windows/package-manager/
MIT License
22.99k stars 1.43k forks source link

Regulate tag usage #2049

Open github-account1111 opened 2 years ago

github-account1111 commented 2 years ago

Description of the new feature / enhancement

I was wondering if I can install ffmpeg through winget, so I searched for ffmpeg and got this and this:

> winget search ffmpeg
Name    Id               Version Match       Source
---------------------------------------------------
Wav2Bar Picorims.wav2bar 0.3.0   Tag: ffmpeg winget
y2mp3   moshfeu.y2mp3    2.5.6   Tag: ffmpeg winget

The two packages that came up are not ffmpeg or alternative ffmpeg frontends. They might utilize it at some point, but that doesn't mean they should come up when the user searches for ffmpeg. If you look through the tag lists, there's:

That almost feels like a form of advertisement? "Add as many tags as possible to come up in as many searches as possible."

Proposed technical implementation details

Limit tag usage to 1, maybe 2. Regulate tag usage.

Far as I can tell, tags were introduced to aid the issue of some packages having very specific names, meaning a user might not find it upon searching. E.g. Foobar2000 could benefit from being searchable with a "foobar" tag, Geforce Now with "geforce," Docker Desktop with "docker." How would "wav2bar" be useful popping up for "ffmpeg" or "flatpack" or "electron" or "audio"?

RokeJulianLockhart commented 2 years ago

For such situations as these, if the searcher were to support searching dependencies of packages, this would remediate any desire to utilize such tags maliciously to improve WinGet SEO of those packages. However I estimate that this would be too much for the servers to manage, even if this feature were to be utilized infrequently, as I expect that it would.