SWAT0: Difference between revisions

From IndieWeb
(note history, 2010 flow based on Activitystreams, PuSH, Salmon and Webfinger)
(→‎IndieWeb Examples: itemize citations)
Line 49: Line 49:


== IndieWeb Examples ==
== IndieWeb Examples ==
* '''2015-07-12''' two overlapping sets of IndieWeb community members simultaneously demonstrated SWAT0 as documented in: [http://tantek.com/2015/193/t1/congratulations-first-indieweb-swat0 Congratulations first indieweb SWAT0 demo!] and [http://tantek.com/2015/193/t2/user-flow-permalinks-indieweb-swat0 User flow and permalinks from IndieWeb SWAT0 achievement]. Video: [https://aaronparecki.com/notes/2015/07/14/1/swat0 Live demo of #SWAT0 at IndieWebCamp 2015] (93 seconds)
=== 2015-07-12 B A K ===
** '''Players A, B, C''' (caveats if any in parenthesesl)
On 2015-07-12 two overlapping sets of IndieWeb community members simultaneously demonstrated SWAT0 as documented that night in:  
* [http://tantek.com/2015/193/t1/congratulations-first-indieweb-swat0 Congratulations first indieweb SWAT0 demo!] and  
* [http://tantek.com/2015/193/t2/user-flow-permalinks-indieweb-swat0 User flow and permalinks from IndieWeb SWAT0 achievement].  
* Video: [https://aaronparecki.com/notes/2015/07/14/1/swat0 Live demo of #SWAT0 at IndieWebCamp 2015] (93 seconds)
 
* '''Players A, B, C''' (caveats if any in parenthesesl)
** {{benthatmustbeme}}, {{aaronpk}}, {{kevinmarks}} (using a secondary site of his)
** {{benthatmustbeme}}, {{aaronpk}}, {{kevinmarks}} (using a secondary site of his)
** {{benthatmustbeme}}, {{aaronpk}}, {{kylewm}}
** {{benthatmustbeme}}, {{aaronpk}}, {{kylewm}}

Revision as of 23:27, 22 July 2015

SWAT0 is an abbreviation for The Social Web Acid Test level 0 and is an user-feature interoperability test for social web functionality defined in 2010.

See:

Summary

The SWAT0 test can be rephrased in IndieWeb terminology, referring to people's own websites rather than "social network" services.

  1. With his phone, Ben Roberts takes a photo of Aaron Parecki, tags him in the photo, and posts it to his site.
  2. Aaron Parecki gets a notification that he's been tagged in a photo.
  3. Kyle Mahan, who is subscribed to Ben Roberts, sees the photo in his reader UI.
  4. Kyle Mahan posts a reply to the photo from this UI, the reply is posted to his site.
  5. Ben Roberts and Aaron Parecki receive notifications that Kyle Mahan has commented on the photo.

mapping to indieweb

The following indieweb mapping of the SWAT0 steps and user flow was demonstrated on 2015-07-12:

  1. With his phone, Ben Roberts takes a photo of Aaron Parecki, tags him in the photo (by person-tagging with http://aaronparecki.com/) , and posts it to his site (which sends a webmention to aaronparecki.com)
  2. Aaron Parecki gets a person-tag mention (a specific form of person mention) notification that he's been tagged in a photo (because his watch buzzes when he is webmentioned), because Ben Roberts's website linked to aaronpk's site with a class of "u-category h-card".
  3. Kyle Mahan, who follows Ben Roberts, sees the photo in his reader. His reader being Woodwind which is pinged by Ben Roberts's PuSH support.
  4. Kyle Mahan, still using Woodwind, posts a reply to the photo on his site. (using micropub)
  5. Ben Roberts receives a notification that Kyle Mahan has commented on the photo, via webmention to Ben Roberts's site about the new comment, which his server sends back to his client device (laptop browser) as a push notification
  6. Aaron Parecki receives a notification of the new comment on a photo he's tagged in:
    1. because Ben Roberts's server, having received the comment, does salmention sending and thus resends a person-tag webmention to Aaron Parecki
    2. then Aaron Parecki's server receives the person-tag webmention and does salmention receiving processing, notices the new comment on the source of the webmention, generates a push notification to aaronpk's client device (phone) that Kyle Mahan has commented on the photo Aaron Parecki is tagged in.

* Note: On 2015-07-12 Kevin Marks commented on Ben Roberts photo nearly the same time (likely before) as Kyle Mahan, also using Woodwind, but signed-in using his Known install on known.kevinmarks.com. However, kylewm is noted in the example above since he wrote all the software he used (Woodwind and Red Wind). (selfdogfood tie-break).

implementation requirements

For the above to work, each of the three participants has some implementation requirements for their indieweb site/service.

Players A, B, C as identified by the tweetable summary:

A must support

B must support:

  • receiving person-tag mentions on their server and passing them along as a specific push notification to their client device that they've been tagged in a post (preferably (implied) type of post) too.
  • salmention receiving, that is when receiving a webmention, they must notice the new "comment" on the source of the webmention, and
  • generate a push notification to their client device that someone has commented on the photo they are tagged in.

C must support:

  • having a reader with an integrated commenting UI, either directly as part of their site, or as a Micropub client support built into the reader
  • sending a webmention from their site for a reply post to the in-reply-to post

IndieWeb Examples

2015-07-12 B A K

On 2015-07-12 two overlapping sets of IndieWeb community members simultaneously demonstrated SWAT0 as documented that night in:

Background

Past iterations, fixes:

fixed

In the development of the indieweb mapping of SWAT0, the following were figured out and/or fixed:

  • How to handle receiving a salmention - when you receive a webmention in-reply-to your post or person-mentioning you, your server must read not only the source post's authored properties, but also any responses like comments (or likes or reposts) that may be children of that post!
  • How/when to send a salmention - when there's any response to your post, you resend webmentions to any post your post is in-reply-to, as well as anyone person-tagged in your post.
  • How to people-tag someone in a photo. Merely linking in a comment/caption to someone is just a mention, not a people-tag (i.e. the difference between @-mentioning someone in an Instagram comment/caption vs. actually tagging the person at a 2D point in the photo with their (…) "Tag People" UI).
    • Flickr supports tagging people in photos without marking a 2D point in the photo. So I'm not sold on requiring a 2D point as part of tagging people in a photo. Aaron Parecki 10:34, 23 September 2014 (PDT)
    • Still to be improved: area-tagging a person-tag - but not needed for SWAT0
  • How does someone receiving a homepage webmention tell the difference between a mere mention (e.g. in a comment/caption) vs. actually being tagged (optionally at a specific point/rect) in a photo post? I.e. we know how to distinguish between a post-mention/reply/RSVP - and hypothetically homepage-mention/invitation. Possibly by detecting that the source's link to your target is on "u-category" or a "u-url" inside a "u-category h-card"?

history

In 2010, not long after the original SWAT0 challenge, the following protocol flow was figured out based on the proposed standards of the time: Activitystreams (Atom/XML), PuSH, Salmon, and Webfinger

See Also

Retrieved from "https://indieweb.org/wiki/index.php?title=SWAT0&oldid=20977"