From IndieWeb
Jump to: navigation, search

A tag reply is a special edit response to a post that tags that post with one or more tags, including possibly (or only) person-tags.


Tagging others' content is a very common silo UX and practice. By using your own site to tag others' content, you "ownyourtags" even if/when the silos die.

While most commonly used to tag photos (e.g. tagging other people’s photos on Flickr), another use of tag replies is to add labels to GitHub issues, as part of owning all your own issue tracking and interacting.

IndieWeb Examples

. None so far

IndieWeb Interest


Tantek Çelik has been wanting this feature for a while and has listed it among the features he is working on in Falcon, in particular to use his site for issue tracking and discussion in general.

See also #Brainstorming below for thoughts on the visual appearance of tag-reply posts, and the markup to distinguish them and make the recognizable by services to POSSE them.



Bridgy publish POSSEing tag-of posts:

Silo Examples


Flickr allows people to tag other people's photos, both with plain text tags, and person-tags.

The (person-)tag shows up immediately, there is no pending/approval/moderation.

By default, only your friends on Flickr can (person-)tag your photos. You can change that permission to allow everyone or no one.

Sometime in 2000s-2014(?), if you hovered over a tag on a photo/video permalink page, it would show an HTML popup indicating who added it and when.

(screenshot needed)

Flickr backfeed

If you POSSE your photos to Flickr, you should also backfeed the tags (including person-tags) added to the Flickr copy of your photo as tag-replies to your own site.

Bridgy Backfeed feature requests:

... other approaches?


Facebook allows people to person-tag other's photos.

If you hover over a person-tag on a photo/video, it shows an HTML popup card of that person, with small text at the top saying "Tagged by fullname" where fullname is the name of the person that added the tag.

(screenshot needed).

Facebook notifications

Facebook provides explicit notifications for person-tags, both:

  • When someone person-tags you in a photo
    • ... their photo:
      • (icon)(user) added a photo of you. (photo-thumbnail) / (datetime)
    • ... someone else's: (screenshot needed)
      • (icon)(user) tagged a photo of you. (photo-thumbnail) / (datetime)
  • When someone adds a person-tag to one of your photos (when you receive a person-tag reply)

(screenshots needed)

Facebook POSSE

When you post a person-tag reply, and (at least one of) your in-reply-to URLs is a Facebook post permalink (likely a photo), you should automatically POSSE your person-tag reply to that FB post.

Bridgy Publish feature request:

Facebook backfeed

If you POSSE your photos to Facebook, you should also backfeed the person-tags added to the FB copy of your photo as tag-replies to your own site.

Bridgy Backfeed Feature Requests:

  • ... other approaches?


Instagram does not have any ability for anyone but the author to add person-tags or hashtags.

Instagram backfeed

Still, it would be useful even in the case of the original author adding person-tags or hashtags to a POSSE copy on Instagram to backfeed them to the original.

Since author hashtags are implicit by including them inline in the caption or comments on the photo, if you are backfeeding comments and processing the hashtags in the comments as tag-replies, you should get this functionality automatically.

Related Bridgy Feature requests:


GitHub has the ability to add labels to issues, which are essentially tags.

Adding (or removing) labels from an issue causes a visible "action" among the comments on the issue (e.g. snarfed adding 'publish' label, thus showing a visible "tag-reply" at least inline (note: comments on issues also only show-up inline on an issue, they don't have non-fragment permalinks of their own).


Bridgy Publish supports POSSEing tag-of posts to issues!

GitHub backfeed

Bridgy has an open issue (feature request) to support backfeeding the addition of labels to issues, as tag-of posts:


Until implemented (published, webmentioned, received, incorporated into an original post), these are brainstorming How to examples.

text only design

Based on GitHub's:

which makes sense in the context of the issue being altered, a tag-of post could be summarized as:

🏷 added label ”Agenda f2f“ to issue 5 of GitHub project “coolproj” 5 hours ago

or similarly for removal:

🏷 removed label ”Agenda f2f“ from issue 5 of GitHub project “coolproj” 5 hours ago

How to post a tag-reply

How to mark-up a tag reply, e.g. with the tag "indieweb" Inside a plain h-entry, use:

🏷 added label ”indieweb“ to issue 5 of Git project “proj2”

How to mark-up a tag reply, e.g. with the tags "indieweb" and "indiewebcamp":

🏷 added labels ”indieweb“ & ”indiewebcamp“ to issue 5 of Git project “proj2”

And then send a webmention from your tag reply permalink to http://git.example.com/user1/proj2/issues/5.

Doing so will tag that issue with the tags "indieweb" and "indiewebcamp".

Working on this:

tag and fallback

To tag some other post, and automatically provide synthetic fallback reply text to display for sites that support receiving reply posts but not tag-of posts, use the u-tag-of markup, and a u-in-reply-to plus p-summary for the fallback text (and explicitly no e-content)


  • summary text: "🏷 Tantek added labels indieweb & indiewebcamp to issue 5 of GitHub project “coolproj”"


  • Something shows up instead of nothing, on sites that at least show comments
  • Fallback as new technology discovery mechanism. The "third person" verbiage implies that there may be more markup for the specific type of response that the receiving site / person may want to investigate and support!

Building on prior example:

🏷 Tantek added labels ”indieweb“ & ”indiewebcamp“ to issue 5 of Git project “proj2”

And for a person-tag, see the person tag reply brainstorm's second markup example which just adds the necessary p-summary markup.

person tag reply

To tag someone in someone else’s photo, post a person tag reply such as this, and send webmentions to all the links.

 Bea and 

As a result of the webmentions:

  • Dawn's photo post will be notified that Amber has asked to tag Bea and Crystal in the photo.
  • IF Dawn accepts the person-tags on the photo THEN
    • Bea and Crystal will be notified that Amber tagged them in a photo.

Working on this:

With explicit fallback markup p-summary to generate summary text for receivers that don't recognize u-tag-of (yet)

  • "Amber tagged Bea and Crystal in Dawn’s photo of Bea and Crystal"

 Bea and 

person tag multiple URLs

Similar to person-tags in posts themselves, a person-tag reply should be able to embed an h-card with multiple URLs, e.g. a primary URL to the person's personal site, and URLs for their identity-elsewhere.

See person-tag#Tantek examples for person-tag h-cards with multiple URLs.

(needs markup example, e.g. above markup but with h-cards that have multiple URLs per person)

Abandoned Brainstorming

Brainstorming that’s been rejected or found to not work / make sense. Kept here for historical value (especially if the idea comes up again).

tag and comment

Alternatively, does this use-case make sense? tl;dr: It does not.

Tag some other post, and comment on it at the same time?

2019-007 answer: No. Based on Bridgy #832 discussion, such a multi-interaction response is both an unnecessary complexification of UX (users understand tagging and commenting as separate actions, thus posts, not as one action/post), and consuming code logic.

Inside your usual h-entry, use:


This is a great post about the indieweb and indiewebcamp.

And then send a webmention from your tag reply permalink to http://a.example.com/postpermalink37.

Doing so will tag that postpermalink37 with the tags "indieweb" and "indiewebcamp", as well as make the comment
This is a great post about the indieweb and indiewebcamp

Related Bridgy issue:

See Also