Webmentions: Enabling Better Communication on the Internet

18 thoughts on “Webmentions: Enabling Better Communication on the Internet”

1. Lurking
   Yesterday I was catching up on chat logs and ran across a stub for lurking on the IndieWeb wiki. I cleaned up the formatting a bit and added some additional material. Later Ton Zijlstra dropped a link to his excellent article from 2004 on the topic: Lurking and Social Networks (though honestly, I first came by the link courtesy of our good friend Jeremy Cherfas who added it to the wiki page).

   Lurking is the quiet watching/listening that what many people of the web do in chat rooms in order to begin gauging culture, learning jargon or lingo, and other community norms or unspoken principles before diving in to interact on a more direct level with other participants.

   While the word lurking can have a very negative connotation, online it often has a much more positive one, especially in regard to the health and civility of the commons. Rather than rehash what Ton has done an excellent job of doing, I won’t go into the heavy details and history of online lurking, but instead, let’s take a look at where it isn’t in today’s social media landscape.
   Twitter
   Since 2004, Twitter and a slew of other social media has popped up on the scene and changed many of our prior behaviors concerning lurking. In particular, Twitter’s interface has made it far easier to either like/favorite a post or retweet it.
   In comparison the the preceding era of the blogosphere represented by Tons’ post, Twitter has allowed people to send simple notifications back and forth about each others’ posts indicating a lower bar of interaction than writing a thoughtful and measured comment. Now instead of not knowing about dozens, hundreds, or thousands of lurkers, a (micro)blogger would more quickly know who many more of their readers were because they were liking or resharing their content. Naturally there are still many more potential lurkers who don’t interact with one’s posts this way, but these interactions in some way are like adding fuel to the fire and prompt the writer to continue posting because they’re getting some feedback that indicates they’ve got an audience. Twitter has dramatically lowered the bar for lurkers and made it more socially acceptable for them to make themselves known.
   Twitter image from the collection Social Decay by Andrei Lacatsu
   Of course, not all is rosy and happy in Twitterland as a result of this lowering the social bar. Because it’s so easy to follow almost anyone and interact with them, naturally everyone does. This means that while before one may have lurked a blog for weeks or months before posting a response of any sort, people are now regularly replying to complete strangers without an resistance whatsoever. While this can be valuable and helpful in many instances, oftentimes it comes off as rudely as if one butted into the private conversation of strangers at a public gathering. At the farther end of the spectrum, it’s also much easier for trolls to tag and target unsuspecting victims. As a result, we have the dumpster fire that Twitter has become in the past several years for many of its users.
   The problem for the continued health of the commons is how can we maintain a bar for online lurking, but still provide some feedback? How can we keep people from shouting and yelling at passer-by from their proverbial front porches or vice-versa? How might we encourage more positive lurking online before directly jumping into a conversation? 
   Read Posts and Private Posts
   For several years now, as a part of the IndieWeb movement, I’ve been more directly controlling my online identity and owning my content by using my own domain name and my own website (boffosocko.com). While I still use Twitter, I’m generally only reading content from it via a feed reader. When I post to or interact with it, I’m always publishing my content on my own website first and syndicating a copy to Twitter for those who don’t own their online identities or content and (sadly) rely on Twitter to do that for them. 
   Within this setting, since roughly late 2016, I’ve been posting almost all of what I read online or in books, magazines, or newspapers on my own website. These read posts include some context and are often simply composed of the title of the article, the author, the outlet, a summary/synopsis/or first paragraph or two to remind me what the piece was about, and occasionally a comment or two or ten I had on the piece.

   An example read post with context from my website at https://boffosocko.com/2019/06/02/lurking-and-social-networks-ton-zijlstra/
   In tandem with these posts, I’m also sending webmentions to the websites of those pieces. These (experimental) read webmentions are simply notifications to the originating site that I’ve read their piece. In our prior framing of lurking or Twitter, I’m sending them the simplest notification I can think of to say, “I’m here lurking. I’m reading or looking at your work.”
   I’m not saying that I liked it, favorited it, disliked it, bookmarked it, commented on it,  or anything else, but simply that I read it, I consumed it, I spent the time to interact with it. But in contrast with Ton’s older method of looking at server logs to see what kind of traffic his posts are getting, he can see exactly who I am and visit my website in return if he chooses. (Ton’s old method of sifting through those logs was certainly not a fun experience and the data was usually relatively anonymous and useless.) These newer read notifications could potentially give him a much richer idea of who his (lurking) audience actually is. Then when someone shows up with a comment or reply, it’s not completely from out of the dark: they’ve previously indicated that they’re at least somewhat aware of the context of a potentially broader conversation on his site.
   These read notifications are semantically different from likes, favorites, or even bookmarks on other platforms. In fact many platforms like Twitter, which has moved from “stars” (with the semantic idea of a favorite) to “hearts” (with the semantic idea of a like), have so few indicators of reaction to a post that the actual meaning of them has been desperately blurred. Personally I’ll use Twitter’s like functionality variously to mean: “I’m bookmarking this (or the linked article within it) for reading later”, “I like this post”, “I’ve read this post”, or even “I’m acknowledging receipt of your reply to me”. That’s just too much meaning to pack into a silly little heart icon.
   Because I’m using my own website over which I have complete control, I can make it do a better job of unpacking some of this semantic tom-foolery. I’ve written about it a bit in the past if you care to see some of the details: Thoughts on linkblogs, bookmarks, reads, likes, favorites, follows, and related links. See also: the read-posts tag on this site.
   If they choose, some website owners display these read post notifications in one or more ways. Some sites like Aaron Parecki’s or Jeremy Keith’s will show my interactions as bookmarks. Others, primarily WordPress-based websites that support Webmention (via plugin), will actually show these interactions in their comment sections under the heading “Read” and display my photo/avatar as an indicator that I’ve interacted with that post. In the case of read posts on which I’ve written one or more comments, the receiving site also has the option of showing my interaction not as a read/bookmark intent, but could also show my comments as a reply to their post. I’ve written a bit about this and its potential for large news outlets before in Webmentions: Enabling Better Communication on the Internet for A List Apart. There are also some older legacy sites that might show my interactions as a trackback or pingback, but these seem few and far between these days, particularly as those systems are major targets for spam and the Webmention protocol has a richer interaction/display model.
   How Jeremy Keith displays shares, likes, and bookmarks (including my read post) in the comment section of his website.
   The display of a read post on ColoradoBoulevard.net
   A new itch
   But as I think about these read posts, lurking, and being more civil on the internet, I have a new itch for some functionality I’d like to add to my website. I very frequently use my website as a digital commonplace book to collect links of things I’ve read, watched, and listened to. I’ll collect quotes, highlights, and even my own marginalia. As I mentioned above, my read posts sometimes have comments, and quite often those comments are really meant just for me and not for the author of the original post. In many cases, when my comments may be too egregious, sensitive, or perhaps even insulting to the original author, I’ll make these posts private so that only I can see them on my site.  Of course when they’re private, no notifications are sent to the site at the other end of the line.
   Sometimes I would like to be able to send a read notification to the site, but also keep my commentary privately to myself. This allows me to have my notes on the piece and be highly critical without dragging down the original author or piece who I may not know well or the audience of that same piece which I haven’t properly lurked (in the positive community-based sense indicated above) to be as intelligently and sensitively commenting as I would otherwise like. Thus I’d like to build in some functionality so that I can publicly indicate I’ve read a piece (and send a notification), but also so that I can keep the commentary on my read private to either myself or a smaller audience.
   I suspect that I can do this in a variety of meta-fields on my website which aren’t shown to the public, but which might be shown to either myself or logged in users. In some sense, this is a subset of functionality which many in the IndieWeb have been exploring recently around the ideas of private posts or by limiting the audience of a post. In my case, I’m actually looking at making a post public, but making smaller sub-portions of it private.
   To begin with, I’ll most likely be looking at doing this at a small scale just for myself and my commonplace book, as I can definitely see second and third-order effects and a variety of context collapse issues when portions of posts are private, but others who may be privy to them are commenting on those pieces from the perspective of their public spheres which may not be as private or closed off as mine. i.e.: While I may have something marked as private, privy readers will always have the option of copy/pasting it and dragging it out into the public.
   For those interested, I’ll briefly note that Sebastiaan Andeweg just wrote Private posts: the move of the checkins which has some useful and related background to private posts. (Of course I remember exactly when I read it.) I also highly suspect there will be a private posts related session(s) at the upcoming IndieWeb Summit in Portland in June (tickets are still available). I’m interested to see what others come up with on this front.

   Syndicated copies to:
   Flipboard icon
   
   Tumblr icon
   
   WordPress

   Syndicated copies:

   Reply

