In response to my tagging announcement, Marty McGuire writes:
This could be a use case for tag-reply posts!
Brid.gy supports this for tagging people in Flickr posts, as well as adding labels to GitHub issues.
(wow I really have got to write some sort of reply-to post importer… hand-converting that to Markdown was way more work than it should have been!)
I’m not quite sure I understand the use case that’s being called for, here. Publ tags are “tags” in the Tumblr sense, where they’re used to filter and organize posts, like being able to limit things to rants or whatever; I get the feeling that this is confusion over multiple uses of the word “tag,” like how on Twitter/Facebook/Flickr/etc. “tagging” means signaling to someone that they should read a post (akin to “Tag! You’re it!”). Think Technorati tags from way back when, or Atom categories, which are most akin to hashtags on Twitter and Facebook.
I think a tag-as-in-notification thing would be implemented in Publ the same way I implement in-reply-to and so on – I have a corresponding header in the entry file and my template generates an invisible <a class="u-in-reply-to" href="..."> in the post body. The relevant bit in my entry template is:
{% for type in ('like-of', 'in-reply-to', 'repost-of', 'bookmark-of', 'mention-of', 'rsvp') %}
{% for link in entry.get_all(type) %}
<a href="{{link}}" class="u-{{type}}"></a>
{% endfor %}
{% endfor %}
So in that sense Publ already supports that at the template level; I can simply add tag-of to the list of microformat types. Or am I completely misunderstanding what is being suggested?