Subscribe to Hashtags

Subscribe to Hashtags

Issue ID:464
Issue Category:feature
Component:core
Priority:major
Status:will not fix
Assigned:evan
Milestone:0.7

Adding the ability to subscribe to a hashtag the same way you subscribe to a user would have several benefits:

* You could create de fact groups. Assign a hashtag to the group, people join and leave the group by sub/unsub to the hashtag, and you can post to the group without having to track members

* Mimics some of the real time "track" functionality in that posts containing hashtags show up in your stream in real time. You don't need to visit the hashtag page to see new posts.

===================================

8/3/2008 Discussion summary between kshep & brucelerner (captured by bruce)
[related ticket #150 & #116]
It seems that there are 3 types of 'groups' we were discussing: topic-oriented, denter-oriented and function-oriented. In all three cases, a user self-selects to 'use' groups.

* topic-oriented is similar to hashtags. It is a dent that is "sender" identified for inclusion. Can be consolidated via search or inserted in the a user's lifestream.

* denter-oriented is system identified, meaning that the "sender" does not have to do anything except dent to be included the group. This is like 'follow' except its a multiple follow separate from the whole lifestream. It allows focus during a discussion, 'replacing' the lifestream view while active. Might also be thought of as a filter on the lifestream.

* if hashtags were added to the lifestream then topic- and denter-oriented groups could be filters on the lifestream.

* 'track' is a superset of topic and denter groups. It can actively consolidate names or words (including tags) into a stream.

* function-oriented allows control of the identi.ca settings based on groups of information. It would allow a temporary change in the dents followed or sent to devices.

(apologies if all my terminology hasn't migrated from twitter yet).
=================================

Legacy Data

This issue was migrated from another tracking system. The legacy data at time of import is provided below as a reference.

Ticket ID: 
464
Reported by: 
kshep
Owner: 
evan
Status: 
closed
Resolution: 
willnotfix
Type: 
feature
Component: 
core
Priority: 
2
Version: 
undefined
Milestone: 
0.7

Updates

#1

we have groups, and that allows ppl to subscribe

Login or Register to modify this issue, or to receive updates by email.

You can also subscribe to the RSS feed for updates to this issue.