Since Twitter created the @ and # tags, more and more applications are finding interesting ways to use this new way of forming freeform relationships between people, groups and content.
Interesting examples:
- Google Plus
- GitHub
- Discourse.org
Creating a relationship between people, groups and content
@ username
- creates a relationship between user and content
- allows other users to include users into the conversation or workflow (e.g. hey @user2, I think you should check this out)
@@ goupName
- creates a relationship between the group and the content
- allows groups to quickly be added into the context or workflow
Hashtag categoryName
- Hashtags would be a quick way to categorize Tiki objects
- If the category doesn't exists, Tiki would auto create a category
- Fast workflow for categorizing content would make it easier to users to share and properly associate objects.
Things to think about
- When creating the Hashtag, should it simply get indexed as a searchable item OR should we tie it into the Categories somehow (category mirroring). That way categories would also be considered as hashtags. This means that when a hashtag is added to any content type, it would essentially be the same as if we had categorized it.
Potential Issues
- For @username, we need to see if we can accelerate the performance of the autocomplete. Right now for example when entering a username on Dev.T.O inside a bug report under the "volunteered to solve" field, it takes a very long time before the autocomplete kicks in.
Use Cases
- Project Management
- Bug Tracking (dev.t.o)
- Social Networking
- Online Communities
- Wiki Collaboration
What problems does this feature solve?
- Categorizing items is sometimes cumbersome and not intuitive. Also difficult to setup the right permissions to make sure that only certain categories are seen by users.
- Ability to add new users or groups to a conversation, task etc... Right now there is no way to "Add a Follower". This is often the case on dev.t.o when we need to bring in another developer into the conversation. The only way to do so is to copy the link and send that person an email manually
Team
- pascalstjean
- koth
- patrick.proulx
- jonny (need to discuss)
- LPH (need to discuss)
- YOU?