Taglist
Taglists are a central and essential part to the application. It entails a collection of users (who can be individually subscribed to a taglist) that can be tagged to content that pertains to the taglist itself.
Setting a taglist up is fairly straightforward and requires 3 components
This should be a concise word that is unique to this taglist. This abbreviation will be used in commands when referring to this taglist.
This option should be used if the content for this taglist will incorporate ratings (Safe / Questionable / Explicit).
A simple human-readable description of the taglist.
User-subscriptions require a taglist to persist. This means that when a taglist is removed, all the subscription-data is removed along with it. Any users that no longer have any subscription-data (i.e. any users that were only subscribed to the taglist that is being deleted) will be permanently removed from the system. If this occurs, the application will warn in advance on how many users will be removed.
Ratings are a useful tool to give subscribers more control of taglist content that they will see.
If a taglist is selected to use ratings, these ratings will have to be explicitly set for:
- Most commands.
- When subscribing a user.
- When setting up an archive.
For example, a tag command without s / q / e will ignore any taglists that require ratings.
If a taglist without ratings is changed to one with, it will default to using s, q, e for all subscriptions tied to that taglist.
The taglist abbreviation is case-insensitive. This means that if another taglist is created with the same name, it will replace the existing taglist while retaining its subscriptions. Case-sensitivity cannot be used to separate abbreviations.