Comment 5 for bug 1299879

I'm not sure that what do you mean. I'd say that this change mostly helps users who are currently running separate chat clients to overcome total hub count limits. You've never been able to know whether the user is in a public hub or not because there's no way to determine that from the tag.

If you want to know if your users are staying in public hubs, I recommend setting up remote monitoring, monitoring all their network traffic and performing random home searches where you go through everything they have. Even then they might be able to log in to public hubs without you knowing from it. Not to mention cases where people are chatting/sharing files by using other applications... or in real life (in public).