Has anyone run any benchmarks for NodeBB on iOS and Android devices?

For the past year, poor Android performance has been a pain point for Discourse & Ember.js:

• https://meta.discourse.org/t/why-is-discourse-so-slow-on-android/8823
• http://discuss.emberjs.com/t/why-is-ember-3x-5x-slower-on-android/6577/23

The bug in question appears to affect several JavaScript applications (Angular-based ones as well for instance), therefore I was curious to know if any similar findings have been made with NodeBB.

The good news is that they appear to be making some headway on the issue.

@a_5mith Oh absolutely. Yours is a very good example of explicit use of tags. Used in this manner, it wouldn't be hard to establish a good tagging norm.

I just want to train users to choose their tags very carefully. Especially if you can choose to be notified by certain tags, it'd be important to limit their use. So when a bewildered user stops by the general support forum, they have to carefully choose 2 tags out of pre-existing ones (StackOverflow style) to get the right people's attention.

@Giorgio-Chiodi said:

There's no correct way to use them.

That's where I think forums ought to be more opinionated. With some exceptions in special categories, I wouldn't want to allow more than 2-3 tags per thread.

It's a novel idea, but frankly I don't think this needs to be its own thing. I would roll it into tags.

Reason #1: You get weird URLs
Example 1: /topic/868/nodebb-plugin-topic-badges-topic-badges/
Example 2: /topic/1107/nodebb-plugin-google-adsense-google-adsense

Reason #2: It would fit neatly in with tags
Here's how it could work: When I start a post with a [, I could be presented with an auto-complete list (a la @mentions) of canonical tags, i.e. tags that will be shown in this top spot, and might have an icon attached to it etc. No extra text would be added to the URL/title, it'd just be added as a tag.

Reason #3: Tags are more powerful
I don't really see the point in giving a thread the nodebb-plugin-google-adsense badge unless this badge can be used as a filter to show only threads using this badge. In other words, how tags work.

Another thing about tags is that I feel they should either denote something uniquely identifying about the thread they're applied to, or not be used at all. Take this one for instance:

With one exception, all of these tags are better covered by a search. Say you're looking for a plugin with some kind of YouTube functionality. Sure you can get a decent overview with the youtube tag, but you won't trust that to be an exhaustive list, because you can't trust people to have tagged their threads appropriately (a common issue for WordPress plugins for instance). So you search.

As soon as you go past 1-2 tags it's also very noisy (especially in combination with the Topic Badges, which I'll make a separate comment on)

The only tag I find worthwhile is imgshow, and that's assuming it would be unique to this plugin. This is where hierarchical tags (think Google Code issue tracker) can be very useful, because you could make rules for special tag groups, e.g.:

If I create the first instance of the plugin:imgshow tag, I am now the owner of this tag. I will get a notification of all new threads using this tag, and I will have moderation rights over every thread that uses this tag.

I always thought tags' potential for increasing discovery of new things is severely under-utilised.

The WordPress support forum uses tags to great effect, though there's certainly room for improvement. See this post for the Contact Form 7 plugin for instance.

Thanks to its (hidden) contact-form-7 tag, it spices up the topic with two key additions:

• A prominent plugin title
• A widget with key links:
• Plugin page
• Frequently Asked Questions
• Support Threads
• Reviews

Another example I like is news on IndieDB. Scroll down and you'll see there are boxes for Related Games/Engines/Groups. Tags would be good for this sort of thing.