Suggestions (formatted as "Answer") should be listed here for at least 2 working days to see what comments they get.

Thereafter, answers should be revised according to the result of the comments, for example, making it clear that a certain set of tags should not be merged and stating the reason.

Wait another working day before you start editing tags and check what the discussion is. If previously there has been a lot of different ideas and comments, you may even ask that a moderator gives the go-ahead.

Report all retagging with a comment, so that moderators can cleanup the back-end (otherwise unused tags are shown in the list of choises when tagging a question)

Comments

@jgr I edited that part to be not so normative: "If you run into a question that can't actually be answered at all, or is a simple How-to or Poll / Survey consider commenting that to the writer and/or convert the question to a wiki (edit -> mark with "community wiki")"

I propose to introduce the concept of sticky topics centralizing news / main ideas and so on. A meta-topic could be created to gather sitcky topics title.
Yesterday, I was suggested to use tags, but it's not efficient. I think sticky topics could be good to reduce the number of "duplicate topics".

Neo: no I didn't touch anything yet. We'd rather get an agreement first on merging appcover into activecover and create a relevant tag for the covers accessories. I hope we could find something better than cover-accesory for the purpose ;)

I've studied links 4, 5, 6, 7, 8, 10, 13 and I've found out that these could be merged to two questions:

Compass in Android apps. The oldest might stay (13, 5 --> 4)

GPS in Android apps. The oldest might stay (7,8,10 --> 6)

Some relative info should be moved from the latter ones getting closed if this idea gets any support. The best way might be to add an answer to those, telling that the question is about to be merged - the writes could then edit+move their contribution if needed.

I think this is an example of things which cannot be integrated wuthout interal knowledge of how things work. For example it is possible that all GPS issues are a problem related to temperature, but it's also possible that temperature is not a problem.

Good point @Nux, and the same could apply to many other cases here. Question mergers probably are not that good approach when threads are long and there are many comments and varying views expressed (even contradictory opinions etc).

Above definitions and this note by @jjaone ; touch-interface in phones or tablets is not purely GUI (even if it is an UI), and utilizes some graphical, haptic, motoric, and others sensory (also audio) interfaces to users- ultimately giving user some experiences when interacting with the device.

Answer: See comments below. It should be checked whether they are used correctly for the individual questions (for correct meaning see comments) but not merged.

Ok, I understand that user-experience and user-interface are required. But I do not see the need to differentiate between "ui" and "gui" on a mainly graphical user interface.

Because I saw "ui" and "ux" synonymous (and will not be the only one), I suggest that not the abbreviations are used but the long terms (and an automatism in the background converts ui/ux to there long equivalent in case it should have been typed -- i.e. the "most-wanted-synonym" feature already mentioned).

No you cant make ui and gui the same: if i type with kbrd it's part of UI but it's not GUI. Come on, there is huge amount of tech/user-space terminology that has its use cases and if you just don't know the differences better leave them.as they are, cause the poster might have had good reasons to use e.g GUI and not.UI

UI is not only GUI, both of which are not UX. And @jgr definately not all abbrs should be turned to new invented tags - they are for.things.that have established names and titles and have been used for decades.

@simo synch is synchronization for sure, but the others let them be for good (not only for now), I explained why already.. Overly merging tags that just look similar is a really bad idea unless you are sure there are no semantic differences in them..And in tech terms one letter can change everything to it's opposite..

@jjaone I wasn't clear enough... I always try to think these issues in a long run, so "for now" should have been like "as long as they seem to work well" or something like that... I suppose we have the same thought anyway. Not forever, not for now, but for as long as they serve us well ;)

@simo It doesn't work like that when you talk abt terms and vocabularies (tags as metadata). There is 'rsync' and there is 'syncml' and they will not start to mean the same thing, even if we waited for eternity for that to happens. In text/user-landscape terms are defined (that's why user guides usually have used terminology defined) and then used accordingly. It's not like lets use this term today like this, and let's see what we invent for this for tomorrow...

To clarify my view on suggestions by some here that UX, UI, and GUI tags should be merged. My answer is no they can't and they should not, cause UX (user experience), UI (user interface), GUI (graphical UI), all are different and mean different things when talking abt user facing layer of sw/hw architrctures or stacks. These should not be merged together, but questions could be reviewed to see if they have been used properly.

Further, in more general notion, all these tag-related mass-cleanings and 'mergers' should not be done automatically just based on that the tags look similar enough. There really could be a very good reason why the poster has selected just a particular tag, and not some other tag that seem to be the same). Then again if some re-tags are not correct they are easy to be changed back by anyone.

Comments

@simo I edited that @jgr's orginal Answer (with definitions and stuff), and no this is not a duplicate of that, this gives explanation why UI, UX, GUI should not be merged. I never got any PM from you,

@jgr Thanks for reply, you don't have the delete anything, I removed some of my OT comments, edited your Q with defs, posted my own Answer that those tags should not be merged, and I will keep it there cause it is important that there is a reason why it is not a good idea. Some PM currently on-going with "simo" but it's sleeping time here too, so Gnite to you, sweet dreams, I'l join soonish..

Merging questions is not upported by askbot and even if topics are similar the idea here is that one question addresses unique problem or request, and if not then they should be marked as duplicates and closed (leaving the first/most descriptive/more voted one alive).

Comments

Are you sure that normal users would know 4g is not ok? Most don't even know about 3g, they just speak abt mobile-data connection as opposed to WLAN-connection. Thus 4g-lte won't probably mean anything but to few. So I'd vote for no don't change them, but sure use 4g-lte in Questions if you want to be exact etc.

@TinTTK correct, and the poster's background, and the type of query, and even the indented 'audience' i.e. to whom it's is written..So in some cases it's best just consider fixing tags only when self familiar with the issue at hand, or self involved in those threads..

lte is the official name for the technology, yes. But as far as I know here in Sweden all marketing is about 4g, so that's what people tend to know/understand. My non-technical friends wouldn't know lte, but they would know/guess 4g, so I guess it depends on culture as well.