right now it's the first n words of e-content, ellipsized. when it's ellipsized, http://webmention.herokuapp.com/ sees that it's different from e-content, thinks it's meaningful, and shows it alongside the e-content, resulting in duplication like on http://www.kevinmarks.com/xoxofest2014a.html . irc discussion here.
options:
- don't ellipsize; copy full e-content into p-name. not ideal for fb and g+ since they can be arbitrarily long, but could work for twitter.
- drop p-name for notes and replies entirely. not great because mf2 parsers are then supposed to auto-generate p-name...which would be fine, but based on this example, they populate it with the entire h-entry text, instead of just e-content? that seems wrong...?
background in http://indiewebcamp.com/comments-presentation#How_to_display and http://microformats.org/wiki/h-entry#p-name_of_a_note . cc @voxpelli @kylewm, also @kevinmarks @tantek @barnabywalters for mf2 guidance.
right now it's the first n words of e-content, ellipsized. when it's ellipsized, http://webmention.herokuapp.com/ sees that it's different from e-content, thinks it's meaningful, and shows it alongside the e-content, resulting in duplication like on http://www.kevinmarks.com/xoxofest2014a.html . irc discussion here.
options:
background in http://indiewebcamp.com/comments-presentation#How_to_display and http://microformats.org/wiki/h-entry#p-name_of_a_note . cc @voxpelli @kylewm, also @kevinmarks @tantek @barnabywalters for mf2 guidance.