A site visitor sees the webmentions of a page.

cedewey commented

2018-05-03 20:55:14 +00:00

(Migrated from gitlab.com)

Background

A webmention is when a page on one website mentions a webpage on another website. For example, when someone's blog post includes a link to another webpage.

Further reading

Acceptance Criteria

Given that I am a site visitor,
when I visit a page that has been mentioned by another site
then I see a the title of the page,linked to its url.

## Background A webmention is when a page on one website mentions a webpage on another website. For example, when someone's blog post includes a link to another webpage. **Further reading** * https://alistapart.com/article/webmentions-enabling-better-communication-on-the-internet * https://indieweb.org/Webmention * https://brid.gy/about * https://webmention.net/draft/ & https://webmention.rocks/ * https://github.com/converspace/webmention/blob/master/README.md. * https://github.com/swentel/indieweb ## Acceptance Criteria Given that I am a site visitor, when I visit a page that has been mentioned by another site then I see a the title of the page,linked to its url.

mlncn commented

2018-12-22 17:35:12 +00:00

(Migrated from gitlab.com)

marked this issue as related to #136

mlncn commented

2018-12-22 17:36:05 +00:00

(Migrated from gitlab.com)

marked this issue as related to #132

cedewey commented

2019-01-25 18:44:01 +00:00

(Migrated from gitlab.com)

changed title from {-Implement webmentions for posts-} to {+A site visitor sees the webmentions of a page.+}

changed title from **{-Implement webmentions for posts-}** to **{+A site visitor sees the webmentions of a page.+}**

cedewey commented

2019-01-25 18:44:01 +00:00

(Migrated from gitlab.com)

changed the description

cedewey commented

2019-01-25 18:44:37 +00:00

(Migrated from gitlab.com)

@mlncn I've added Acceptance Criteria to this issue. Is this what you had in mind?

mlncn commented

2019-01-27 17:17:03 +00:00

(Migrated from gitlab.com)

@cedewey Not quite...

Webmentions are what are used by Indieweb to handle different types of interactions, including:

Comments/Replies
Favorites/Likes
Reposts

I'm not sure any of them necessarily are best captured by the title of the page that mentioned one of our pages.

Comments and replies, which are generally taken to include Twitter mentions, ideally include the entire reply and highlight the profile of the person who made the reply, and somewhat subtly linking back to the site or service where the reply was originally posted.

Favorites and likes are usually represented simply with a count, that can be expanded to show who is in that number; in these cases, the title of the page on the favoriting site/service is likely the same as our post, so the name of the site/profile is what we'd want.

Reposts may not have enough common services for us to worry about right now, but i'm not sure. There might also need to be a separate user story or this one expanded to cover helping people to interact in Indieweb-supporting ways, in particular for reposts (like, how to get 'credit' for reposting our article on your site or on LinkedIn or whatever— Bridgy automates this to the extent it can for social networks and probably there aren't instructions that can help, but i seem to recall that having a submission form to give the link that mentions our site is a thing).

@cedewey Not quite... Webmentions are what are used by Indieweb to handle different types of interactions, including: * Comments/Replies * Favorites/Likes * Reposts I'm not sure any of them necessarily are best captured by the title of the page that mentioned one of our pages. Comments and replies, which are generally taken to include Twitter mentions, ideally include the entire reply and highlight the profile of the person who made the reply, and somewhat subtly linking back to the site or service where the reply was originally posted. Favorites and likes are usually represented simply with a count, that can be expanded to show who is in that number; in these cases, the title of the page on the favoriting site/service is likely the same as our post, so the name of the site/profile is what we'd want. Reposts may not have enough common services for us to worry about right now, but i'm not sure. There might also need to be a separate user story or this one expanded to cover helping people to interact in Indieweb-supporting ways, *in particular* for reposts (like, how to get 'credit' for reposting our article on your site or on LinkedIn or whatever— Bridgy automates this to the extent it can for social networks and probably there aren't instructions that can help, but i seem to recall that having a submission form to give the link that mentions our site is a thing).

mlncn commented

2019-01-27 17:23:11 +00:00

(Migrated from gitlab.com)

changed the description

mlncn commented

2019-01-27 17:46:04 +00:00

(Migrated from gitlab.com)

Revising my thoughts: Treating everything as relatively comment-like, and not making such a big distinction between different kinds of webmentions, is probably how we want to go in the first approximation (like in the example screenshot at https://brid.gy/about)

mlncn commented

2019-01-27 22:57:40 +00:00

(Migrated from gitlab.com)

In the spirit of working on Indieweb for our own site, looking at Jacky Alcine's post about commitment to the free web in 2019 for inspiration, in particular the part below the post is a good example of the submission form:

In theory i can submit the URL of this comment and, even though GitLab doesn't explicitly support Webmentions or other Indieweb protocols, it will be referenced as a reply, so i'll give it a try.

I think favorites or likes would be listed in the 'Bookmarks' section in Jacky's example; in any case I'm wondering if a how-to-bookmark section that could mention ways of doing it yourself and services like Wallabag would make sense, to gently encourage the growth of the non-proprietary web, if not exclusively the own-your-domain IndieWeb.

In the spirit of working on Indieweb for our own site, looking at Jacky Alcine's [post about commitment to the free web in 2019 for inspiration](https://jacky.wtf/weblog/commitment-free-web/), in particular the part below the post is a good example of the submission form: ![Screenshot_2019-01-27_My_Commitment_to_the_IndieWeb_and_Free_Web___jackyalciné](/uploads/eba674c873662e88edce1b040fe1172f/Screenshot_2019-01-27_My_Commitment_to_the_IndieWeb_and_Free_Web___jackyalciné.png) In theory i can submit the URL of this comment and, even though GitLab doesn't explicitly support Webmentions or other Indieweb protocols, it will be referenced as a reply, so i'll give it a try. I think favorites or likes would be listed in the 'Bookmarks' section in Jacky's example; in any case I'm wondering if a how-to-bookmark section that could mention ways of doing it yourself and services like [Wallabag](https://www.wallabag.it/en) would make sense, to gently encourage the growth of the non-proprietary web, if not exclusively the own-your-domain IndieWeb.

mlncn commented

2019-01-28 01:01:31 +00:00

(Migrated from gitlab.com)

The webmention to Jacky's site didn't work, undoubtedly because GitLab blindly adds rel="nofollow" to all links in an effort to reduce the incentive to spam. If i may quote myself from the Definitive Guide to Drupal 7:

Do not set “nofollow,” as in the example; doing so is disrespectful to the people who use your site and against the nature of the Web.

But GitLab isn't built with Drupal 7, so i can't really blame them for not having read that ;-)

The webmention to Jacky's site [didn't work](https://webmention.io/jacky.wtf/webmention/vVtT3i1wsGbdutnzpSmA), undoubtedly because GitLab blindly adds `rel="nofollow"` to all links in an effort to reduce the incentive to spam. If i may quote myself from the Definitive Guide to Drupal 7: > Do not set “nofollow,” as in the example; doing so is disrespectful to the people who use your site and against the nature of the Web. But GitLab isn't built with Drupal 7, so i can't really blame them for not having read that ;-)

A site visitor sees the webmentions of a page. #68

Background

Acceptance Criteria