This is clearly a meta tag – no reason to have it really. This is Super User, a site for questions about computer hardware and software. Applications are software, so the tag really makes no more sense than software which is of course blacklisted.
The user in question has been notified that these types of edits are counterproductive. If you see these ...
It seems to have three primary uses:
The poster thinks they've been hacked, and they want to undo what the bad software/entity did. Example.
The poster is trying to break into something and needs help doing so. Example.
The poster wants to do something that may require whacking some system's internals (e.g. they're looking for a "Registry hack"), and wants ...
Considering that Super User has a seperate tag for nearly all computer parts, (ram, cpu, power-supply, hard-drive, motherboard, graphics-card just to name some), I think this tag can safely be removed.
Yes, player is too meta. What to do about it?
On many questions, it's just decoration, duplicating a specific player tag. Delete those.
On some other questions, separate word tags are used in place of a specific player tag. Replace those word tag collections with the appropriate tag.
On some questions, it looks like it isn't actually about the player, ...
Yes, it should be removed.
It adds nothing.
From the existing questions, see if they can't be closed as too broad or just off topic before anything else.
If they're otherwise good, then edit as necessary and remove the tag while you're at it.
Yes, since it's currently applied to many different things (routers, BIOS, SSDs, even Windows), nobody can be an expert in all things bricked. It's kind of like saying something's broken - not helpful in the least.
I might be on board with, say, a bios-bricked tag because it's entirely possible for somebody to be an expert in saving toasted BIOSes.
Yeah, delete itself does not imply anything. The tags could be more specific like data-recovery for getting deleted data back. Or data-removal or file-removal, though I doubt if they are even necessary, except when you don't have permissions on the system.
This has been enabled. Highlighting is now on, with no default language set on both SU and Meta SU. VB highlighting has also been enabled for the VB tag.
You'll need to remember to manually add the hints, and you should be good to go.
Also, this is a pretty advanced feature, so please don't expect new users to know about it (as there's really no way for ...
Questions referring to the Windows Installer packages (.msi files) should be tagged windows-installer.
The tag msi should be merged (and synonymized) into windows-installer as company tags aren't very helpful and people will use the tag to refer to Windows Installer packages anyway.
After the next build, the ban message on your flag summary page will indicate how long you must wait before flagging again:
Fair warning: flag ban durations are calculated on demand. If more flags are declined after you view this message, the duration may be extended; if more flags are marked helpful, the ban may be lifted entirely. You should treat ...
Your flag said,
A duplicate, would be better if the whole thing would get removed. (Only I answered anyway. So...yeah.)
Maybe that was misunderstood by the mod who handled it. I also had to read it twice. We're all humans, remember. Maybe you could have written something like:
Please delete my question. It's a duplicate of an older post, and I already ...
Completely agree with you. Checked first 50 question of tag - found no reason to keep it.
Moreover, a lot of questions tagged with recovery tag also have data-recovery, password-recovery andpartition-recovery tags with them which makes recovery tag unmeaningful.
Another part of questions use 2 tags e.g. partition and recovery in place of partitiion-recovery,...
This is due to a rather nasty spam influx a couple of years back which resulted in a blanket ban on korean: Sudden influx of Korean spam
I've spoken to a member of the team and they have pushed out an update to the rules that should be slightly less restrictive.
Give it a whirl and let us know.
I'm not sure if it's a bug. the previous flags are dismissed and you're flagging it for some other reason, perhaps the post has been vandalized again. It's up to you to not flag it multiple times.
And oh, don't be fooled thinking Mods don't notice this or others haven't tried this before. Frivolous flags are treated with disdain, and not only we decide to ...
Tag removed from all questions.
Questions about setting up a helpdesk service are off-topic for Super User. If the question has to do with helpdesk software, it might be on-topic for Server Fault, but remember not to migrate crap. In any case, this is a meaningless meta tag.
TLDR: burninate bugcheck, retag to bsod
Being a WinDbg user (see my profile on Stack Overflow), I totally agree that these are synonyms.
As Ilmari Karonen pointed out already, this is defined on MSDN:
When Microsoft Windows encounters a condition that compromises safe system operation, the system halts. This condition is called a bug check. It is also ...
Done. All remaining diy questions are closed; the others have been edited to remove that tag and fix other minor issues. (I also did my best to remove the hardware recommendation aspect when it appeared.) I certainly agree that diy provided no categorization value - it was used on all sorts of things, from hardware improvisation to hardware replacement to ...
I say burninate application-error.
Super User has a long-standing tradition of burninating error-related tags. I see no reason to break this tradition now.
error: What could we do with the [error] tag?
errors: Burninate error, errors, fatal error
error-message: Let's nuke the "error-message" tag
problem: Are "error" and "...
This is now enabled, but there's no default language set, which means you'll need to provide hinting as to what scheme should be used for it to show.
On a few tags, by tag kind of makes sense for obvious reasons. However, in others .. it wouldn't, depending on the content of the post. In order to stay consistent, we're just allowing manual hints as needed, ...