handle webmention sources with multiple types (ie mf2 classes)

[snarfed]

example: https://snarfed.org/2015-09-29_known-announces-dreamhost-as-exclusive-web-hosting-sponsor both likes and replies to http://stream.withknown.com/2015/known-announces-dreamhost-as-exclusive-web-hosting-sponsor , but that page only shows it as a single like, without the reply text.

i don't know what the "right" thing to do here is, but i suspect you'd rather prioritize the reply over the like, or maybe show them both individually. low priority, obviously. just a heads up!

here's the source HTML snippet:

<div class="e-content">
  wow. this is big news. congrats ben and erin!
  (and <a href="http://cleverdevil.io/">jonathan</a>!)
  <a class="u-in-reply-to u-like-of"
     href="http://stream.withknown.com/2015/known-announces-dreamhost-as-exclusive-web-hosting-sponsor"></a>
</div>

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[benwerd]

Oh! Fascinating. Replies should definitely be prioritized - but there's obviously something more complicated that we maybe should be doing.

[danito]

I bookmarked your post (https://nxd4n.nixekinder.be/2015/known-announces-dreamhost-as-exclusive-web-hosting-sponsor), isn't it handled as a like or other webmention? Is there a other way to "like" your post with Known?

[funwhilelost]

I just discovered that you can like a post from the /share UI. I'm curious why the "like" option isn't shown when you click "Status Update" on the homepage.

[kylewm]

Replies should definitely be prioritized - but there's obviously something more complicated that we maybe should be doing.

I'd vote to keep this simple: prioritize the reply over like (as in 3412c79df2a803748b30b7ea7b63a7725fcb2cc7), and just show it as a reply. Soooo few people post u-in-reply-to u-like-of or u-in-reply-to u-repost-of, and I tend to be of the opinion that those should be separate posts anyway.

[benwerd]

@funwhilelost: To show likes etc by default, I think we'd have to detect that the target page supports them. Otherwise it's extremely confusing. We changed likes to bookmarks because that's a paradigm that most users better understand.

@kylewm: There's an implication here that's worth considering. I think it's mostly visual, but it doesn't make sense for a "like" to take up all the vertical space of a status update, I don't think. I'm wondering if those kinds of metadata posts should just be single lines of the form:

--- Kyle liked This Homepage ---

Or something like that?

[funwhilelost]

@benwerd I see your point from a data point of view but I don't think they're 100% canonical from a user's perspective. Though, if I had to use "bookmark" as my like mechanism I wouldn't lose any sleep over it.

[funwhilelost]

That is to say: Personally I want to "like" pages even if they don't receive it.

[kylewm]

We are talking about totally different things, right? As it stands I believe this issue is resolved and can be closed.

I'm not trying to be pedantic about staying "on topic", just find the discussion in this context confusing. We probably need to have a more open-ended discussion about local and remote likes/stars/bookmarks. the UX is challenging, and questions about them keep coming up.