23 January 2005

Technorati Tags: An end-users perspective on what is possible


Creative Commons License

This work is licensed under a Creative Commons License.



Executive Summary


This is a user-end perspective on Technorati tags. This note outlines a number of potential features which Technorati may wish to explore. We have outlined a number of features which a Technorati Chicklet may need to integrate with.


Overview

This note outlines a number of potential programs Technorati may choose to look into when exploring Tag-integration tools.

This note focuses on a chicklet and the various types of possible future capabilities, which this simple tool would need to integrate.

This note may serve as a template for discussion among Technorati users and developers on future directions Technorati may embark with in .

Discussion

Technorati has tags. And it looks as though Technorati could very well have a number of other interesting projects in the works. It remains to be seen which of the below concepts are incorporated into Technorati design plans.

Simply put, Technorati tagging is fast. Users can post the Technorati tag HTML and you’re all set. Feedburner has these chicklets for counters.

I thought it would be interesting to see the same type of thing for Technorati. Perhaps some developers might want to work with Technorati to come up with a range of chicklets that people can use.

  • Technorati Tag – A tag button or chicklet to quickly spread tags

    Users might like a single chicklet to quickly post a Technorati Tag. When designing this chicklet I thought it would be useful to share the concept of the chicklet, and also share the vision of where Technorati Management may choose to take things.

    Again, this is purely speculation. But if developers want to know what end-users are thinking, this note might assist in this discussion. Also, it is hoped that the following list of ideas might also be a set of features that developers keep in mind when developing Technorati tools.

    Today’s tagging tools need to be made with the potential features that may be added. Clearly, these have not been developed, but the following might serve as a template of where things could go.

    Again, it remains up to Technorati Management to choose which features are ultimately incorporated into the Technorati platform.

    User Requirements

    Users may want to do more than simply post a Tag-line in their blog or host. They may choose to have some more interesting methods to post the link. One solution would be to combine the Tag-HTML with a chicklet.

    One analogy is the FeedBurner Checklist. It remains to be understood how Tagging catches on; with time, users may want more interesting options and more colorful features to promote their individual tags.

    In my view, it is in Technocrat’s interests to develop simple promotion tools for the individual user to post. These chicklets would not only promote the individual user’s tag, but quickly brand the tag as being associated with the Technorati family Just as the feed-buttons have caught on, if the Technorati-tag button is designed correctly with future requirements in mind, it could similarly prove to be an excellent promotional item not just for Technocrat’s tags, but also end-user projects.

    Desired Technorati chicklet features

    Here is a list of general user-end requirements associated with Technorati Promotional Tag. The list is merely notional.


    Technorati Tag Chicklet Concept

    A. Integrated

    Combined tag-and-chicklet image. The chicklet would include the Technorati HTML to link to the tags.

    B. Ease

    Simple copy and paste to either blog-content or template. The chicklet would be easy to copy and place.

    C. Adjustable

    Option to add embedded Tag Comments to say more about the Technorati Tag. Users could modify the chicklet to add comments.

    D. Flawless

    Successfully demonstrate the inputted tag works in the chicklet: Easily added, links to the correct tag. The chicklet would obviously need to work.

    E. Interesting

    Colorful, elegant design and colors consistent with Technorati color scheme. The chicklet would need to be interesting to look at reflecting well on both Technorati and the end-users choice in both the tag-subject, and in associating themselves with Technorati and the tags and add something to their hosts and sites they cannot currently get from other buttons.

    F. Flexible

    Chicklet design also needs to be flexible enough to accommodate future changes and additions to Technorati Tagging software tools for users, to include the following types of possible changes, upgrades or features.


    Purpose

    The rest of this note serves two purposes: To outline various hypothetical concepts which developers would ensure the chicklet integrates with; and also outline possible development efforts for Technorati.

    Even if the chicklet idea is abandoned, it is hoped that the list of tag-related concepts might be incorporated into other development efforts. Whether they are isolated to Technorati Tags, or more broadly to Technorati member tools remains to be seen.

    Potential Technorati Features

    This is a list of the possible features that Technorati could develop. These features are only speculation. Developers working on creating tag-related tools would have to consult Technorati management on the actual future directions.

    This list is independent of management and no way reflects management’s actual plans and directions. If you use this list, you do so at your own rise. Developers and end-users: Please consult Technorati management on their actual plans.

    1. User-defined displays of tag results

    A Technorati platform that allows users to screen, select, prioritize, and ignore other blog comments associated with the Technorati tag

    2. Foldering

    A Technorati tag support system that allows end-users to organize the tag-results into folders, clusters, or other groups that end-users can link-to-in-a-single-click, and grab all URLs for the tagged-blogs and quickly comment on a group of tags.

    Folder would permit end-users to know which tags had been added since the last visit; to zero-out all comment to a restart position of “No new tags”: and put at the front of the reading list those new tags added since last review.

    Integrate with a section called, “my tags” listing all tags the user creates, monitors, lists in blogs. Allow end-users to differentiate tags on the basis of author, use-location, blog-sue, subject matter.

    A member-tool that allows users to group tag-results into folders; list the number of hits, identify the last update to the tag-group; and list new tags added since last review.

    Chicklet needs to integrate with the common link for a particular user-created tag-group. Would permit end-users to recombine tag-groups into new groups, or make tag groups smaller into more specific classes.

    Chicklet would need to integrate with spacing, syntax, and font choices end-user would use: To include, foreign language, spaces, capital letters, and other apostrophes and quotations that end-users may choose to use to define their tag-name.

    Users would be able to suggest, manage, or have Technorati-tags suggest “other similar tag groups” that are available for integration into the end-users Tag-group.

    Chicklet would integrate with tags related to specific blog content, permitting users to shut down their blog-centered comments, and have all blog-related comments organized into groups which end-users could define on their own. This would essentially allow end-users to create a block for spammers, and require all spammers [if they want to spam] to post their spam in their own blog, facilitating quick identification of spammers and problematic content.

    3. Feed Integration

    Integrate with the option to have Technorati tags fed to the end-use through a feed.

    4. User-recorded information on results

    Ability to allow end-users to use the chicklet, to quickly link to Technorati-tag-feeds which allow the end-user to record notes, provide ranks, and record the usefulness of the tag-content; and let the Technorati tools record those user-feed-comments to be incorporated into future-feed-searches.

    End-users would be able to establish own categories, weights that would adjust which tags get priority, highlighted, ignored, or integrated into parameters which Technorati-generated subscriptions would find and report.

    Ability for the chicklet to integrate with various display options, user-defined parameters adjusting feed-results into positions, locations, and templates the user-defines in an aggregator of their choosing.

    5. User generated bots

    Ability to integrate with end-user-controlled bots that search for feeds, and store the results in Technorati.

    These user-bots would have the ability to compare the outputs from a single source, identify which channels from that source are problematic; and identify by comparison which feeds would or would not work to timely provide information and results.

    Results of this bot-analysis would be shared with all Technorati users, giving alerts to others on the state of feeds, the various inconsistencies in the channels from a single source or platform, and make recommendations on which feeds to change, update, transition to, delete, or provide warnings to content providers of problems with those feeds.

    The bot would analyze the subscription with auto-tests, collect data, evaluate the quality for the response, and identify low quality sources. All the while, this information would be integrated into the end-users single Technorati code, adjust the searches, and make necessary updates and adjustments to the chicklet so that it remains a viable link to the quality Technorati Tags.

    The bot would also identify those locations storing personal information, have an auto-delete function to ensure that end-users personal information [identify theft stuff] was protected. Failures or problems with sites in timely responding and removing content would be disseminated to all Technorati-tag-code users to provide alerts that personal e-mails were needed, and notification made to Internet fraud alerts and law enforcement.

    Bot would send instructions to offending sites to delete personal information, remove subscriptions, take off e-mail lists, and update blog-links as needed to cut off ties with offending sites, and integrate with tools that create firewalls and protections from the blogs and Technorati tags from harmful bots, viruses, and other outside spy detection tools.

    6. Stand alone Technorati-based RSS browser

    Integrate with a browser-based Technorati-centered tagging-platform that allows end-users to manage, search for, and store both Technorati tags, and feeds related to these tags.

    7. Auto-publishing to blog

    Allow end-users to use the chicklet to provide results, which link to a list of Technorati tags; and the chicklet successfully integrates with an open box by the Technorati tag-list; users can input comments at this small box to create draft blog comments, then auto-publish from Technorati-tags to their individual blogs. Users also need to be able to re-arrange the Technorati-tag-outputs so that multiple tag-responses can be, with one comment, grouped into clusters for a combined blog-comment related to multiple Technorati-tag-hits.

    8. Scheduling Tag-reviews

    Allow end-users to record the time it takes to complete reviews, tasks, bogging, and research associated with Technorati tags. Allow for start and stop times of tasks; recording cumulative time. This time-data would then be stored in Technorati-tags.

    As users find similar tags, projects, or other tag-related content, end-users would be able to define the scope of tasks to accomplish, and Technorati tags would identify a block of time in the end-users calendar to accomplish this task.

    Users would have the ability to list all the Technorati-tag-related functions, see how long the cumulative tasks would take, and then slide the tasks along a calendar visually, similarly to how Technorati favelets slide along the desk to the browser.

    9. Feed timing

    This scheduling function would permit Technorati tag-users to slide tasks, reviews, and other tag-related research along a calendar so that feeds could be initiated to support the final due date or expected accomplishment.

    Users would be able to take the Technorati-Tags, cluster them into groups, define a milestone in time to conduct a review of that tag, while at the same time Technorati would then conduct a search for other results, produce a feed, and generate results in time for that scheduled milestone.

    10. Multiple parameters within a single Tachnorati tag code

    Users would want the chicklet to integrate with Technorati tag tools that could allow end-users to define multiple parameters to be integrated into a single Technorati-stored code.

    Parameters that might be embedded within this single code could include things as: Website, XML feed attributes and URI, blog name; name of content/blog article; contents; trackback; blogger identification name. This detailed information would be stored in member-tools, and integrated into feed-searches with the bot.

    Information within this tag-code would also outline user-defined parameters related to displaying feed content; size of boxes and templates used in Technorati-related templates and feed-displays; define parameters of radio boxes users use to critique and make comments related to the feed-results which would be incorporated into future Technorati-tag-related-feed-hunts.

    The multiple parameters would allow XML subscription information to be embedded with the tag; permit multi-searches of feeds and tags both within Technorati, and externally outside the platform. The parameters would be used to find, select, choose, prioritize, and ignore feeds that do or do not meet end-user requirements.

    Parameters would also be used to design the layout of the report. The parameters within the single code would provide results to the XZM feed on methods to prioritize, organize, list by either
  • [1] topic;
  • [2] sequential-time-order;
  • [3] newspaper format [with various feed-results placed on the report like a newspaper];
  • [4] program schedule whereby feeds were placed on a program-management-like schedule, and permitting end-users to move the feed-reports horizontally, vertically, or other directs to group, time, and adjust the expected reporting results of the Technorati feeds; or
  • [5] other categories or user-defined criteria the end-user may define within the Technorati platform

    The tool chicklet would integrate with Technorati-related tools which would hunt down public news releases, create a tracking system for corporate-public relations responses, and automatically delete those feeds from future searches when corporate CEOs and or public relations departments failed to provide timely response to end-user inquiries, comments, feedback, or recommendations for improvement.

    Chicklet would integrate with a system that would provide a list of issues, tags, other content which corporations are not timely responding to; specific statements or problems identified which would also integrate with the auto-delete function from both the Technorati tags and the Technorati-feeds.

    Deletions would be universal across all platforms and scrub the system of all data related to an ignored, deleted, or not longer useful feed.

    Chicklet would integrate with blog-search tools, bots, and URIs for feeds.

    Conclusion

    Technorati has tags. It remains to be seen what else they have in development. Get involved!



    Creative Commons License

    This work is licensed under a Creative Commons License.



    Executive Summary


    This is a user-end perspective on Technorati tags. This note outlines a number of potential features which Technorati may wish to explore. We have outlined a number of features which a Technorati Chicklet may need to integrate with.


    Overview

    This note outlines a number of potential programs Technorati may choose to look into when exploring Tag-integration tools.

    This note focuses on a chicklet and the various types of possible future capabilities, which this simple tool would need to integrate.

    This note may serve as a template for discussion among Technorati users and developers on future directions Technorati may embark with in .

    Discussion

    Technorati has tags. And it looks as though Technorati could very well have a number of other interesting projects in the works. It remains to be seen which of the below concepts are incorporated into Technorati design plans.

    Simply put, Technorati tagging is fast. Users can post the Technorati tag HTML and you’re all set. Feedburner has these chicklets for counters.

    I thought it would be interesting to see the same type of thing for Technorati. Perhaps some developers might want to work with Technorati to come up with a range of chicklets that people can use.

  • Technorati Tag – A tag button or chicklet to quickly spread tags

    Users might like a single chicklet to quickly post a Technorati Tag. When designing this chicklet I thought it would be useful to share the concept of the chicklet, and also share the vision of where Technorati Management may choose to take things.

    Again, this is purely speculation. But if developers want to know what end-users are thinking, this note might assist in this discussion. Also, it is hoped that the following list of ideas might also be a set of features that developers keep in mind when developing Technorati tools.

    Today’s tagging tools need to be made with the potential features that may be added. Clearly, these have not been developed, but the following might serve as a template of where things could go.

    Again, it remains up to Technorati Management to choose which features are ultimately incorporated into the Technorati platform.

    User Requirements

    Users may want to do more than simply post a Tag-line in their blog or host. They may choose to have some more interesting methods to post the link. One solution would be to combine the Tag-HTML with a chicklet.

    One analogy is the FeedBurner Checklist. It remains to be understood how Tagging catches on; with time, users may want more interesting options and more colorful features to promote their individual tags.

    In my view, it is in Technocrat’s interests to develop simple promotion tools for the individual user to post. These chicklets would not only promote the individual user’s tag, but quickly brand the tag as being associated with the Technorati family Just as the feed-buttons have caught on, if the Technorati-tag button is designed correctly with future requirements in mind, it could similarly prove to be an excellent promotional item not just for Technocrat’s tags, but also end-user projects.

    Desired Technorati chicklet features

    Here is a list of general user-end requirements associated with Technorati Promotional Tag. The list is merely notional.


    Technorati Tag Chicklet Concept

    A. Integrated

    Combined tag-and-chicklet image. The chicklet would include the Technorati HTML to link to the tags.

    B. Ease

    Simple copy and paste to either blog-content or template. The chicklet would be easy to copy and place.

    C. Adjustable

    Option to add embedded Tag Comments to say more about the Technorati Tag. Users could modify the chicklet to add comments.

    D. Flawless

    Successfully demonstrate the inputted tag works in the chicklet: Easily added, links to the correct tag. The chicklet would obviously need to work.

    E. Interesting

    Colorful, elegant design and colors consistent with Technorati color scheme. The chicklet would need to be interesting to look at reflecting well on both Technorati and the end-users choice in both the tag-subject, and in associating themselves with Technorati and the tags and add something to their hosts and sites they cannot currently get from other buttons.

    F. Flexible

    Chicklet design also needs to be flexible enough to accommodate future changes and additions to Technorati Tagging software tools for users, to include the following types of possible changes, upgrades or features.


    Purpose

    The rest of this note serves two purposes: To outline various hypothetical concepts which developers would ensure the chicklet integrates with; and also outline possible development efforts for Technorati.

    Even if the chicklet idea is abandoned, it is hoped that the list of tag-related concepts might be incorporated into other development efforts. Whether they are isolated to Technorati Tags, or more broadly to Technorati member tools remains to be seen.

    Potential Technorati Features

    This is a list of the possible features that Technorati could develop. These features are only speculation. Developers working on creating tag-related tools would have to consult Technorati management on the actual future directions.

    This list is independent of management and no way reflects management’s actual plans and directions. If you use this list, you do so at your own rise. Developers and end-users: Please consult Technorati management on their actual plans.

    1. User-defined displays of tag results

    A Technorati platform that allows users to screen, select, prioritize, and ignore other blog comments associated with the Technorati tag

    2. Foldering

    A Technorati tag support system that allows end-users to organize the tag-results into folders, clusters, or other groups that end-users can link-to-in-a-single-click, and grab all URLs for the tagged-blogs and quickly comment on a group of tags.

    Folder would permit end-users to know which tags had been added since the last visit; to zero-out all comment to a restart position of “No new tags”: and put at the front of the reading list those new tags added since last review.

    Integrate with a section called, “my tags” listing all tags the user creates, monitors, lists in blogs. Allow end-users to differentiate tags on the basis of author, use-location, blog-sue, subject matter.

    A member-tool that allows users to group tag-results into folders; list the number of hits, identify the last update to the tag-group; and list new tags added since last review.

    Chicklet needs to integrate with the common link for a particular user-created tag-group. Would permit end-users to recombine tag-groups into new groups, or make tag groups smaller into more specific classes.

    Chicklet would need to integrate with spacing, syntax, and font choices end-user would use: To include, foreign language, spaces, capital letters, and other apostrophes and quotations that end-users may choose to use to define their tag-name.

    Users would be able to suggest, manage, or have Technorati-tags suggest “other similar tag groups” that are available for integration into the end-users Tag-group.

    Chicklet would integrate with tags related to specific blog content, permitting users to shut down their blog-centered comments, and have all blog-related comments organized into groups which end-users could define on their own. This would essentially allow end-users to create a block for spammers, and require all spammers [if they want to spam] to post their spam in their own blog, facilitating quick identification of spammers and problematic content.

    3. Feed Integration

    Integrate with the option to have Technorati tags fed to the end-use through a feed.

    4. User-recorded information on results

    Ability to allow end-users to use the chicklet, to quickly link to Technorati-tag-feeds which allow the end-user to record notes, provide ranks, and record the usefulness of the tag-content; and let the Technorati tools record those user-feed-comments to be incorporated into future-feed-searches.

    End-users would be able to establish own categories, weights that would adjust which tags get priority, highlighted, ignored, or integrated into parameters which Technorati-generated subscriptions would find and report.

    Ability for the chicklet to integrate with various display options, user-defined parameters adjusting feed-results into positions, locations, and templates the user-defines in an aggregator of their choosing.

    5. User generated bots

    Ability to integrate with end-user-controlled bots that search for feeds, and store the results in Technorati.

    These user-bots would have the ability to compare the outputs from a single source, identify which channels from that source are problematic; and identify by comparison which feeds would or would not work to timely provide information and results.

    Results of this bot-analysis would be shared with all Technorati users, giving alerts to others on the state of feeds, the various inconsistencies in the channels from a single source or platform, and make recommendations on which feeds to change, update, transition to, delete, or provide warnings to content providers of problems with those feeds.

    The bot would analyze the subscription with auto-tests, collect data, evaluate the quality for the response, and identify low quality sources. All the while, this information would be integrated into the end-users single Technorati code, adjust the searches, and make necessary updates and adjustments to the chicklet so that it remains a viable link to the quality Technorati Tags.

    The bot would also identify those locations storing personal information, have an auto-delete function to ensure that end-users personal information [identify theft stuff] was protected. Failures or problems with sites in timely responding and removing content would be disseminated to all Technorati-tag-code users to provide alerts that personal e-mails were needed, and notification made to Internet fraud alerts and law enforcement.

    Bot would send instructions to offending sites to delete personal information, remove subscriptions, take off e-mail lists, and update blog-links as needed to cut off ties with offending sites, and integrate with tools that create firewalls and protections from the blogs and Technorati tags from harmful bots, viruses, and other outside spy detection tools.

    6. Stand alone Technorati-based RSS browser

    Integrate with a browser-based Technorati-centered tagging-platform that allows end-users to manage, search for, and store both Technorati tags, and feeds related to these tags.

    7. Auto-publishing to blog

    Allow end-users to use the chicklet to provide results, which link to a list of Technorati tags; and the chicklet successfully integrates with an open box by the Technorati tag-list; users can input comments at this small box to create draft blog comments, then auto-publish from Technorati-tags to their individual blogs. Users also need to be able to re-arrange the Technorati-tag-outputs so that multiple tag-responses can be, with one comment, grouped into clusters for a combined blog-comment related to multiple Technorati-tag-hits.

    8. Scheduling Tag-reviews

    Allow end-users to record the time it takes to complete reviews, tasks, bogging, and research associated with Technorati tags. Allow for start and stop times of tasks; recording cumulative time. This time-data would then be stored in Technorati-tags.

    As users find similar tags, projects, or other tag-related content, end-users would be able to define the scope of tasks to accomplish, and Technorati tags would identify a block of time in the end-users calendar to accomplish this task.

    Users would have the ability to list all the Technorati-tag-related functions, see how long the cumulative tasks would take, and then slide the tasks along a calendar visually, similarly to how Technorati favelets slide along the desk to the browser.

    9. Feed timing

    This scheduling function would permit Technorati tag-users to slide tasks, reviews, and other tag-related research along a calendar so that feeds could be initiated to support the final due date or expected accomplishment.

    Users would be able to take the Technorati-Tags, cluster them into groups, define a milestone in time to conduct a review of that tag, while at the same time Technorati would then conduct a search for other results, produce a feed, and generate results in time for that scheduled milestone.

    10. Multiple parameters within a single Tachnorati tag code

    Users would want the chicklet to integrate with Technorati tag tools that could allow end-users to define multiple parameters to be integrated into a single Technorati-stored code.

    Parameters that might be embedded within this single code could include things as: Website, XML feed attributes and URI, blog name; name of content/blog article; contents; trackback; blogger identification name. This detailed information would be stored in member-tools, and integrated into feed-searches with the bot.

    Information within this tag-code would also outline user-defined parameters related to displaying feed content; size of boxes and templates used in Technorati-related templates and feed-displays; define parameters of radio boxes users use to critique and make comments related to the feed-results which would be incorporated into future Technorati-tag-related-feed-hunts.

    The multiple parameters would allow XML subscription information to be embedded with the tag; permit multi-searches of feeds and tags both within Technorati, and externally outside the platform. The parameters would be used to find, select, choose, prioritize, and ignore feeds that do or do not meet end-user requirements.

    Parameters would also be used to design the layout of the report. The parameters within the single code would provide results to the XZM feed on methods to prioritize, organize, list by either
  • [1] topic;
  • [2] sequential-time-order;
  • [3] newspaper format [with various feed-results placed on the report like a newspaper];
  • [4] program schedule whereby feeds were placed on a program-management-like schedule, and permitting end-users to move the feed-reports horizontally, vertically, or other directs to group, time, and adjust the expected reporting results of the Technorati feeds; or
  • [5] other categories or user-defined criteria the end-user may define within the Technorati platform

    The tool chicklet would integrate with Technorati-related tools which would hunt down public news releases, create a tracking system for corporate-public relations responses, and automatically delete those feeds from future searches when corporate CEOs and or public relations departments failed to provide timely response to end-user inquiries, comments, feedback, or recommendations for improvement.

    Chicklet would integrate with a system that would provide a list of issues, tags, other content which corporations are not timely responding to; specific statements or problems identified which would also integrate with the auto-delete function from both the Technorati tags and the Technorati-feeds.

    Deletions would be universal across all platforms and scrub the system of all data related to an ignored, deleted, or not longer useful feed.

    Chicklet would integrate with blog-search tools, bots, and URIs for feeds.

    Conclusion

    Technorati has tags. It remains to be seen what else they have in development. Get involved!


    -->

    Creative Commons License

    This work is licensed under a Creative Commons License.



    Executive Summary


    This is a user-end perspective on Technorati tags. This note outlines a number of potential features which Technorati may wish to explore. We have outlined a number of features which a Technorati Chicklet may need to integrate with.


    Overview

    This note outlines a number of potential programs Technorati may choose to look into when exploring Tag-integration tools.

    This note focuses on a chicklet and the various types of possible future capabilities, which this simple tool would need to integrate.

    This note may serve as a template for discussion among Technorati users and developers on future directions Technorati may embark with in .

    Discussion

    Technorati has tags. And it looks as though Technorati could very well have a number of other interesting projects in the works. It remains to be seen which of the below concepts are incorporated into Technorati design plans.

    Simply put, Technorati tagging is fast. Users can post the Technorati tag HTML and you’re all set. Feedburner has these chicklets for counters.

    I thought it would be interesting to see the same type of thing for Technorati. Perhaps some developers might want to work with Technorati to come up with a range of chicklets that people can use.

  • Technorati Tag – A tag button or chicklet to quickly spread tags

    Users might like a single chicklet to quickly post a Technorati Tag. When designing this chicklet I thought it would be useful to share the concept of the chicklet, and also share the vision of where Technorati Management may choose to take things.

    Again, this is purely speculation. But if developers want to know what end-users are thinking, this note might assist in this discussion. Also, it is hoped that the following list of ideas might also be a set of features that developers keep in mind when developing Technorati tools.

    Today’s tagging tools need to be made with the potential features that may be added. Clearly, these have not been developed, but the following might serve as a template of where things could go.

    Again, it remains up to Technorati Management to choose which features are ultimately incorporated into the Technorati platform.

    User Requirements

    Users may want to do more than simply post a Tag-line in their blog or host. They may choose to have some more interesting methods to post the link. One solution would be to combine the Tag-HTML with a chicklet.

    One analogy is the FeedBurner Checklist. It remains to be understood how Tagging catches on; with time, users may want more interesting options and more colorful features to promote their individual tags.

    In my view, it is in Technocrat’s interests to develop simple promotion tools for the individual user to post. These chicklets would not only promote the individual user’s tag, but quickly brand the tag as being associated with the Technorati family Just as the feed-buttons have caught on, if the Technorati-tag button is designed correctly with future requirements in mind, it could similarly prove to be an excellent promotional item not just for Technocrat’s tags, but also end-user projects.

    Desired Technorati chicklet features

    Here is a list of general user-end requirements associated with Technorati Promotional Tag. The list is merely notional.


    Technorati Tag Chicklet Concept

    A. Integrated

    Combined tag-and-chicklet image. The chicklet would include the Technorati HTML to link to the tags.

    B. Ease

    Simple copy and paste to either blog-content or template. The chicklet would be easy to copy and place.

    C. Adjustable

    Option to add embedded Tag Comments to say more about the Technorati Tag. Users could modify the chicklet to add comments.

    D. Flawless

    Successfully demonstrate the inputted tag works in the chicklet: Easily added, links to the correct tag. The chicklet would obviously need to work.

    E. Interesting

    Colorful, elegant design and colors consistent with Technorati color scheme. The chicklet would need to be interesting to look at reflecting well on both Technorati and the end-users choice in both the tag-subject, and in associating themselves with Technorati and the tags and add something to their hosts and sites they cannot currently get from other buttons.

    F. Flexible

    Chicklet design also needs to be flexible enough to accommodate future changes and additions to Technorati Tagging software tools for users, to include the following types of possible changes, upgrades or features.


    Purpose

    The rest of this note serves two purposes: To outline various hypothetical concepts which developers would ensure the chicklet integrates with; and also outline possible development efforts for Technorati.

    Even if the chicklet idea is abandoned, it is hoped that the list of tag-related concepts might be incorporated into other development efforts. Whether they are isolated to Technorati Tags, or more broadly to Technorati member tools remains to be seen.

    Potential Technorati Features

    This is a list of the possible features that Technorati could develop. These features are only speculation. Developers working on creating tag-related tools would have to consult Technorati management on the actual future directions.

    This list is independent of management and no way reflects management’s actual plans and directions. If you use this list, you do so at your own rise. Developers and end-users: Please consult Technorati management on their actual plans.

    1. User-defined displays of tag results

    A Technorati platform that allows users to screen, select, prioritize, and ignore other blog comments associated with the Technorati tag

    2. Foldering

    A Technorati tag support system that allows end-users to organize the tag-results into folders, clusters, or other groups that end-users can link-to-in-a-single-click, and grab all URLs for the tagged-blogs and quickly comment on a group of tags.

    Folder would permit end-users to know which tags had been added since the last visit; to zero-out all comment to a restart position of “No new tags”: and put at the front of the reading list those new tags added since last review.

    Integrate with a section called, “my tags” listing all tags the user creates, monitors, lists in blogs. Allow end-users to differentiate tags on the basis of author, use-location, blog-sue, subject matter.

    A member-tool that allows users to group tag-results into folders; list the number of hits, identify the last update to the tag-group; and list new tags added since last review.

    Chicklet needs to integrate with the common link for a particular user-created tag-group. Would permit end-users to recombine tag-groups into new groups, or make tag groups smaller into more specific classes.

    Chicklet would need to integrate with spacing, syntax, and font choices end-user would use: To include, foreign language, spaces, capital letters, and other apostrophes and quotations that end-users may choose to use to define their tag-name.

    Users would be able to suggest, manage, or have Technorati-tags suggest “other similar tag groups” that are available for integration into the end-users Tag-group.

    Chicklet would integrate with tags related to specific blog content, permitting users to shut down their blog-centered comments, and have all blog-related comments organized into groups which end-users could define on their own. This would essentially allow end-users to create a block for spammers, and require all spammers [if they want to spam] to post their spam in their own blog, facilitating quick identification of spammers and problematic content.

    3. Feed Integration

    Integrate with the option to have Technorati tags fed to the end-use through a feed.

    4. User-recorded information on results

    Ability to allow end-users to use the chicklet, to quickly link to Technorati-tag-feeds which allow the end-user to record notes, provide ranks, and record the usefulness of the tag-content; and let the Technorati tools record those user-feed-comments to be incorporated into future-feed-searches.

    End-users would be able to establish own categories, weights that would adjust which tags get priority, highlighted, ignored, or integrated into parameters which Technorati-generated subscriptions would find and report.

    Ability for the chicklet to integrate with various display options, user-defined parameters adjusting feed-results into positions, locations, and templates the user-defines in an aggregator of their choosing.

    5. User generated bots

    Ability to integrate with end-user-controlled bots that search for feeds, and store the results in Technorati.

    These user-bots would have the ability to compare the outputs from a single source, identify which channels from that source are problematic; and identify by comparison which feeds would or would not work to timely provide information and results.

    Results of this bot-analysis would be shared with all Technorati users, giving alerts to others on the state of feeds, the various inconsistencies in the channels from a single source or platform, and make recommendations on which feeds to change, update, transition to, delete, or provide warnings to content providers of problems with those feeds.

    The bot would analyze the subscription with auto-tests, collect data, evaluate the quality for the response, and identify low quality sources. All the while, this information would be integrated into the end-users single Technorati code, adjust the searches, and make necessary updates and adjustments to the chicklet so that it remains a viable link to the quality Technorati Tags.

    The bot would also identify those locations storing personal information, have an auto-delete function to ensure that end-users personal information [identify theft stuff] was protected. Failures or problems with sites in timely responding and removing content would be disseminated to all Technorati-tag-code users to provide alerts that personal e-mails were needed, and notification made to Internet fraud alerts and law enforcement.

    Bot would send instructions to offending sites to delete personal information, remove subscriptions, take off e-mail lists, and update blog-links as needed to cut off ties with offending sites, and integrate with tools that create firewalls and protections from the blogs and Technorati tags from harmful bots, viruses, and other outside spy detection tools.

    6. Stand alone Technorati-based RSS browser

    Integrate with a browser-based Technorati-centered tagging-platform that allows end-users to manage, search for, and store both Technorati tags, and feeds related to these tags.

    7. Auto-publishing to blog

    Allow end-users to use the chicklet to provide results, which link to a list of Technorati tags; and the chicklet successfully integrates with an open box by the Technorati tag-list; users can input comments at this small box to create draft blog comments, then auto-publish from Technorati-tags to their individual blogs. Users also need to be able to re-arrange the Technorati-tag-outputs so that multiple tag-responses can be, with one comment, grouped into clusters for a combined blog-comment related to multiple Technorati-tag-hits.

    8. Scheduling Tag-reviews

    Allow end-users to record the time it takes to complete reviews, tasks, bogging, and research associated with Technorati tags. Allow for start and stop times of tasks; recording cumulative time. This time-data would then be stored in Technorati-tags.

    As users find similar tags, projects, or other tag-related content, end-users would be able to define the scope of tasks to accomplish, and Technorati tags would identify a block of time in the end-users calendar to accomplish this task.

    Users would have the ability to list all the Technorati-tag-related functions, see how long the cumulative tasks would take, and then slide the tasks along a calendar visually, similarly to how Technorati favelets slide along the desk to the browser.

    9. Feed timing

    This scheduling function would permit Technorati tag-users to slide tasks, reviews, and other tag-related research along a calendar so that feeds could be initiated to support the final due date or expected accomplishment.

    Users would be able to take the Technorati-Tags, cluster them into groups, define a milestone in time to conduct a review of that tag, while at the same time Technorati would then conduct a search for other results, produce a feed, and generate results in time for that scheduled milestone.

    10. Multiple parameters within a single Tachnorati tag code

    Users would want the chicklet to integrate with Technorati tag tools that could allow end-users to define multiple parameters to be integrated into a single Technorati-stored code.

    Parameters that might be embedded within this single code could include things as: Website, XML feed attributes and URI, blog name; name of content/blog article; contents; trackback; blogger identification name. This detailed information would be stored in member-tools, and integrated into feed-searches with the bot.

    Information within this tag-code would also outline user-defined parameters related to displaying feed content; size of boxes and templates used in Technorati-related templates and feed-displays; define parameters of radio boxes users use to critique and make comments related to the feed-results which would be incorporated into future Technorati-tag-related-feed-hunts.

    The multiple parameters would allow XML subscription information to be embedded with the tag; permit multi-searches of feeds and tags both within Technorati, and externally outside the platform. The parameters would be used to find, select, choose, prioritize, and ignore feeds that do or do not meet end-user requirements.

    Parameters would also be used to design the layout of the report. The parameters within the single code would provide results to the XZM feed on methods to prioritize, organize, list by either
  • [1] topic;
  • [2] sequential-time-order;
  • [3] newspaper format [with various feed-results placed on the report like a newspaper];
  • [4] program schedule whereby feeds were placed on a program-management-like schedule, and permitting end-users to move the feed-reports horizontally, vertically, or other directs to group, time, and adjust the expected reporting results of the Technorati feeds; or
  • [5] other categories or user-defined criteria the end-user may define within the Technorati platform

    The tool chicklet would integrate with Technorati-related tools which would hunt down public news releases, create a tracking system for corporate-public relations responses, and automatically delete those feeds from future searches when corporate CEOs and or public relations departments failed to provide timely response to end-user inquiries, comments, feedback, or recommendations for improvement.

    Chicklet would integrate with a system that would provide a list of issues, tags, other content which corporations are not timely responding to; specific statements or problems identified which would also integrate with the auto-delete function from both the Technorati tags and the Technorati-feeds.

    Deletions would be universal across all platforms and scrub the system of all data related to an ignored, deleted, or not longer useful feed.

    Chicklet would integrate with blog-search tools, bots, and URIs for feeds.

    Conclusion

    Technorati has tags. It remains to be seen what else they have in development. Get involved!



  • Creative Commons License

    This work is licensed under a Creative Commons License.



    Executive Summary


    This is a user-end perspective on Technorati tags. This note outlines a number of potential features which Technorati may wish to explore. We have outlined a number of features which a Technorati Chicklet may need to integrate with.


    Overview

    This note outlines a number of potential programs Technorati may choose to look into when exploring Tag-integration tools.

    This note focuses on a chicklet and the various types of possible future capabilities, which this simple tool would need to integrate.

    This note may serve as a template for discussion among Technorati users and developers on future directions Technorati may embark with in .

    Discussion

    Technorati has tags. And it looks as though Technorati could very well have a number of other interesting projects in the works. It remains to be seen which of the below concepts are incorporated into Technorati design plans.

    Simply put, Technorati tagging is fast. Users can post the Technorati tag HTML and you’re all set. Feedburner has these chicklets for counters.

    I thought it would be interesting to see the same type of thing for Technorati. Perhaps some developers might want to work with Technorati to come up with a range of chicklets that people can use.

  • Technorati Tag – A tag button or chicklet to quickly spread tags

    Users might like a single chicklet to quickly post a Technorati Tag. When designing this chicklet I thought it would be useful to share the concept of the chicklet, and also share the vision of where Technorati Management may choose to take things.

    Again, this is purely speculation. But if developers want to know what end-users are thinking, this note might assist in this discussion. Also, it is hoped that the following list of ideas might also be a set of features that developers keep in mind when developing Technorati tools.

    Today’s tagging tools need to be made with the potential features that may be added. Clearly, these have not been developed, but the following might serve as a template of where things could go.

    Again, it remains up to Technorati Management to choose which features are ultimately incorporated into the Technorati platform.

    User Requirements

    Users may want to do more than simply post a Tag-line in their blog or host. They may choose to have some more interesting methods to post the link. One solution would be to combine the Tag-HTML with a chicklet.

    One analogy is the FeedBurner Checklist. It remains to be understood how Tagging catches on; with time, users may want more interesting options and more colorful features to promote their individual tags.

    In my view, it is in Technocrat’s interests to develop simple promotion tools for the individual user to post. These chicklets would not only promote the individual user’s tag, but quickly brand the tag as being associated with the Technorati family Just as the feed-buttons have caught on, if the Technorati-tag button is designed correctly with future requirements in mind, it could similarly prove to be an excellent promotional item not just for Technocrat’s tags, but also end-user projects.

    Desired Technorati chicklet features

    Here is a list of general user-end requirements associated with Technorati Promotional Tag. The list is merely notional.


    Technorati Tag Chicklet Concept

    A. Integrated

    Combined tag-and-chicklet image. The chicklet would include the Technorati HTML to link to the tags.

    B. Ease

    Simple copy and paste to either blog-content or template. The chicklet would be easy to copy and place.

    C. Adjustable

    Option to add embedded Tag Comments to say more about the Technorati Tag. Users could modify the chicklet to add comments.

    D. Flawless

    Successfully demonstrate the inputted tag works in the chicklet: Easily added, links to the correct tag. The chicklet would obviously need to work.

    E. Interesting

    Colorful, elegant design and colors consistent with Technorati color scheme. The chicklet would need to be interesting to look at reflecting well on both Technorati and the end-users choice in both the tag-subject, and in associating themselves with Technorati and the tags and add something to their hosts and sites they cannot currently get from other buttons.

    F. Flexible

    Chicklet design also needs to be flexible enough to accommodate future changes and additions to Technorati Tagging software tools for users, to include the following types of possible changes, upgrades or features.


    Purpose

    The rest of this note serves two purposes: To outline various hypothetical concepts which developers would ensure the chicklet integrates with; and also outline possible development efforts for Technorati.

    Even if the chicklet idea is abandoned, it is hoped that the list of tag-related concepts might be incorporated into other development efforts. Whether they are isolated to Technorati Tags, or more broadly to Technorati member tools remains to be seen.

    Potential Technorati Features

    This is a list of the possible features that Technorati could develop. These features are only speculation. Developers working on creating tag-related tools would have to consult Technorati management on the actual future directions.

    This list is independent of management and no way reflects management’s actual plans and directions. If you use this list, you do so at your own rise. Developers and end-users: Please consult Technorati management on their actual plans.

    1. User-defined displays of tag results

    A Technorati platform that allows users to screen, select, prioritize, and ignore other blog comments associated with the Technorati tag

    2. Foldering

    A Technorati tag support system that allows end-users to organize the tag-results into folders, clusters, or other groups that end-users can link-to-in-a-single-click, and grab all URLs for the tagged-blogs and quickly comment on a group of tags.

    Folder would permit end-users to know which tags had been added since the last visit; to zero-out all comment to a restart position of “No new tags”: and put at the front of the reading list those new tags added since last review.

    Integrate with a section called, “my tags” listing all tags the user creates, monitors, lists in blogs. Allow end-users to differentiate tags on the basis of author, use-location, blog-sue, subject matter.

    A member-tool that allows users to group tag-results into folders; list the number of hits, identify the last update to the tag-group; and list new tags added since last review.

    Chicklet needs to integrate with the common link for a particular user-created tag-group. Would permit end-users to recombine tag-groups into new groups, or make tag groups smaller into more specific classes.

    Chicklet would need to integrate with spacing, syntax, and font choices end-user would use: To include, foreign language, spaces, capital letters, and other apostrophes and quotations that end-users may choose to use to define their tag-name.

    Users would be able to suggest, manage, or have Technorati-tags suggest “other similar tag groups” that are available for integration into the end-users Tag-group.

    Chicklet would integrate with tags related to specific blog content, permitting users to shut down their blog-centered comments, and have all blog-related comments organized into groups which end-users could define on their own. This would essentially allow end-users to create a block for spammers, and require all spammers [if they want to spam] to post their spam in their own blog, facilitating quick identification of spammers and problematic content.

    3. Feed Integration

    Integrate with the option to have Technorati tags fed to the end-use through a feed.

    4. User-recorded information on results

    Ability to allow end-users to use the chicklet, to quickly link to Technorati-tag-feeds which allow the end-user to record notes, provide ranks, and record the usefulness of the tag-content; and let the Technorati tools record those user-feed-comments to be incorporated into future-feed-searches.

    End-users would be able to establish own categories, weights that would adjust which tags get priority, highlighted, ignored, or integrated into parameters which Technorati-generated subscriptions would find and report.

    Ability for the chicklet to integrate with various display options, user-defined parameters adjusting feed-results into positions, locations, and templates the user-defines in an aggregator of their choosing.

    5. User generated bots

    Ability to integrate with end-user-controlled bots that search for feeds, and store the results in Technorati.

    These user-bots would have the ability to compare the outputs from a single source, identify which channels from that source are problematic; and identify by comparison which feeds would or would not work to timely provide information and results.

    Results of this bot-analysis would be shared with all Technorati users, giving alerts to others on the state of feeds, the various inconsistencies in the channels from a single source or platform, and make recommendations on which feeds to change, update, transition to, delete, or provide warnings to content providers of problems with those feeds.

    The bot would analyze the subscription with auto-tests, collect data, evaluate the quality for the response, and identify low quality sources. All the while, this information would be integrated into the end-users single Technorati code, adjust the searches, and make necessary updates and adjustments to the chicklet so that it remains a viable link to the quality Technorati Tags.

    The bot would also identify those locations storing personal information, have an auto-delete function to ensure that end-users personal information [identify theft stuff] was protected. Failures or problems with sites in timely responding and removing content would be disseminated to all Technorati-tag-code users to provide alerts that personal e-mails were needed, and notification made to Internet fraud alerts and law enforcement.

    Bot would send instructions to offending sites to delete personal information, remove subscriptions, take off e-mail lists, and update blog-links as needed to cut off ties with offending sites, and integrate with tools that create firewalls and protections from the blogs and Technorati tags from harmful bots, viruses, and other outside spy detection tools.

    6. Stand alone Technorati-based RSS browser

    Integrate with a browser-based Technorati-centered tagging-platform that allows end-users to manage, search for, and store both Technorati tags, and feeds related to these tags.

    7. Auto-publishing to blog

    Allow end-users to use the chicklet to provide results, which link to a list of Technorati tags; and the chicklet successfully integrates with an open box by the Technorati tag-list; users can input comments at this small box to create draft blog comments, then auto-publish from Technorati-tags to their individual blogs. Users also need to be able to re-arrange the Technorati-tag-outputs so that multiple tag-responses can be, with one comment, grouped into clusters for a combined blog-comment related to multiple Technorati-tag-hits.

    8. Scheduling Tag-reviews

    Allow end-users to record the time it takes to complete reviews, tasks, bogging, and research associated with Technorati tags. Allow for start and stop times of tasks; recording cumulative time. This time-data would then be stored in Technorati-tags.

    As users find similar tags, projects, or other tag-related content, end-users would be able to define the scope of tasks to accomplish, and Technorati tags would identify a block of time in the end-users calendar to accomplish this task.

    Users would have the ability to list all the Technorati-tag-related functions, see how long the cumulative tasks would take, and then slide the tasks along a calendar visually, similarly to how Technorati favelets slide along the desk to the browser.

    9. Feed timing

    This scheduling function would permit Technorati tag-users to slide tasks, reviews, and other tag-related research along a calendar so that feeds could be initiated to support the final due date or expected accomplishment.

    Users would be able to take the Technorati-Tags, cluster them into groups, define a milestone in time to conduct a review of that tag, while at the same time Technorati would then conduct a search for other results, produce a feed, and generate results in time for that scheduled milestone.

    10. Multiple parameters within a single Tachnorati tag code

    Users would want the chicklet to integrate with Technorati tag tools that could allow end-users to define multiple parameters to be integrated into a single Technorati-stored code.

    Parameters that might be embedded within this single code could include things as: Website, XML feed attributes and URI, blog name; name of content/blog article; contents; trackback; blogger identification name. This detailed information would be stored in member-tools, and integrated into feed-searches with the bot.

    Information within this tag-code would also outline user-defined parameters related to displaying feed content; size of boxes and templates used in Technorati-related templates and feed-displays; define parameters of radio boxes users use to critique and make comments related to the feed-results which would be incorporated into future Technorati-tag-related-feed-hunts.

    The multiple parameters would allow XML subscription information to be embedded with the tag; permit multi-searches of feeds and tags both within Technorati, and externally outside the platform. The parameters would be used to find, select, choose, prioritize, and ignore feeds that do or do not meet end-user requirements.

    Parameters would also be used to design the layout of the report. The parameters within the single code would provide results to the XZM feed on methods to prioritize, organize, list by either
  • [1] topic;
  • [2] sequential-time-order;
  • [3] newspaper format [with various feed-results placed on the report like a newspaper];
  • [4] program schedule whereby feeds were placed on a program-management-like schedule, and permitting end-users to move the feed-reports horizontally, vertically, or other directs to group, time, and adjust the expected reporting results of the Technorati feeds; or
  • [5] other categories or user-defined criteria the end-user may define within the Technorati platform

    The tool chicklet would integrate with Technorati-related tools which would hunt down public news releases, create a tracking system for corporate-public relations responses, and automatically delete those feeds from future searches when corporate CEOs and or public relations departments failed to provide timely response to end-user inquiries, comments, feedback, or recommendations for improvement.

    Chicklet would integrate with a system that would provide a list of issues, tags, other content which corporations are not timely responding to; specific statements or problems identified which would also integrate with the auto-delete function from both the Technorati tags and the Technorati-feeds.

    Deletions would be universal across all platforms and scrub the system of all data related to an ignored, deleted, or not longer useful feed.

    Chicklet would integrate with blog-search tools, bots, and URIs for feeds.

    Conclusion

    Technorati has tags. It remains to be seen what else they have in development. Get involved!


    " />
  • << Home