Heya!
Have not read thread, there's that disclaimer - but I will, today. Just passing through real quick and saw the taggings. A couple notes:
1. Yes, it is true this only affected 25 devices out of 1200+. Obviously though, 25 of the most popular among the more technical community.
2. We badly wanted to prefix them legit, so you could click said prefix and filter to only your carrier, but the multi prefix functionality is highly busted and broke many things for us when we tried it out. In fact, we're still recovering from it. BUT, we do plan to get it working, and would like to then properly multi-prefix these forums.
3. This is why we put them all as [whatever it was before] at the beginning of the titles. We are hoping everyone follows that lead/example, because when we get multi prefix working again, that will make it much easier to automate applying those prefixes.
4. This was done for a reason - yes maintenance on our end is easier like this, true. But it is because:
a) we need to be as consistant as possible on a site like this, for various reasons
b) it was the only way we can introduce a new tabbed-like way to access root/resources, which you'll see in a few weeks.
Honestly from a maintanence perspective multiple forums was a nightmare. But I agree it's not the best for a certain group of users - especially since it would appear advanced searching, for example, in S3 root forum, for [verizon] isn't pulling any results.
I will talk with Rob and see if he can bump priority to get multi prefix working.
Edit: One solution would be to nix the current root prefixes, "rom, kernel, etc" prefixes in favor of carrier prefixes. Then for THOSE, use the [rom] in titles.
In fact, I like that. The problem is, then it becomes a maint thing keeping track of what carriers for what forums. But I would be willing to do that..
vote:
http://androidforums.com/threads/in...-to-be-broke-by-carriers-now-combined.915007/