2. Watched Against Blogging by Zach Whalen from Domains 2019 | YouTube

   [youtube https://www.youtube.com/watch?v=ojDBIrykiNc&w=560&h=315%5D
   For the past 15 years, I’ve included blog assignments in my classes as a default, routine, and generally low-stakes assignment. It began with a simple journal where students kept track of their progress through a video game, and through the years, the assignment has ranged from similarly simple logs or progress reports to the more ornate and decorous “features articles” where students seek to emulate magazine writing and engage with a public audience. At times, like when having a platform online was still a novelty and the adrenaline rush of Web 2.0-fueled activism took flight in the optimism of Barack Obama’s first presidential campaign, blogging totally made sense. As a classroom experience, a blog assignment helped students find their digital identity through written expression. By finding their voice digitally, students found themselves. But while this will still happen, and while I still see brilliant writing from my students, the era when the exigency of a blog assignment can be reliably vindicated by an authentic external audience has ended. It’s time for something else, which means it’s time to re-evaluate what blogs have been and what we have needed them for in order to find the best ways to meet those goals through other means. In this short presentation, I will offer several suggestions. This is, however, an aspirational proposal. I’m writing this between semesters as I reflect on the Fall — where blog assignments didn’t always meet my goals or in some cases arguably undermined other goals for my class — and thinking ahead to the Spring — when I hope to implement some new assignments based on this recent conviction about the ineffectuality of blog assignments. Therefore, by June, my expectation is that I will have something new to report: either finding success with an entirely new set of assignments and corresponding tools, or returning to the familiar embrace of blog assignments with a renewed sense of their value. Most likely, I’ll be somewhere in between, but my hunch is that different forms of discursive content creation will help students take control of their learning and find direction for their digital identities. Whatever I find in the coming semester, I’m confident that I’ll be ready to share some insight into the intents, purposes, and outcomes of inviting students to do intellectual work on the internet of 2019.

   Notes as they occur to me while I’m watching this video:
   To me blogging is a means of thinking out loud.
   Of course having a site doesn’t mean one is blogging. In fact, in my case, I’m collecting bits and pieces on my site like a digital commonplace book, and out of those collections come some quick basic thoughts, and often some longer pieces, which could be called blog posts, but really are essays that help to shape my thinking. I really wish more people would eschew social media and use their own websites this way.
   We need to remember that a website or domain is FAR, FAR more than just a simple blog. 
   It kills me how many in the edtech/Domains space seem to love memes. It’s always cute and fun, but they feel so vapid and ineffectual. It’s like copying someone else’s work and trying to pass it off as our own. English teachers used to say, “Don’t be cliché,” but now through the use of digital memes they’re almost encouraging it. Why not find interesting images and create something new and dramatically different.  (I can’t help but think of the incredibly unique Terry Gilliam “cartoons” in Monty Python’s Flying Circus and the phrase “and now for something completely different…”.
   Zach uses the phrase “personal learning journal” but doesn’t quite get to the idea of using domains as digital commonplace books.  He also looks at other social sites like Tik-Tok, Instagram stories, YouTube channels, and Twitter hashtags, but doesn’t consider that what those things are could easily be contained within one’s own personal site/domain. The IndieWeb has been hacking away at just this for several years now. What he’s getting at here, but isn’t quite saying is “Why can’t we expand the Domain beyond the restrained idea of “just a blog.” And isn’t that just the whole point of the IndieWeb movement? Your website can literally be anything you want it to be! Just go do it. Invent. Iterate. Have fun!
   Zack should definitely take a look at what one can do with Webmention. See: Webmentions: Enabling Better Communication on the Internet. I suppose some of the restraint is that most people don’t know that it’s relatively easy now to get one domain to be able to talk to another domain the way social sites like Facebook and Twitter do @mentions. And once you’ve got that, there’s a whole lot more you can do!
   Perhaps what we should do is go back to the early web and the idea of “small pieces, loosely joined“. What can we do with all the smaller, atomized pieces of the web? How can we use these building blocks in new and unexpected ways? To build new and exciting things? What happens when you combine Facebook, Twitter, Instagram, Snapchat, Blogger, Soundcloud, Foursquare, Flickr, Goodreads, Periscope, Lobsters, TikTok, Quora, Zotero, Flipboard, GitHub, Medium, Huffduffer, Plurk, etc., etc. altogether and mix them up in infinite ways? You get Domains! You may get something as cutting edge–but still relatively straight-laced–as Aaron Parecki’s website, which you might have to dig into to realize just how much he’s got going on there, or you might end up with something as quirky and cool as Kicks Condor’s site or his discovery/syndication channel Indieweb.xyz.
   Want to be able to use your website to highlight and mark up what you read? Go ahead and do that! I have. You could keep a record of everything you watch or listen to. Make a food diary. Track where you’ve been. Want to keep collections of chicken related things so your site can have a chicken feed? Go crazy!! 
    

   Reply

3. Watched Against Blogging by Zach Whalen from Domains 2019 | YouTube

   [youtube https://www.youtube.com/watch?v=ojDBIrykiNc&w=560&h=315%5D
   For the past 15 years, I’ve included blog assignments in my classes as a default, routine, and generally low-stakes assignment. It began with a simple journal where students kept track of their progress through a video game, and through the years, the assignment has ranged from similarly simple logs or progress reports to the more ornate and decorous “features articles” where students seek to emulate magazine writing and engage with a public audience. At times, like when having a platform online was still a novelty and the adrenaline rush of Web 2.0-fueled activism took flight in the optimism of Barack Obama’s first presidential campaign, blogging totally made sense. As a classroom experience, a blog assignment helped students find their digital identity through written expression. By finding their voice digitally, students found themselves.
   But while this will still happen, and while I still see brilliant writing from my students, the era when the exigency of a blog assignment can be reliably vindicated by an authentic external audience has ended. It’s time for something else, which means it’s time to re-evaluate what blogs have been and what we have needed them for in order to find the best ways to meet those goals through other means. In this short presentation, I will offer several suggestions.
   This is, however, an aspirational proposal. I’m writing this between semesters as I reflect on the Fall — where blog assignments didn’t always meet my goals or in some cases arguably undermined other goals for my class — and thinking ahead to the Spring — when I hope to implement some new assignments based on this recent conviction about the ineffectuality of blog assignments. Therefore, by June, my expectation is that I will have something new to report: either finding success with an entirely new set of assignments and corresponding tools, or returning to the familiar embrace of blog assignments with a renewed sense of their value.
   Most likely, I’ll be somewhere in between, but my hunch is that different forms of discursive content creation will help students take control of their learning and find direction for their digital identities. Whatever I find in the coming semester, I’m confident that I’ll be ready to share some insight into the intents, purposes, and outcomes of inviting students to do intellectual work on the internet of 2019.

   Notes as they occur to me while I’m watching this video:
   To me blogging is a means of thinking out loud.
   Of course having a site doesn’t mean one is blogging. In fact, in my case, I’m collecting bits and pieces on my site like a digital commonplace book, and out of those collections come some quick basic thoughts, and often some longer pieces, which could be called blog posts, but really are essays that help to shape my thinking. I really wish more people would eschew social media and use their own websites this way.
   We need to remember that a website or domain is FAR, FAR more than just a simple blog. 
   It kills me how many in the edtech/Domains space seem to love memes. It’s always cute and fun, but they feel so vapid and ineffectual. It’s like copying someone else’s work and trying to pass it off as our own. English teachers used to say, “Don’t be cliché,” but now through the use of digital memes they’re almost encouraging it. Why not find interesting images and create something new and dramatically different.  (I can’t help but think of the incredibly unique Terry Gilliam “cartoons” in Monty Python’s Flying Circus and the phrase “and now for something completely different…”.
   Zach uses the phrase “personal learning journal” but doesn’t quite get to the idea of using domains as digital commonplace books.  He also looks at other social sites like Tik-Tok, Instagram stories, YouTube channels, and Twitter hashtags, but doesn’t consider that what those things are could easily be contained within one’s own personal site/domain. The IndieWeb has been hacking away at just this for several years now. What he’s getting at here, but isn’t quite saying is “Why can’t we expand the Domain beyond the restrained idea of “just a blog.” And isn’t that just the whole point of the IndieWeb movement? Your website can literally be anything you want it to be! Just go do it. Invent. Iterate. Have fun!
   Zack should definitely take a look at what one can do with Webmention. See: Webmentions: Enabling Better Communication on the Internet. I suppose some of the restraint is that most people don’t know that it’s relatively easy now to get one domain to be able to talk to another domain the way social sites like Facebook and Twitter do @mentions. And once you’ve got that, there’s a whole lot more you can do!
   Perhaps what we should do is go back to the early web and the idea of “small pieces, loosely joined“. What can we do with all the smaller, atomized pieces of the web? How can we use these building blocks in new and unexpected ways? To build new and exciting things? What happens when you combine Facebook, Twitter, Instagram, Snapchat, Blogger, Soundcloud, Foursquare, Flickr, Goodreads, Periscope, Lobsters, TikTok, Quora, Zotero, Flipboard, GitHub, Medium, Huffduffer, Plurk, etc., etc. altogether and mix them up in infinite ways? You get Domains! You may get something as cutting edge–but still relatively straight-laced–as Aaron Parecki’s website, which you might have to dig into to realize just how much he’s got going on there, or you might end up with something as quirky and cool as Kicks Condor’s site or his discovery/syndication channel Indieweb.xyz.
   Want to be able to use your website to highlight and mark up what you read? Go ahead and do that! I have. You could keep a record of everything you watch or listen to. Make a food diary. Track where you’ve been. Want to keep collections of chicken related things so your site can have a chicken feed? Go crazy!! 
    

   Syndicated copies to: Twitter icon
   

   Reply

4. Usually I’m reading their content via a feed reader, but last night I visited their actual site and I noticed that the Nieman Lab has a reading page!
   Since they’re unlikely to report on the mechanics of some of their own website and journalistic output, I’ll take a moment to highlight it on their behalf.
   Reading pages or Linkblogs
   Traditionally known as linkblogs back in the old blogosphere days, this sort of web pattern is probably better and more specifically called a “reading page” now. (Even Nieman titles the page “What We’re Reading” and uses /reading/ in the URL path to the page itself.) Many people still maintain linkblogs or bookmark pages (often on social silos like Pinboard, Pinterest, Twitter, Pocket, Instapaper, et al.), but generally the semantic name there implies articles or pages that were found to be of general interest or that one wanted to keep to read or consume later. On today’s more advanced web, there’s actually more value in naming it a reading page as it indicates a more proactive interest in the bookmarked content–namely having spent the time, effort, and energy to have actually read the thing being bookmarked. This additional indication of having more skin in the game provides a lot of additional value of a read post over a simpler bookmark post in my mind. It’s also part of the reason my website sends and receives read-specific webmentions.
   This pattern of providing links of read material is pretty cool for a variety of reasons.
   Discovery
   First, if you’re following and reading the Nieman Lab, you’re very likely going to be interested in many of the things that they’re reading, researching, and covering. By providing a reading page they’re giving their readers a trove of useful data to discover articles and material in similar and tangential spaces that the lab may not be able to actively cover or engage in at the time. 
   Context
   By knowing what the Lab is reading, you’re provided with a broader perspective of the things they’re actively interested in. By reading those things yourself, you’ll have increased context into what they’re doing, what those areas look like, and what they are adding to the conversation in their research and work.
   Added value to their site
   Linkblogging has long been a thing, and, in part, is what a large number of Twitter users are typically doing. In Nieman Lab’s case, they’re just doing it on their own website, which adds tremendous value to it. By smartly hosting it on their own site they’re also guarding against the built value of their read archive disappearing if they were hosted on a social silo (remember Delicious? CiteULike?). Also by keeping it on their site, it has more long-tail value than if it were to all disappear into the new-content-wins attention machine that Twitter has become.
   Of course I’d personally find it a lot more beneficial if they provided or advertised a linkblog feed for their reading page. Sadly they don’t. However, if you’re as interested as I am, you’ll dig under the hood a bit to discover that Nieman Lab’s site is built on WordPress and they’re using that page likely with a category, tag, or other taxonomy. So with a short bit of intuitive guessing about how WordPress is structured, we happily discover there is a feed of their reads at https://www.niemanlab.org/reading/feed/. (I suspect this feed exists as a design choice by WordPress than by the design or will of the Nieman Lab.) If you prefer a faster, one button subscribe option:

   If Nieman would like their own universal follow button like this, take a peek at what SubToMe has to offer on this front.
   Value to research
   By accumulating a trove of links and summaries, which they’re hopefully keeping, they’re creating a huge relevant database for future research on the topics in which they have interest. The small pieces that may not make sense today may potentially be woven into future narratives and pieces of research later, but this sort of thing is vastly harder to do without reading and making note of it. In a sense, they’re creating a corporate or research lab-based commonplace book for their own use.
   Other Examples
   While I’ve seen many people (generally individuals and not magazines, companies, or other bigger outlets) regularly publish newsletters or weekly posts on what they’ve found on the web that is interesting, I haven’t seen as many who publish specific pages or archives of what they’re reading. Even fewer provide RSS or other feeds of this content.
   The IndieWeb wiki read page has some useful and interesting examples of this behavior, but they’re almost all individuals. 
   One other example I can think of in the journalism space, mostly because it’s getting to that end-of-the-year recap time is Bloomberg’s Jealousy List, which this year incidentally has some fun little drolleries that move as you scroll the page. This subset of reading lists is interesting as a group of articles Bloomberg wished they’d written and published themselves. This may indicate that they’re keeping a reading list internally, but just not publishing it regularly like Nieman is.
   I can’t help thinking if Nieman Lab’s OpenFuego bot is a part of their workflow in creating their reading page as well?
   And finally, since I also have a similar behavior, I’ll mention that you can find my reads on my reading page (sometimes with commentary) or follow it all via RSS if you like.
   Are you aware of other people or organizations publishing lists of what they’re actively reading online? Do they provide feeds? How can we make this feature more prevalent on the open web?

   Syndicated copies to:
   
   Twitter icon
   
   Micro.blog icon
   

   Reply

5. Next we’ll want the Webmention Plugin (+Semantic Linkbacks) which will let our site communicate with other websites as well as to receive replies and reactions on Twitter with the help of Brid.gy. Install and activate both. #PressEdConf20
   (Want to go deeper into the idea of what Webmention is and how one could use it?  I wrote an article for A List Apart that goes into details.)

   Syndicated copies:

   Reply

6. Last year I thought it would be fun to outline how people might use their #WordPress websites to actively participate in #PressEdConf20 by posting content on their WordPress website and syndicating copies to Twitter for those following that way.
   (Meta: Welcome to my talk: I know it’s cheating & early, but I’m hoping a few presenters will borrow this method.) 

   My general thought was:
   The only thing better than A WordPress and Education, Pedagogy and Research Conference on Twitter would be A WordPress and Education, Pedagogy and Research Conference using WordPress itself!
   (Meta: Sure, post it to Twitter: but why not own a copy of your presentation on your own website when you’re done?)

   So let’s give it a spin by providing an outline for how to accomplish it in true #IndieWeb & #DoOO fashion? Perhaps a few people might trying doing this year’s conference this way? Here’s an early #PressEdConf20 presentation to get the juices flowing.
   (Meta: Hint for those on Twitter: I’m including links to my website, so you can get just a little bit more information than Twitter limits me to–oh, the fringe benefits of having one’s website where they’re not censored by the confines of the platform on which they’re creating!)

   First, we’ll start off by making the humble presumption that you’ve got your own domain and an install of WordPress running on it. Hopefully this covers most #PressEdConf20 attendees.
   (Meta: If it doesn’t there are lots of options: You could do something similar a bit more manually if you like using WordPress.com. You’ve also got a great community of people who could help you to better own your online identity and domain right here! I’ll bet our friends at Reclaim Hosting could help as well.)

   Next we’ll want the Webmention Plugin (+Semantic Linkbacks) which will let our site communicate with other websites as well as to receive replies and reactions on Twitter with the help of Brid.gy. Install and activate both.
   (Want to go deeper into the idea of what Webmention is and how one could use it?  I wrote an article for A List Apart that goes into details.)
   Illustration by Dougal MacPherson
   Image courtesy of A List Apart

   One could manually syndicate content from WordPress to Twitter, but there are multiple plugins and ways to syndicate it. My favorite is the Syndication Links plugin, which we can use for syndicating to other services. Install and activate. 

   Next we’ll want an account on Brid.gy for Twitter. This will allow us to publish from our website to Twitter; it will also allow us to reverse syndicate reactions  from #PressEdConf20 on Twitter back to our posts using Webmention.
   (Meta: Publishing this way will require Microformats: Your theme will need the proper microformats support to use this method, but again other methods are available.)

   Authenticate your website and Twitter account with Bridgy and enable Bridgy publish on your account page: https://brid.gy/twitter/username.

   In Syndication Links settings at example.com/wp-admin/admin.php?page=syndication_links

   Enable Syndication to Other Sites
   Enable Twitter via Bridgy

   Add a custom provider using the following:

   name: XYZ pressEdconf20
   UID: XYZ-pressEdconf20
   target URL: https://indieweb.xyz/en/pressEdconf20/

   Save the settings.
   (Meta: Syndication Links Settings: These will help you set up syndication targets on other platforms and can be configured for a variety of social media.)
    
    
    
    

   Now write all of your posts in your presentation as status updates (without titles) and include any media (photos, videos, etc.) making sure to mark up the photos with a class of u-photo in the HTML. Don’t forget the hashtag #PressEdConf20.

   Set posts for one every minute. Use the SL Syndicate To meta box to syndicate your Twitter account and to the indieweb.xyz sub where everyone can find them (if they’re not following the proceedings via Twitter).

   Others at #PressEdConf20 with Webmentions can reply to your posts on their sites. Replies will show up in comments depending on settings. Bridgy will also find responses to your content on Twitter & syndicate those back to your website automatically.
   (Meta: Give it a whirl!: Reply to this post on Twitter to see it boomerang back to the comment section of my website.)
   Webmention rocks

   Those who are paying attention at #PressEdConf20 will see the value in webmention for allowing cross-site interactions without the need for “social media”. WithKnown, Drupal, Grav, and other CMSs are capable of doing this too.
   (Meta: Ownership of your Open Pedagogy Anyone? Who needs invasive corporate social media to interact online now?)

   With luck, I’ll have created this entire #PressEdConf20 presentation on my own website and syndicated it to Twitter without actually needing to visit Twitter itself. I’m around for questions. Thank you for your time and attention. [more…]
   Those looking for more details can find documentation on the IndieWeb wiki at https://indieweb.org/Getting_Started_on_WordPress, or https://boffosocko.com/2018/04/27/setting-up-wordpress-for-indieweb-use/
   I’m also happy to help people set things up and make alternate suggestions via video chat or you can find online help in the IndieWeb WordPress chat.

   P.S. There’s still some time to submit your talk for #PressEdConf20. Since it’s all designed to be online from the start, I’m hoping it won’t be cancelled like all the other events lately.
   (Meta: PressEdConf 2020: A WordPress and Education, Pedagogy and Research Conference on Twitter March 26, 2020)

   Syndicated copies:

   Reply

7. What is a Webmention?
   Webmention is a relatively recent web standard (or W3C recommendation) that allows notifications when one website mentions a URL on another website. Think of it like @mentions on social platforms, but instead of just working within a particular website from one account to another, they work across websites. Your website can now @mention my website!
   For those who are interested in delving deeper into the idea and its implications, I’ve written a primer in the past : Webmentions: Enabling Better Communication on the Internet.
   The goal is for other websites to be able to reference content in my TiddlyWiki website, and if those websites support sending the notifications as either webmentions (or the older pingbacks), I’ll get a notification that my content was referenced elsewhere on the web. This is just the beginning of allowing two way communication between websites.
   My exploration today is how to quickly get these up and running on a public TiddlyWiki instance. The public part is important because webmentions won’t work for non-public URLs which includes private TiddlyWikis. If you’re wondering how to self-host a TiddlyWiki on your own domain, I’ve recently written up a tutorial for doing just that. At the end of this article, I’ll make a few notes about how one might use webmentions, particularly in a TiddlyWiki ecosystem.
   I’ll start out by saying that writing a full JavaScript implementation of the Webmention spec is beyond my capabilities presently, but it could be something that TiddlyWiki core might implement in the future. (Maybe something like Lazymention which is written in node.js might be leveraged?)
   Here I’m going to focus on using a third party service to do all of the heavy lifting and code our behalf. It’s relatively common, especially in the static website space, for websites to rely on third party or publisher services to either send or receive Webmentions on their behalf. Given my current knowledge of TiddlyWiki and how its internals work and my knowledge of Webmention services, I thought it would be quickest and easiest to look at using the Webmention.io service to handle receiving these @mentions from other sites on my behalf.
   While this article may seem long, I’m hoping it’s detailed enough for those who are code averse to follow the recipe and do this themselves. If you can create a Tiddler, cut and paste some text, and follow the tutorial you won’t need to know anything about code. I did the entire thing myself in about five minutes from start to finish.
   Receiving Webmention notifications for your TiddlyWiki
   As a quick overview, we’re going to cut and paste a few lines of code into a special tiddler of our TiddlyWiki based website. This will allow us to do two things:

   Log into Webmention.io to create an account
   Allow other sites that send webmentions to us to find an endpoint on our TiddlyWiki website that accepts them on our behalf.

   We’ll then rely on the Webmention.io dashboard to show us our notifications or received webmentions.
   Logging into Webmention.io
   Webmention.io requires you to log in with your domain name/URL and relies on you being able to authenticate yourself using it. Since I’m not aware of an IndieAuth or equivalent mechanism for using TiddlyWiki to log into Webmention.io, the quickest method to accomplish this is to rely on RelMeAuth using IndieAuth.com to log into Webmention.io using either a Twitter or GitHub account. From a non-technical perspective, we’ll be using either our Twitter or GitHub account and it’s OAuth2 security to log into the service.
   First we want to put a link to our public TiddlyWiki website into the website field on either Twitter or GitHub using the profile settings of one of those services. Here’s what mine looks like on GitHub:
   
   Next we want to place a corresponding link to the relevant service into the <head> of our TiddlyWiki site using one (it’s okay to use both) of the the following lines of code:
   <link rel="me" href="https://twitter.com/username" />
<link rel="me" href="https://github.com/username" />
   where you will replace the username in these links with the respective usernames of your accounts. (I’ll note that you don’t need to do this for both accounts, you can use either Twitter or GitHub.)
   To place these lines into the appropriate location on your TiddlyWiki, you’ll want to create a tiddler with a name like $:/plugins/indieweb/core/rawMarkup and the tag $:/tags/RawMarkup.
   Then cut and paste one or both of these links as appropriate into this tiddler and save it (and your TiddlyWiki).
   You should now be able to go to webmention.io and enter the URL for your TiddlyWiki into the web sign in box and click “sign in”. The service will parse your website’s page, find the link to either Twitter or GitHub and present you with the appropriate sign in button for one or both of those services. Click on the button for your chosen service. IndieAuth.com will then take you to that service to log into it, or, if you’re already logged in, it will take you back to webmention.io to your new account.
   Creating your Webmention endpoint
   Within webmention.io you can now go to the “settings” page which will give you two more links which are your webmention and pingback endpoints. They will look something like this:
   <link rel="webmention" href="https://webmention.io/example.com/webmention" />
<link rel="pingback" href="https://webmention.io/example.com/xmlrpc" />
   where example.com will be replaced with the URL for your website.
   Now you should cut and paste these two <link>s into the same tiddler you created above: $:/plugins/indieweb/core/rawMarkup. Now save the Tiddler and your TiddlyWiki. (Be sure to leave the previous links in case you need to log back into webmention.io in the future.)
   You’re done!
   That hopefully wasn’t too hard.
   But what does this do? When another website links to your website and sends you a notification, the code on your page will delegate the receipt of the webmention to webmention.io which will verify that the sending site has your URL on a publicly viewable page (this helps to cut down on spam problems that pingbacks used to have). It will then store the notification for you.
   If you need a reminder to check them occasionally, maybe you could add a Tiddler with the link to your dashboard to appear on your wiki when you open it next.
   Perhaps in a future tutorial I’ll delve into the specifics of actually showing these mentions directly within your TiddlyWiki on the Tiddlers to which they relate.
   Optional Webmention badge
   Some may notice that I’ve put a small Webmention badge into the footer of my TiddlyWiki site to visually indicate to human readers that the site accepts webmentions. You can optionally do this for fun if you’d like.
   Sending Webmentions with TiddlyWiki
   Sending Webmentions seems to be an issue as the fragment-based URLs that TiddlyWiki uses as permalinks using JavaScript seem to cause an issue with many receivers. They apparently have problems resolving and parsing pages due to js;dr related issues. I would send webmentions manually, but most receivers I’m aware of have this js;dr problem. I’m not sure if there is an easy way around this issue.
   Hyperchats, Wikis, and Open Educational Resources
   What’s interesting about supporting Webmention, particularly from a TiddlyWiki perspective, is that if my TiddlyWiki is notified of mentions of it from outside sources, I can quickly cut and paste those responses directly into my Wiki pages in a pseudo-comment section similar to the comments section on this post which could serve as a model. If those mentions of a particular Tiddler are from other TiddlyWikis, I could also choose to drag-and-drop (or import) them into my TiddlyWiki!
   If I want to go a step further, I could transclude those imported Tiddlers into the Tiddler that they’re in reference to. Perhaps I might do this under a heading of “@mentions” or perhaps “Comments” and suddenly I’ve got a way of displaying two-way conversations on my own TiddlyWiki site.
   As is mentioned in Kicks Condor’s post about Hyperchat Modality, one could potentially use custom theming information (cleverly named “whostyles” in that post) from imported Tiddlers (or themes from other platforms) to identify the web identities of the sites they’re received from. I’ll also mention Kicks’ post about Hypertexting which is related and forms an interesting melange of websites, blogs, wikis, and hypertext of all kinds to form a more interesting web medium.
   For the broader information collecting and building or academic communities (and here I can’t help thinking about the Open Educational Resources space that uses Creative Commons licensing to build their teaching resources), one could use these webmentions as a means of notifying sites that their content has been used, changed, or updated (typically those using Creative Commons will credit their source using a link). Then the receiver of the notification could optionally add to or change their version or even just collect the changes. This becomes particularly useful when the Tiddlers can be easily dragged and dropped between TiddyWikis!
   As an explicit example, imagine a professor who wanted to build a textbook anthology, but who could do so by dragging and dropping a variety of Tiddlers from one site to another to create a quick textbook or reader for their students. This idea is particularly exciting to me when combined with the idea behind TW5-powered ebooks!
   What could you imagine doing with webmention notifications on your TiddlyWiki site?

   Syndicated copies:

   • website

   Reply

8. Nearly headless WordPress (for ubiquity and ease-of-use) + Micropub (for posting almost anything quickly) + Webmention (for cross site communication) + frosted in IndieWeb goodness = blog evolved.
   Sadly, it seems like too many in the thread completely got lost on the “why” portion which was the best part of the question.

   Reply

9. Sue, I wrote a generally non-technical primer on them a while back. I think they could be used to some interesting effect in the OER space actually. Perhaps we ought to focus this month’s #DoOO meetup on the topic?

   Reply

10. Sorry if it’s not intuitive. I wrote my response on my website and syndicated to Twitter. There are two links, one bare that goes to my original & the other is a twitter “card” that goes to the article. Otherwise the version on my site has a link to the other article too.
    
    

    Reply

11. My poor little website passed 23,000 comments/replies/reactions yesterday. This is in tremendous part due to webmentions and the ability to collect the conversation about my content across social spaces.
    I’m wondering when comments will pass the number of posts (currently 27,648)?

    Syndicated copies:

    Reply

12. Chris Aldrich
    Hello! I’m Chris. I use this website as my primary hub for online identity and communication. It’s also my online commonplace book.
    Below, you’ll find a variety of media types I publish. You’ll also see lists of categories I frequently publish to including IndieWeb, mathematics, information theory, biology, history, economics, humanities, note taking & related topics. If you’re interested in more niche sub-topics, I have a list of tags available for searching and following as well.
    As a member of the IndieWeb movement/community, I follow many of their principles including owning all of my own data by publishing it on my own website. When I participate on most social media sites, I generally post here first and syndicate/cross-post duplicates out to them (POSSE). In some cases, I may post to social services first and then immediately syndicate copies of that content to my own website (PESOS). This site supports the receipt of Webmention notifications and, when possible, will show replies from other websites. If you @mention me on Twitter or link to my posts there, I should receive notifications here and can show those replies as comments on my posts.
    You’re welcome to subscribe to or follow my content in any manner or on any platform you prefer. However, keep in mind that the canonical copies live on this site and are the most complete. You’d have to follow me on a plethora of sites to be able to follow even a small portion of my online content output, and even then you’ll find that this is the only site with complete copies of all of it.

     Firehose
     Microblog
     Linkblog
     

     Articles
     Notes
     Replies
     Photos
     Checkins
     Reads
     Watches
     Listens
     Bookmarks
     Favorites
     Likes
     Reposts
     Itches
     Issues
     RSVPs
     Wishlist
     Books
     Annotation
     Microcast
     Follows
     Jams
     Acquisition
     Audio
     Video
     Quotes
     Chat
     Recipes
     Food Diary
     Eat
     Drink
     Exercise
     Plays
     Chickens
     IndieWeb Podcast
     
     

    Reply

13. This Article was mentioned on luisquintanilla.me

    Reply

14. @ljquintanilla @sergey_tihon Looks like it might also qualify for the IndieWeb Gift Calendar too: https://indieweb.org/2021-12-indieweb-gift-calendar
    (Got a Webmention from your post BTW. Congratulations!)

    Syndicated copies:

    Reply

15. Hi Chris,

    Webmentions sounds pretty cool. I do worry how you would filter out spam mentions though. Would PVA validated accounts be needed perhaps? I guess there is always some level of spam that gets through in any large system..

    Take care
    James

    Reply

    1. Most big platforms have tools and methods for handling spam already (eg. Akismet for WordPress and other platforms). Some have been working at a vouch protocol as an additional layer of protection as well. Anecdotally I find that that I don’t get a lot of spam and by design the spec mitigates spam from the start, or at least makes it cost something.

       Reply

16. I’ve added Webmention support to the posts on this blog.
    Webmentions are a method for websites to know that they’ve been linked to (or mentioned) from elsewhere on the web.

    Webmention is a web standard for mentions and conversations across the web, a powerful building block that is used for a growing federated network of comments, likes, reposts, and other rich interactions across the decentralized social web.
    When you link to a website, you can send it a Webmention to notify it. If it supports Webmentions, then that website may display your post as a comment, like, or other response, and presto, you’re having a conversation from one site to another!

    It depends on a couple of things being in place for it all to work, but I’ve implemented the basics to fetch and display any mentions that have been detected by the webmention.io service.
    I have already been using Github Issues-powered commenting for the past couple of years, so I took the time to consolidate comments and Webmentions in to a single chunk of “interactions” functionality to fetch, cache, and render any comments or Webmentions. This is all done with native JS and could probably be improved further with a framework like Vue.js, but it works fine for now.
    I’m using brid.gy to recieve Webmentions from Twitter and Reddit interactions via webmention.io — this will mean that if somebody shares/likes/retweets a link to one of my blog posts on either platform it will display that here below the post.
    I’m using webmention.app and IFTTT to automatically try and send webmentions to sites I link to from within my posts.
    As you can see it’s a bit complicated, and it feels like it’s held together with duct tape in places, but for now it works!
    Lots of others have written about how they’ve implemented Webmentions on their sites, and these write-ups were really useful when arriving at my own implementation.
    So to share the love, here are some links to those posts:

    Webmentions – Phil Gyford
    Webmentions for your Static Site – Rowan Manning
    Using Web Mentions in a static site (Hugo) – Paul Kinlan
    Adding Webmention Support to a Static Site – Keith J. Grant
    Adding Webmentions to My Static Hugo Site – Ana Ulin
    Using Webmentions in Eleventy – Max Böck
    Webmentions: Enabling Better Communication on the Internet – Chris Aldrich
    Add Webmention support to your website in ten minutes – Daniel Aleksandersen
    Sending your First Webmention from Scratch – Aaron Parecki
    Implementing Webmention on a static website – Deluvi
    Adding Webmention Support from Scratch – Dwayne Harris
    Social media responses on a Jekyll site using webmentions – James Dinsdale
    Adding webmentions to my blog – Sebastian De Deyne
    A Brief Look at WebMention – Ben Shi
    IndieWebify.Me

    And that’s about it really. I’ll be tweeting a link to this post once it’s published and then any replies or likes will hopefully appear at the bottom of the page.

    Reply

17. Lurking
    Yesterday I was catching up on chat logs and ran across a stub for lurking on the IndieWeb wiki. I cleaned up the formatting a bit and added some additional material. Later Ton Zijlstra dropped a link to his excellent article from 2004 on the topic: Lurking and Social Networks (though honestly, I first came by the link courtesy of our good friend Jeremy Cherfas who added it to the wiki page).

    Lurking is the quiet watching/listening that what many people of the web do in chat rooms in order to begin gauging culture, learning jargon or lingo, and other community norms or unspoken principles before diving in to interact on a more direct level with other participants.

    While the word lurking can have a very negative connotation, online it often has a much more positive one, especially in regard to the health and civility of the commons. Rather than rehash what Ton has done an excellent job of doing, I won’t go into the heavy details and history of online lurking, but instead, let’s take a look at where it isn’t in today’s social media landscape.
    Twitter
    Since 2004, Twitter and a slew of other social media has popped up on the scene and changed many of our prior behaviors concerning lurking. In particular, Twitter’s interface has made it far easier to either like/favorite a post or retweet it.
    In comparison the the preceding era of the blogosphere represented by Tons’ post, Twitter has allowed people to send simple notifications back and forth about each others’ posts indicating a lower bar of interaction than writing a thoughtful and measured comment. Now instead of not knowing about dozens, hundreds, or thousands of lurkers, a (micro)blogger would more quickly know who many more of their readers were because they were liking or resharing their content. Naturally there are still many more potential lurkers who don’t interact with one’s posts this way, but these interactions in some way are like adding fuel to the fire and prompt the writer to continue posting because they’re getting some feedback that indicates they’ve got an audience. Twitter has dramatically lowered the bar for lurkers and made it more socially acceptable for them to make themselves known.
    Twitter image from the collection Social Decay by Andrei Lacatsu
    Of course, not all is rosy and happy in Twitterland as a result of this lowering the social bar. Because it’s so easy to follow almost anyone and interact with them, naturally everyone does. This means that while before one may have lurked a blog for weeks or months before posting a response of any sort, people are now regularly replying to complete strangers without an resistance whatsoever. While this can be valuable and helpful in many instances, oftentimes it comes off as rudely as if one butted into the private conversation of strangers at a public gathering. At the farther end of the spectrum, it’s also much easier for trolls to tag and target unsuspecting victims. As a result, we have the dumpster fire that Twitter has become in the past several years for many of its users.
    The problem for the continued health of the commons is how can we maintain a bar for online lurking, but still provide some feedback? How can we keep people from shouting and yelling at passer-by from their proverbial front porches or vice-versa? How might we encourage more positive lurking online before directly jumping into a conversation? 
    Read Posts and Private Posts
    For several years now, as a part of the IndieWeb movement, I’ve been more directly controlling my online identity and owning my content by using my own domain name and my own website (boffosocko.com). While I still use Twitter, I’m generally only reading content from it via a feed reader. When I post to or interact with it, I’m always publishing my content on my own website first and syndicating a copy to Twitter for those who don’t own their online identities or content and (sadly) rely on Twitter to do that for them. 
    Within this setting, since roughly late 2016, I’ve been posting almost all of what I read online or in books, magazines, or newspapers on my own website. These read posts include some context and are often simply composed of the title of the article, the author, the outlet, a summary/synopsis/or first paragraph or two to remind me what the piece was about, and occasionally a comment or two or ten I had on the piece.
    An example read post with context from my website at https://boffosocko.com/2019/06/02/lurking-and-social-networks-ton-zijlstra/
    In tandem with these posts, I’m also sending webmentions to the websites of those pieces. These (experimental) read webmentions are simply notifications to the originating site that I’ve read their piece. In our prior framing of lurking or Twitter, I’m sending them the simplest notification I can think of to say, “I’m here lurking. I’m reading or looking at your work.”
    I’m not saying that I liked it, favorited it, disliked it, bookmarked it, commented on it,  or anything else, but simply that I read it, I consumed it, I spent the time to interact with it. But in contrast with Ton’s older method of looking at server logs to see what kind of traffic his posts are getting, he can see exactly who I am and visit my website in return if he chooses. (Ton’s old method of sifting through those logs was certainly not a fun experience and the data was usually relatively anonymous and useless.) These newer read notifications could potentially give him a much richer idea of who his (lurking) audience actually is. Then when someone shows up with a comment or reply, it’s not completely from out of the dark: they’ve previously indicated that they’re at least somewhat aware of the context of a potentially broader conversation on his site.
    These read notifications are semantically different from likes, favorites, or even bookmarks on other platforms. In fact many platforms like Twitter, which has moved from “stars” (with the semantic idea of a favorite) to “hearts” (with the semantic idea of a like), have so few indicators of reaction to a post that the actual meaning of them has been desperately blurred. Personally I’ll use Twitter’s like functionality variously to mean: “I’m bookmarking this (or the linked article within it) for reading later”, “I like this post”, “I’ve read this post”, or even “I’m acknowledging receipt of your reply to me”. That’s just too much meaning to pack into a silly little heart icon.
    Because I’m using my own website over which I have complete control, I can make it do a better job of unpacking some of this semantic tom-foolery. I’ve written about it a bit in the past if you care to see some of the details: Thoughts on linkblogs, bookmarks, reads, likes, favorites, follows, and related links. See also: the read-posts tag on this site.
    If they choose, some website owners display these read post notifications in one or more ways. Some sites like Aaron Parecki’s or Jeremy Keith’s will show my interactions as bookmarks. Others, primarily WordPress-based websites that support Webmention (via plugin), will actually show these interactions in their comment sections under the heading “Read” and display my photo/avatar as an indicator that I’ve interacted with that post. In the case of read posts on which I’ve written one or more comments, the receiving site also has the option of showing my interaction not as a read/bookmark intent, but could also show my comments as a reply to their post. I’ve written a bit about this and its potential for large news outlets before in Webmentions: Enabling Better Communication on the Internet for A List Apart. There are also some older legacy sites that might show my interactions as a trackback or pingback, but these seem few and far between these days, particularly as those systems are major targets for spam and the Webmention protocol has a richer interaction/display model.
    How Jeremy Keith displays shares, likes, and bookmarks (including my read post) in the comment section of his website. The display of a read post on ColoradoBoulevard.net
    A new itch
    But as I think about these read posts, lurking, and being more civil on the internet, I have a new itch for some functionality I’d like to add to my website. I very frequently use my website as a digital commonplace book to collect links of things I’ve read, watched, and listened to. I’ll collect quotes, highlights, and even my own marginalia. As I mentioned above, my read posts sometimes have comments, and quite often those comments are really meant just for me and not for the author of the original post. In many cases, when my comments may be too egregious, sensitive, or perhaps even insulting to the original author, I’ll make these posts private so that only I can see them on my site.  Of course when they’re private, no notifications are sent to the site at the other end of the line.
    Sometimes I would like to be able to send a read notification to the site, but also keep my commentary privately to myself. This allows me to have my notes on the piece and be highly critical without dragging down the original author or piece who I may not know well or the audience of that same piece which I haven’t properly lurked (in the positive community-based sense indicated above) to be as intelligently and sensitively commenting as I would otherwise like. Thus I’d like to build in some functionality so that I can publicly indicate I’ve read a piece (and send a notification), but also so that I can keep the commentary on my read private to either myself or a smaller audience.
    I suspect that I can do this in a variety of meta-fields on my website which aren’t shown to the public, but which might be shown to either myself or logged in users. In some sense, this is a subset of functionality which many in the IndieWeb have been exploring recently around the ideas of private posts or by limiting the audience of a post. In my case, I’m actually looking at making a post public, but making smaller sub-portions of it private.
    To begin with, I’ll most likely be looking at doing this at a small scale just for myself and my commonplace book, as I can definitely see second and third-order effects and a variety of context collapse issues when portions of posts are private, but others who may be privy to them are commenting on those pieces from the perspective of their public spheres which may not be as private or closed off as mine. i.e.: While I may have something marked as private, privy readers will always have the option of copy/pasting it and dragging it out into the public.
    For those interested, I’ll briefly note that Sebastiaan Andeweg just wrote Private posts: the move of the checkins which has some useful and related background to private posts. (Of course I remember exactly when I read it.) I also highly suspect there will be a private posts related session(s) at the upcoming IndieWeb Summit in Portland in June (tickets are still available). I’m interested to see what others come up with on this front.

    Reply

Mentions

• 💬 Lurking, Twitter, The Commons, and Private Posts | Chris Aldrich
• 💬 Adding support for Webmentions | The blog of Max Glenister
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich