IndieWeb Collection

53 thoughts on “IndieWeb Collection”

1. Why we transitioned from Medium back to our own blog by Josh Pigford (Baremetrics)

   Where to publish something has becoming a difficult decision for a lot of businesses. You read so many stories about using various channels to distribute content and grow traffic, it’s hard to know what does and doesn’t work. Medium, in particular, has become a major player in the world of startup content, but is it really that great?

   […]

   The numbers just didn’t make sense. Yes, I could put more into Medium and try to build up readership even more. The guys at Basecamp regularly get 250k+ views on their content. But doing that helps Medium the most in the long run. They’ve been fumbling left and right trying to figure out how to make Medium sustainable, and I’m just not convinced they’ll always do what’s best for us and our business.

   Switching back

   Now I didn’t want to throw out distribution on Medium entirely. There can definitely be some benefit to syndicating content there. It’s essentially another distribution channel to expose people to our content.

   So we needed a game plan on how we could still make use of Medium as a distribution channel without cannibalizing our own readership or SEO work.

   This is 100% on the mark, you should definitely own your own content. Syndicating it out to Medium is a great idea, particularly when you can get a rel=”canonical” tag for the original on Medium. Incidentally Medium has their own WordPress plugin that will allow you to quickly and easily syndicate your site’s content directly to Medium without needing to separately import it. It’s also available on a per post basis.
   But, even with this, you’re only getting 50% of the value of having your own website because you’ve only got one way communication out. Next you’ll need communication back in. What if I said you could get a lot of the comments, likes, and interactions from those other silos back into your website too? This way the conversations others are having relating to your content also come back to your site and enrich it there? What if you could own all (or almost all) of the conversation around your content?
   Think about it, what if there was an @mention functionality that worked from website to website instead of being stuck inside Twitter, Facebook, Google+, Instagram, Flickr etc.? Interestingly, it exists! And you can set it up for free with last year’s new W3C Webmention protocol which already has WordPress plugins ready to go. Roughly for WordPress you’ll need the Webmentions plugin, the Semantic Linkbacks plugin, the Syndication Links plugin, a few strategically placed rel=”me” tags on your site, (maybe some tweaks to your microformats on your theme), and a free Brid.gy account. Details for setting it up can be found on the WordPress pages of the indieweb.org website. I suspect if you’re strong enough to have figured out the tech for your article, you could probably have it up and running in under an hour or so. Then instead of feeding content from your blog to the black hole of social media, you could have actual two-way communication with many social silos! Now you won’t need to pay as much attention to those other sites as you can use your WordPress site as an “app” to interact with them instead.
   I’m happy to help walk you through it if you’re interested and need help. My own personal site has some documentation of some of the above as well as examples of how it works.
   In some sense, hopefully this post on my site will be an interesting exemplar. I own it and “loaned” or syndicated copies to Disqus and Twitter. Comments, likes and reposts you make to the Twitter copy will automatically be ported back here after the fact using Brid.gy. (Sadly, Disqus isn’t supported–yet.)
   Syndicated copies to:
   
   
   

   Author: Chris Aldrich

   I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.


   I’m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.
   View all posts by Chris Aldrich

   Reply

2. To PESOS or to POSSE? by Dries Buytaert (dri.es)

   Comparing two different approaches that help you take control back over your own data on the web.
   […]
   The goal of this analysis was to understand the pros and cons of how I can own my own content on https://dri.es. While PESOS would be much easier to implement, I decided to go with POSSE. My next step is to figure out my “POSSE plan”; how to quickly and easily share status updates on my Drupal site, how to syndicate them to 3rd party services, how to re-organize my mailing list and my RSS feed, and more. If you have any experience with implementing POSSE, feel free to share your takeaways in the comments.

   What a fantastic breakdown of the concepts of POSSE vs. PESOS, though to be sure there are also additional variations for syndicating, cross-posting, or moving content around to reach various audiences.
   One thing that I think you’ve only briefly touched upon is the ability to also have likes, replies/comments, etc. also come back to your site as native content via webmentions. I’ve been able to get rid of five apps and their incessant notifications and trim it all back to just using my own site to handle everything instead. Using something I choose to use instead of something I’m forced to, while also owning my data, is really very liberating.
   Like you, I too have always wanted to own my own content on the web, and there are some easier and some harder methods. Not being as strong a developer as many, I’ve taken a more hybrid approach to things which is still evolving. To some extent I began at the easy end with some PESOS based workflows and relying on simple tools like IFTTT.com to at least begin owning all my content. For many content management systems, this is nearly dead easy, and could even be done with something as simple and flexible as Tumblr without much, if any, coding experience.
   Over time, as I’ve been able, I’ve  moved to a more direct POSSE method as either I or, more often, others have managed to master making the simple posting interfaces easier and easier. I think in the end, POSSE is the strongest of the methods, so that has always been my ultimate goal.
   From a Drupal-centric approach, you might be able to gain an interesting perspective on the multitude of ways POSSE/PESOS can be done by looking at the various ways that are available in WordPress ecosystem. It’s probably easy to discern that some are far easier than others based on one’s facility with coding. In general, I’ve noticed that the more freedom and flexibility a particular method or plugin has, the longer it takes to code and/or configure. The less flexibility a plugin offers, the easier. (So one could compare something like SNAP at the more comprehensive/difficult end to something simpler like JetPack for POSSE.) The difficulty is in the administrative tax of keeping up with the panoply of social media platform APIs to keep things working smoothly over time, particularly when you want your posts to be able to leverage the broad arrays of posting options and display outputs platforms like Facebook and Twitter offer. The other difficult questions can sometimes be: am I just replacing one or two social platforms, or am I trying to replace 20? and am I doing them with one plugin or with 20? and finally, how DRY is that process? Sometimes manually cutting and pasting is just as good.
   As you do, I write first and foremost for myself and then a distant second for reaction and conversation with others. Thus I think of my personal site as just that: personal. To some extent it’s a modern day version of a commonplace book where I collect a variety of thoughts in a variety of means, while still trying somewhat to keep it in an outer facing form to look what people might expect a site to look like. This means that I have a good number more than the traditional types of posts most social media sites have. I try to own all my own bookmarks and even post what I’m reading both online and in physical form. I keep highlights and annotations of things I find interesting. I naturally keep longer posts, status updates, and photos like many. I even log scrobbles of music and podcasts I listen to as well as film and television I watch. Interestingly there’s a tremendous amount I only publish privately to myself or a small circle of others that’s hidden on my site’s back end. Depending on how far and deep you want your experience to go you might want to consider how all these will look or be represented on your site. To  a great extent, I think that WordPress’s attempt to copy Tumblr (text, photo, quote, link, chat, audio, video) with their Post Formats was interesting, it just didn’t go far enough. Naturally, this may take a different form for you depending on whether you’re building just for yourself or if you’re planning something more modular for the larger Drupal community to leverage.
   A few of the post types my website supports.The best part of all this is that I’ve not done any of it alone. While I try to maintain a list of some of my experiments to help others (you’ll probably appreciate the ones on mobile posting and RSS based on your outline), there’s also a wealth of other examples on the IndieWeb wiki and a terrifically stellar group of people around almost 24-7 in the IndieWeb chat to help spur me along. I’ll echo Tantek’s welcome to what I think is a more thoughtful and vibrant open web.
   I hope others also find these resources so they’re not fumbling around in the dark as I was for so long. Since you’re obviously building in Drupal, I can recommend you take a look at some of the examples provided by the WordPress and the Known communities which Ben referenced. Since they’re all .php based and open-source, you may get further faster in addition to being able to iterate upon and improve their work. Many of the developers are frequently in the IndieWeb chat and I’m sure would be happy to help with ideas and pitfalls they came across along the way.
   Like others, I’m posting my reply first on my own website, and manually cross-posting it to yours (manually until you support Webmention–perhaps via the Vinculum plugin?) as well as automatically to Twitter and others.
   ​​​
   Syndicated copies to:
   
   
   
   

   Author: Chris Aldrich

   I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.


   I’m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.
   View all posts by Chris Aldrich

   Syndicated copies:

   Reply

3. What a fantastic breakdown of the concepts of POSSE vs. PESOS, though to be sure there are also additional variations for syndicating, cross-posting, or moving content around to reach various audiences.
   One thing that I think you’ve only briefly touched upon is the ability to also have likes, replies/comments, etc. also come back to your site as native content via webmentions. I’ve been able to get rid of five apps and their incessant notifications and trim it all back to just using my own site to handle everything instead. Using something I choose to use instead of something I’m forced to, while also owning my data, is really very liberating.
   Like you, I too have always wanted to own my own content on the web, and there are some easier and some harder methods. Not being as strong a developer as many, I’ve taken a more hybrid approach to things which is still evolving. To some extent I began at the easy end with some PESOS based workflows and relying on simple tools like IFTTT.com to at least begin owning all my content. For many content management systems, this is nearly dead easy, and could even be done with something as simple and flexible as Tumblr without much, if any, coding experience.
   Over time, as I’ve been able, I’ve  moved to a more direct POSSE method as either I or, more often, others have managed to master making the simple posting interfaces easier and easier. I think in the end, POSSE is the strongest of the methods, so that has always been my ultimate goal.
   From a Drupal-centric approach, you might be able to gain an interesting perspective on the multitude of ways POSSE/PESOS can be done by looking at the various ways that are available in WordPress ecosystem. It’s probably easy to discern that some are far easier than others based on one’s facility with coding. In general, I’ve noticed that the more freedom and flexibility a particular method or plugin has, the longer it takes to code and/or configure. The less flexibility a plugin offers, the easier. (So one could compare something like SNAP at the more comprehensive/difficult end to something simpler like JetPack for POSSE.) The difficulty is in the administrative tax of keeping up with the panoply of social media platform APIs to keep things working smoothly over time, particularly when you want your posts to be able to leverage the broad arrays of posting options and display outputs platforms like Facebook and Twitter offer. The other difficult questions can sometimes be: am I just replacing one or two social platforms, or am I trying to replace 20? and am I doing them with one plugin or with 20? and finally, how DRY is that process? Sometimes manually cutting and pasting is just as good.
   As you do, I write first and foremost for myself and then a distant second for reaction and conversation with others. Thus I think of my personal site as just that: personal. To some extent it’s a modern day version of a commonplace book where I collect a variety of thoughts in a variety of means, while still trying somewhat to keep it in an outer facing form to look what people might expect a site to look like. This means that I have a good number more than the traditional types of posts most social media sites have. I try to own all my own bookmarks and even post what I’m reading both online and in physical form. I keep highlights and annotations of things I find interesting. I naturally keep longer posts, status updates, and photos like many. I even log scrobbles of music and podcasts I listen to as well as film and television I watch. Interestingly there’s a tremendous amount I only publish privately to myself or a small circle of others that’s hidden on my site’s back end. Depending on how far and deep you want your experience to go you might want to consider how all these will look or be represented on your site. To  a great extent, I think that WordPress’s attempt to copy Tumblr (text, photo, quote, link, chat, audio, video) with their Post Formats was interesting, it just didn’t go far enough. Naturally, this may take a different form for you depending on whether you’re building just for yourself or if you’re planning something more modular for the larger Drupal community to leverage.
   A few of the post types my website supports.
   The best part of all this is that I’ve not done any of it alone. While I try to maintain a list of some of my experiments to help others (you’ll probably appreciate the ones on mobile posting and RSS based on your outline), there’s also a wealth of other examples on the IndieWeb wiki and a terrifically stellar group of people around almost 24-7 in the IndieWeb chat to help spur me along. I’ll echo Tantek’s welcome to what I think is a more thoughtful and vibrant open web.
   I hope others also find these resources so they’re not fumbling around in the dark as I was for so long. Since you’re obviously building in Drupal, I can recommend you take a look at some of the examples provided by the WordPress and the Known communities which Ben referenced. Since they’re all .php based and open-source, you may get further faster in addition to being able to iterate upon and improve their work. Many of the developers are frequently in the IndieWeb chat and I’m sure would be happy to help with ideas and pitfalls they came across along the way.
   Like others, I’m posting my reply first on my own website, and manually cross-posting it to yours (manually until you support Webmention–perhaps via the Vinculum plugin?) as well as automatically to Twitter and others.
   ​​​

   Syndicated copies:

   • googleplus
   • website

   Reply

4. This week, using the magic of open web standards, I was able to write an issue post on my own website, automatically syndicate a copy of it to GitHub, and later automatically receive a reply to the copy on GitHub back to my original post as a comment there. This gives my personal website a means of doing two way communication with GitHub.
   This functionality is another in a long line of content types my website is able to support so that I’m able to own my own content, yet still be able to interact with people on other websites and social media services. Given the number of social sites I’ve seen disappear over the years (often taking my content with them), this functionality gives me a tremendously larger amount of control and ownership over my web presence and identity while still allowing me to easily communicate with others.
   In this post I wanted to briefly sketch what I’ve done to enable this functionality, so others who are so inclined can follow along to do the same thing.
   Setting up WordPress to syndicate to GitHub
   I’ll presume as a first step that one has both a GitHub account and a self-hosted WordPress website, though the details will also broadly apply to just about any content management system out there that supports the web standards mentioned.
   Register your GitHub account and your website with Bridgy
   Ryan Barrett runs a fantastic free open sourced service called Bridgy. To use it you’ll need the microformat rel=​​​“me” links on both your GitHub account and your website’s homepage that point at each other.  GitHub will do most of the work on its side for you simply by adding the URL of your website to the URL field for your GitHub account at https://github.com/settings/profile. Next on your website’s homepage, you’ll want to add a corresponding rel=​​​​​“me” link from your website to your GitHub account.
   In my case, I have a simple widget on my homepage with roughly the following link:<a href="https://github.com/username">GitHub</a>
   in which I’ve replaced ‘username’ with my own GitHub username. There are a variety of other ways to add a rel=​​​​​“me” link to your webpage, some of which are documented on the IndieWeb wiki.
   Now you can go to Brid.gy and under “Connect your accounts” click on the GitHub button. This will prompt you to sign into GitHub via oAuth if you’re not already logged into the site. If you are already signed in, Brid.gy will check that the rel=​​​​​“me” links on both your site and your GitHub account reciprocally point at each other and allow you to begin using the service to pull replies to your posts on GitHub back to your website.
   To allow Brid.gy to publish to GitHub on your behalf (via webmention, which we’ll set up shortly), click on the “Publish” button.
   Install the Webmention Plugin
   The underlying technology that allows the Bridgy service to both publish on one’s behalf as well as for the replies from GitHub to come back to one’s site is an open web standard known as Webmention. WordPress can quickly and easily support this standard with the simple Webmention plugin that can be downloaded and activated on one’s site without any additional configuration.
   For replies coming back from GitHub to one’s site it’s also recommended that one also install and activate the Semantic Linkbacks Plugin which also doesn’t require any configuration. This plugin provides better integration and UI features in the comments section of one’s website.
   Install Post Kinds Plugin
   The Post Kinds Plugin is somewhat similar to WordPress’s Post Formats core functionality, it just goes the extra mile to support a broader array of post types with the appropriate meta data and semantic markup for interacting with Bridgy, other web parsers, and readers.
   Download the plugin, activate it, and in the plugin’s settings page enable the “Issue” kind. For more details on using it, I’ve written about this plugin in relative detail in the past.
   Install Bridgy Publish Plugin
   One can just as easily install the Bridgy Publish Plugin for WordPress and activate it. This will add a meta box to one’s publishing dashboard that, after a quick configuration of which social media silos one wishes to support, will allow one to click a quick checkbox to automatically syndicate their posts.
   Install the Syndication Links Plugin
   The Syndication Links plugin is also a quick install and activate process. You can modify the settings to allow a variety of ways to display your syndication links (or not) on your website if you wish.
   This plugin will provide the Bridgy Publish Plugin a place to indicate the permalink of where your syndicated content lives on GitHub. The Bridgy service will use this permalink to match up the original content on your website and the copy on GitHub so that when there are replies, it will know which post to send those replies to as comments which will then live on your own website.
   Post away
   You should now be ready to write your first issue on your website, cross post it to GitHub (a process known in IndieWeb parlance as POSSE), and receive any replies to your GitHub issue as comments back to your own website.
   Create a new post.
   In the “Kinds” meta box, choose the “Issue” option.
   Kinds meta box with “Issue” option chosen.Type in a title for the issue in the “Title” field.
   In the “Response Properties” meta box, put the permalink URL of the Github repopository for which you’re creating an issue. The plugin should automatically process the URL and import the repository name and details.
   The “Response Properties” meta box.In the primary editor, type up any details for the issue as you would on GitHub in their comment box. You can include a relatively wide variety of custom symbols and raw html including
   and with code samples which will cross-post and render properly.
   In the GitHub meta box, select the GitHub option. You can optionally select other boxes if you’re also syndicating your content to other services as well. See the documentation for Bridgy and the plugin for how to do this.
   Bridgy Publish meta box with GitHub chosen.Optionally set any additional metadata for your post (tags, categories, etc.) as necessary.
   Publish your post.
   On publication, your issue should be automatically filed to the issue queue of the appropriate GitHub repo and include a link back to your original (if selected). Your post should receive the syndicated permalink of the issue on GitHub and be displayed (depending on your settings) at the bottom of your post.
   Syndication Links Plugin will display the location of your syndicated copies at the bottom of your post.When Bridgy detects future interactions with the copy of your post on GitHub, it will copy them and send them to your original post as a webmention so that they can be displayed as comments there.
   An example of a comment sent via webmention from GitHub via Brid.gy. It includes a permalink to the comment as well as a link to the GitHub user’s profile and their avatar.If you frequently create issues on GitHub like this you might want a slightly faster way of posting. Toward that end, I’ve previously sketched out how to create browser bookmarklets that will allow you one click post creation from a particular GitHub repo to speed things along. Be sure to change the base URL of your website and include the correct bookmarklet type of “issue” in the code.
   The Post Kinds plugin will also conveniently provide you with an archive of all your past Issue posts at the URL http://example.com/kind/issue/, where you can replace example.com with your own website. Adding feed/ to the end of that URL provides an RSS feed link as well. Post Kinds will also let you choose the “Reply” option instead of “Issue” to create and own your own replies to GitHub issues while still syndicating them in a similar manner and receive replies back.
   Other options
   Given the general set up of the variety of IndieWeb-based tools, there are a multitude of other ways one can also accomplish this workflow (both on WordPress as well as with an infinity of other CMSes). The outline I’ve provided here is one of the quickest methods for beginners that will allow a relatively high level of automation and almost no manual work.
   One doesn’t necessarily need to use the Post Kinds Plugin, but could manually insert all the requisite HTML into their post editor to accomplish the post side of things via webmention. (One also has the option to manually syndicate the content to GitHub by cutting and pasting it as well.) If doing things manually this way is desired, then one will need to also manually provide a link to the syndicated post on GitHub into their original so that Bridgy can match up the copy and the original to send the replies via webmention.
   More details on how to use Bridgy with Github manually in conjunction with WordPress or other CMSes can be found here: https://brid.gy/about#github-issue-comment
   Further steps
   If you’ve followed many of these broad steps, you’ve given already given yourself an incredibly strong IndieWeb-based WordPress installation. With a minimal amount of small modifications you can also use it to dovetail your website with other social services like Twitter, Facebook, Flickr, Instagram, Google+ and many others. Why not take a quick look around on the IndieWeb wiki to see what other magic you can perform with your website!
   I’ve documented many of my experiments, including this one, in a collection of posts for reference.
   Help
   If you have questions or problems, feel free to comment below or via webmention using your own website. You can also find a broad array of help with these plugins, services, and many other pieces of IndieWeb technology in their online chat rooms.​​​​​​​​

   Respond via Twitter:
   Reply
   Repost
   Like

   Syndicated copies to:
   
   
   
   
   
   

   Author: Chris Aldrich

   I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.


   I’m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.
   View all posts by Chris Aldrich

   Syndicated copies:

   Reply

5. This week, using the magic of open web standards, I was able to write an issue post on my own website, automatically syndicate a copy of it to GitHub, and later automatically receive a reply to the copy on GitHub back to my original post as a comment there. This gives my personal website a means of doing two way communication with GitHub.
   This functionality is another in a long line of content types my website is able to support so that I’m able to own my own content, yet still be able to interact with people on other websites and social media services. Given the number of social sites I’ve seen disappear over the years (often taking my content with them), this functionality gives me a tremendously larger amount of control and ownership over my web presence and identity while still allowing me to easily communicate with others.
   In this post I wanted to briefly sketch what I’ve done to enable this functionality, so others who are so inclined can follow along to do the same thing.
   Setting up WordPress to syndicate to GitHub
   I’ll presume as a first step that one has both a GitHub account and a self-hosted WordPress website, though the details will also broadly apply to just about any content management system out there that supports the web standards mentioned.
   Register your GitHub account and your website with Bridgy
   Ryan Barrett runs a fantastic free open sourced service called Bridgy. To use it you’ll need the microformat rel=​​​“me” links on both your GitHub account and your website’s homepage that point at each other.  GitHub will do most of the work on its side for you simply by adding the URL of your website to the URL field for your GitHub account at https://github.com/settings/profile. Next on your website’s homepage, you’ll want to add a corresponding rel=​​​​​“me” link from your website to your GitHub account.
   In my case, I have a simple widget on my homepage with roughly the following link:
   <a href="https://github.com/username">GitHub</a>
   in which I’ve replaced ‘username’ with my own GitHub username. There are a variety of other ways to add a rel=​​​​​“me” link to your webpage, some of which are documented on the IndieWeb wiki.
   Now you can go to Brid.gy and under “Connect your accounts” click on the GitHub button. This will prompt you to sign into GitHub via oAuth if you’re not already logged into the site. If you are already signed in, Brid.gy will check that the rel=​​​​​“me” links on both your site and your GitHub account reciprocally point at each other and allow you to begin using the service to pull replies to your posts on GitHub back to your website.
   To allow Brid.gy to publish to GitHub on your behalf (via webmention, which we’ll set up shortly), click on the “Publish” button.
   Install the Webmention Plugin
   The underlying technology that allows the Bridgy service to both publish on one’s behalf as well as for the replies from GitHub to come back to one’s site is an open web standard known as Webmention. WordPress can quickly and easily support this standard with the simple Webmention plugin that can be downloaded and activated on one’s site without any additional configuration.
   For replies coming back from GitHub to one’s site it’s also recommended that one also install and activate the Semantic Linkbacks Plugin which also doesn’t require any configuration. This plugin provides better integration and UI features in the comments section of one’s website.
   Install Post Kinds Plugin
   The Post Kinds Plugin is somewhat similar to WordPress’s Post Formats core functionality, it just goes the extra mile to support a broader array of post types with the appropriate meta data and semantic markup for interacting with Bridgy, other web parsers, and readers.
   Download the plugin, activate it, and in the plugin’s settings page enable the “Issue” kind. For more details on using it, I’ve written about this plugin in relative detail in the past.
   Install Bridgy Publish Plugin
   One can just as easily install the Bridgy Publish Plugin for WordPress and activate it. This will add a meta box to one’s publishing dashboard that, after a quick configuration of which social media silos one wishes to support, will allow one to click a quick checkbox to automatically syndicate their posts.
   Install the Syndication Links Plugin
   The Syndication Links plugin is also a quick install and activate process. You can modify the settings to allow a variety of ways to display your syndication links (or not) on your website if you wish.
   This plugin will provide the Bridgy Publish Plugin a place to indicate the permalink of where your syndicated content lives on GitHub. The Bridgy service will use this permalink to match up the original content on your website and the copy on GitHub so that when there are replies, it will know which post to send those replies to as comments which will then live on your own website.
   Post away
   You should now be ready to write your first issue on your website, cross post it to GitHub (a process known in IndieWeb parlance as POSSE), and receive any replies to your GitHub issue as comments back to your own website.
   Create a new post.
   In the “Kinds” meta box, choose the “Issue” option.
   Kinds meta box with “Issue” option chosen.
   Type in a title for the issue in the “Title” field.
   In the “Response Properties” meta box, put the permalink URL of the Github repopository for which you’re creating an issue. The plugin should automatically process the URL and import the repository name and details.
   The “Response Properties” meta box.
   In the primary editor, type up any details for the issue as you would on GitHub in their comment box. You can include a relatively wide variety of custom symbols and raw html including
   and with code samples which will cross-post and render properly.
   In the GitHub meta box, select the GitHub option. You can optionally select other boxes if you’re also syndicating your content to other services as well. See the documentation for Bridgy and the plugin for how to do this.
   Bridgy Publish meta box with GitHub chosen.
   Optionally set any additional metadata for your post (tags, categories, etc.) as necessary.
   Publish your post.
   On publication, your issue should be automatically filed to the issue queue of the appropriate GitHub repo and include a link back to your original (if selected). Your post should receive the syndicated permalink of the issue on GitHub and be displayed (depending on your settings) at the bottom of your post.
   Syndication Links Plugin will display the location of your syndicated copies at the bottom of your post.
   When Bridgy detects future interactions with the copy of your post on GitHub, it will copy them and send them to your original post as a webmention so that they can be displayed as comments there.
   An example of a comment sent via webmention from GitHub via Brid.gy. It includes a permalink to the comment as well as a link to the GitHub user’s profile and their avatar.
   If you frequently create issues on GitHub like this you might want a slightly faster way of posting. Toward that end, I’ve previously sketched out how to create browser bookmarklets that will allow you one click post creation from a particular GitHub repo to speed things along. Be sure to change the base URL of your website and include the correct bookmarklet type of “issue” in the code.
   The Post Kinds plugin will also conveniently provide you with an archive of all your past Issue posts at the URL http://example.com/kind/issue/, where you can replace example.com with your own website. Adding feed/ to the end of that URL provides an RSS feed link as well. Post Kinds will also let you choose the “Reply” option instead of “Issue” to create and own your own replies to GitHub issues while still syndicating them in a similar manner and receive replies back.
   Other options
   Given the general set up of the variety of IndieWeb-based tools, there are a multitude of other ways one can also accomplish this workflow (both on WordPress as well as with an infinity of other CMSes). The outline I’ve provided here is one of the quickest methods for beginners that will allow a relatively high level of automation and almost no manual work.
   One doesn’t necessarily need to use the Post Kinds Plugin, but could manually insert all the requisite HTML into their post editor to accomplish the post side of things via webmention. (One also has the option to manually syndicate the content to GitHub by cutting and pasting it as well.) If doing things manually this way is desired, then one will need to also manually provide a link to the syndicated post on GitHub into their original so that Bridgy can match up the copy and the original to send the replies via webmention.
   More details on how to use Bridgy with Github manually in conjunction with WordPress or other CMSes can be found here: https://brid.gy/about#github-issue-comment
   Further steps
   If you’ve followed many of these broad steps, you’ve given already given yourself an incredibly strong IndieWeb-based WordPress installation. With a minimal amount of small modifications you can also use it to dovetail your website with other social services like Twitter, Facebook, Flickr, Instagram, Google+ and many others. Why not take a quick look around on the IndieWeb wiki to see what other magic you can perform with your website!
   I’ve documented many of my experiments, including this one, in a collection of posts for reference.
   Help
   If you have questions or problems, feel free to comment below or via webmention using your own website. You can also find a broad array of help with these plugins, services, and many other pieces of IndieWeb technology in their online chat rooms.​​​​​​​​

   Respond via Twitter:
   Reply
   Repost
   Like

   Syndicated copies to:
   
   
   
   
   
   
   
   

   Syndicated copies:

   • googleplus

   Reply

6. A collection of articles, replies, and posts about IndieWeb philosophies and technologies by Chris Aldrich

   Source: IndieWeb Collection

   Reply

7. A user considers by Jeremy Cherfas (jeremycherfas.net) There’s a strain of thought going around that the IndieWeb is deliberately exclusionary. I don’t know why, and…

   Reply

8. 11:35 de la mañana. Track C en La Nave. WordCamp Madrid. Por fin llegó el día para el que llevo escribiendo en este blog los últimos 30 días. El momento de ver quién se va a subir al carro de la misión que les he encomendado. La #ResistenciaWCMadrid.
   Os he hablado todos estos días de muchas de las cosas que he contado -de manera más resumida- en los 25 minutos de mi charla. Aún así me gustaría hacer una pequeña transcripción inventada de lo que he hablado para poder enlazar a otras fuentes y que quede todo más completo. Así que aquí va mi exposición en versión escrita.

   Esta charla tiene una versión muy resumida que es exactamente su título. WordPress -que todos conocemos- no es solo para blogs -como bien sabéis-. Pero tenéis que haceros uno. Fin de la charla resumida.
   Pero vamos a ver si se puede rascar algo más, porque si no a ver qué hago con los otros 34 slides -que colgaré al final de este post sin falta-.
   Si esta charla fuera sobre Facebook en lugar de WordPress todo sería más fácil… porque ya tendría un análisis de vuestro perfil y sólo hablaría de lo que os fuera a gustar. O incluso porque habría creado una serie de fake news y unos anuncios para que vinierais a verme. Cosa que no he hecho. Y aún así aquí estáis.
   Si esta charla fuera sobre Google en lugar de WordPress todo sería más fácil también. Sólo tendría que prometeros un mejor posicionamiento en el ranking y consejos infalibles sobre SEO para que vinieseis. O en su defecto, llevaría semanas usando retargeting en anuncios persiguiéndoos para que estuvieses aquí sentados.
   Pero realmente esta charla no es sobre Facebook ni sobre Google ni sobre WordPress. Es una charla sobre vosotros. Sobre vosotros y sobre por qué tenéis que estar al mando de vuestra presencia online. Una presencia online cuyo mayor baluarte va a ser un blog, claro está.
   Esto así, en frío, un sábado por la mañana, puede sonar un poco aburrido.
   Pero si os digo… que los aquí presentes sois los elegidos para formar parte de la resistencia y tenéis una misión… Puede que la cosa cambie. La resistencia… una misión…
   Antes que nada vamos a volver atrás unos cuantos años. Hace muchos años (cada vez más) en Intenet reinaba el caos. Había blogs, había gifs que no pesaban más que unos pocos kilobytes, había directorios de páginas porque los buscadores aún no eran muy avanzados, había anillos de páginas por temáticas, había listas de correos, hablábamos por IRC, pocos se planteaban poner sus datos personales, nuestras webs estaban alojadas en Geocities y no en SiteGround o Dinahosting o GoDaddy…
   Efectivamente, cualquier tiempo pasado no fue necesariamente mejor. Y ojo, no quiero convertir esta charla en las batallitas del abuelo o nostalgia de tiempos pasados.
   Pero sí que hace falta saber de dónde venimos y qué ocurrió. Pequeñas startups, nacidas en garajes, en universidades, con un montón de millones de inversión se convirtieron en grandes corporaciones. Don’t be evil decían. Encuentra a tus amigos. Qué está pasando. Qué bonito todo. Todo gratis. Somos el producto dice la famosa frase, ¿y qué?
   Bueno, ahora mucha gente se está dando cuenta lo que supone todo eso. No “somos” el producto. Nuestros datos lo son. Y han empezado los problemas.
   Por nombrar unos pocos: filtraciones de datos privados (hola Mark), noticias falsas y manipulación (hola políticos), censura en redes sociales (hola algoritmos), abuso de anuncios y popups (excepto si son de los buenos, de los míos, claro), webs lentas y sobrecargadas (hola todos), criptominería, cookies que te vigilan, monopolios claves en el acceso a la información y hasta un aburrimiento y desidia generalizado al enfrentarse a todo esto. Gente que empieza a pensar que Internet no les aporta nada.
   ¿Estamos condenados a un futuro cada vez más oscuro?
   ¡No! El movimiento IndieWeb viene al rescate. Porque viendo el panorama, ¿quién quiere formar parte del orden establecido? Pero ¿qué es la IndieWeb?
   Por definición es una alternativa a la “web corporativa”, está centrada en las personas. Tiene una filosofía cuyo mayor mandamiento es que tu contenido es tuyo, que tienes el control absoluto del contenido y del formato y que te permite estar mejor conectado con todo el mundo -no sólo con los que usan Twitter, o Facebook-, gracias al modelo POSSE. Aquí tenéis un montón de artículos sobre la IndieWeb de Chris Aldrich.
   Tenemos una filosofía, pero ¿cómo vamos a luchar? Desde nuestra propia web hecha con WordPress. Pero llegan las dudas y las piernas que tiemblan.
   Pa’ qué quiero un blog si no tengo nada sobre lo que escribir. Pa’ qué quiero un blog si no tengo tiempo para escribir a diario. Pa’ qué quiero un blog si nadie me va a leer y es como si no lo hiciera. Pa’ qué quiero un blog si no va a valer de nada. Estoy seguro que más de uno se está planteando esas preguntas.
   Para todas tengo una respuesta rápida y concisa. Todo el mundo tiene algo sobre lo que escribir. Cualquier cosa que te guste. Lo que haces en tu día a día. Aquí todos tenéis alguna relación con WordPress. Muchos habéis viajado hasta aquí. Utilizáis cosas. Todo son temas.
   No hace falta escribir a diario. Yo lo he estado haciendo estos últimos 30 días antes de la charla y es agotador. A alguien le hubiera importado que escribiera dos veces a la semana. ¿Dos veces al mes? Escribe cuando puedas.
   ¿Nadie te va a leer? ¿Cuántos somos aquí? Venga ya… no va a valer de nada… ¿no habéis oído que estamos en una batalla? Los aquí sentados somos la #ResistenciaWCMadrid. Si etiquetáis vuestras publicaciones con este hashtag vuestros compañeros de batalla leeran vuestros posts. Ya tenéis el primer lector. Los primeros diez.
   Y es que aparte de darnos lectura a nosotros, tener tu blog y tu web personal tiene muchos beneficios. Por listar algunos que se me han ocurrido a mí y a Fernan (¿tenéis la entrada para la WCBilbao?): te da visibilidad, te permite contar quién eres y hacer llegar el mensaje que te apetezca. Te permite buscar tus propias dudas y mensajes si lo dejaste por escrito en un mismo sitio. Te permite mirar atrás y ver lo viejo que eres o lo tonto que eras hace diez años. Tu contenido no se perderá cuando desaparezca la próxima plataforma (hola Fotolog). Tienes el control absoluto de los contenidos sin que nadie te diga si lo puedes publicar o no. Escribir te permite crear hábitos, muy importante para la productividad. Fomenta el pensamiento crítico y el contrastar para crear tus contenidos y al leer los de los demás. Se puede consumir a cualquier velocidad -no como vuestras historias de Instagram-, te obliga a sintetizar y ordenar tus ideas, te permite compartir en cualquier plataforma…
   Como veis, no he hablado de marketing, ni de retorno de la inversión, ni de métricas, ni de optimización para redes sociales, linkbaiting y demás. No todo tiene que hacerse para crecer y crecer. No todo tiene que ser escalable. No todo tiene que ser negocio. No tenemos que vivir para trabajar, como dice Brian Gardner en este artículo.
   Y es que con tu blog personal puedes cambiar la vida de la gente. De una persona. De cientos. Qué más da. ¿Os imagináis cambiando la vida de una persona por algo cuyo mayor esfuerzo es sentarse media hora delante de vuestro WordPress? Al que le solucionáis un problema con vuestro tutorial y le permitís avanzar en un proyecto que tenía atascado. Al que va a una ciudad que no conoce y disfruta de restaurantes fantásticos a buen precio y aman la ciudad. Al que está de bajón y le hacéis reír con cualquier tontería…
   Pero volvamos a la batalla. La batalla contra todos los problemas de los que hablábamos antes. ¿Cómo la vamos a ganar?
   Usando nuestra propia web como centro de nuestra presencia en Internet. Hablé de esto el año pasado en este evento, sobre la web abierta. No dejéis todos vuestros contenidos en jardines vallados, en silos como las redes sociales. No lo hagáis.
   Sindicad vuestros contenidos. Que escribáis en vuestra web no quiere decir que no lo mováis por todos lados. El modelo POSSE significa Publish (on your) own site, syndicate everywhere. Usad vuestra web de base para luego enlazar desde todas las plataformas.
   Usad vuestra web para experimentar. Cread un microblog. Investigad las APIs antes de que nos las cierren todas. Si nos las cierran es porque saben que somos “peligrosos”. Un microblog soluciona el problema de los contenidos de Twitter, que también son contenidos que puede merecer la pena guardar. Crea una categoría, usa una plataforma como Micro.blog o añade tus fotos desde OwnYourGram.
   Y contagiad al mundo con este mensaje. De viva voz. Mediante webmentions, un estandar web para menciones y conversaciones de URL a URL. Usando clientes de terceros para escribir sobre la marcha gracias a Micropub.
   Resumiendo un poco todo lo que os he contado.
   Tenemos herramientas. Nuestra web con WordPress. Plugins para darle características fantásticas. Aquí os dejo enlazadas algunas: IndieWeb, IndieAuth para autenticarse con tu propio sitio, Micropub, Webmention, Semantic Linkbacks, Micro.blog…
   Tenemos principios. Decía Dan Gillmor en su blog que ‘estamos en peligro de perder lo que ha convertido a Internet en el medio más importante en la historia: una plataforma descentralizada donde personas como tú o como yo no necesitan pedir permiso para comunicarse, crear e innovar‘. Os dejo algunas lecturas obligatorias sobre toda esta filosofía, sobre los principios de la IndieWeb, sobre ética en el diseño web, y sobre un manifiesto ético. Leedlo. Os puede cambiar la vida.
   Con estas herramientas y estos principios, recordad #ResistenciaWCMadrid. Somos el punk rock de Internet. God Save the blog!

   WordPress no es solamente para blogs, pero hazte uno from Juan Hernando García

   <!--www.crestaproject.com Social Button in Content Start-->
   

   
   
   
   
   

   Reply

9. Useful reference to indieweb matters#indieweb

   Reply

10. @davidlaietta For WordPress related activity in the area of #IndieWeb, among many others you should generally know are @dshanske (aka GWG), @pfefferle, and @schnarfed (aka snarfed).

    In addition to a lot of IndieWeb specific pieces @pfefferle has also done some work on ActivityStreams (https://wordpress.org/plugins/activitystream-extension/) while @schnarfed has some great work with https://fed.brid.gy/ and https://indieweb.org/bridge#ActivityPub

    I’ve written a lot of intro related pieces which may help you get started: http://boffosocko.com/research/indieweb/. In particular, the second two in the “Introductory Articles” section may be the most useful higher level overviews for you. The wiki has a large number of pages devoted to a WordPress worldview starting here: https://indieweb.org/WordPress.

    Along with a plethora of others (who I’ve always found very warm and welcoming) we’re all often hanging out in the IndieWeb chat rooms (there’s a specific #WordPress related one as well): https://indieweb.org/discuss. If you want to hop on a conference call, I’m happy to walk you through some of the basics and point you in the direction of areas you’re most interested in checking out.

    If you’re free at the end of June, the IndieWeb Summit is a great place to start as well: https://2018.indieweb.org/. Many of us are planning on attending. If you can’t make it in person, we should be livestreaming a lot of it for remote attendees as well.

    Syndicated copies:

    Reply

11. It’s and old post. I’d almost forgotten who Anil Dash is. He had me at “The Web”. Thank you, Nicola for this trip down memory lane. I think this is the space folks like David Shanske, Matthias Pfefferle, Ryan Barrett and others are trying to create/re-create.

    Syndicated copies:

    Reply

12. I love that Tim is looking closely at how the choices of tools he’s using can potentially impact his students/readers. I’ve also been in the boat he’s in–trying to wrangle some simple data in a way that makes it easy to collect, read, and disseminate content for myself, students, and other audiences.
    Needing to rely on five or more outside services (Twitter, Instapaper, Pinboard, bit.ly, and finally even Canvas, where some of them are paid services) seems just painful and excessive. He mentions the amount and level of detail he’s potentially giving away to just bit.ly, but each of these are all taking a bite out of the process. Of course this doesn’t take into consideration the fact that Instapaper is actually a subsidiary of Betaworks, the company that owns and controls bit.ly, so there’s even more personal detail being consumed and aggregated there than he may be aware. All this is compounded by the fact that Instapaper is currently completely blocking its users within the EU because it hasn’t been able to comply with the privacy and personal data details/restrictions of the GDPR. Naturally, there’s currently no restrictions on it in the U.S. or other parts of the world.
    I (and many others) have been hacking away for the past several years in trying to tame much of our personal data in a better way to own it and control it for ourselves. And isn’t this part of the point of having a domain of one’s own? Even his solution of using Shaarli to self-host his own bookmarks, while interesting, seems painful to me in some aspects. Though he owns and controls the data, because it sits on a separate domain it’s not as tightly integrated into his primary site or as easily searched. To be even more useful, it needs additional coding and integration into his primary site which appears to run on WordPress. With the givens, it looks more like he’s spending some additional time running his own separate free-standing social media silo just for bookmarks. Why not have it as part of his primary personal hub online?
    I’ve been watching a growing trend of folks both within the IndieWeb/DoOO and edtech spaces begin using their websites like a commonplace book to host a growing majority of their own online and social related data. This makes it all easier to find, reference, consume, and even create new content in the future. On their own sites, they’re conglomerating all their data about what they’re reading, highlighting, annotating, bookmarking, liking, favoriting, and watching in addition to their notes and thoughts. When appropriate, they’re sharing that content publicly (more than half my website is hidden privately on my back end, but still searchable and useful only to me) or even syndicating it out to social sites like Twitter, Facebook, Flickr, Instapaper, et al. to share it within other networks.
    Some other examples of educators and researchers doing this other than myself include Aaron Davis, Greg McVerry, John Johnson, and more recently W. Ian O’Byrne and Cathie LeBlanc among many others. Some have chosen to do it on their primary site while others are experimenting using two or even more. I would hope that as Tim explores, he continues to document his process as well as the pros and cons of what he does and the resultant effects. But I also hopes he discovers this growing community of scholars, teachers, programmers and experimenters who have been playing in the same space so that he knows he’s not alone and perhaps to prevent himself from going down some rabbit holes some of us have explored all too well. Or to use what may be a familiar bit of lingo to him, I hope he joins our impromptu, but growing personal learning network (PLN).

    Syndicated copies:

    • book

    Reply

13. Replied to a tweet by Dan Cohen (Twitter)

    Has anyone set up WordPress so that “standard” post types continue to show up on your blog, but “status” (or “aside”) post types feed into social media platforms such as Twitter or https://t.co/kisv1mbGgT?— Dan Cohen (@dancohen) June 6, 2018

    https://platform.twitter.com/widgets.js

    Dan, There are a lot of moving pieces in your question and a variety of ways to implement them depending on your needs and particular website set up. Fortunately there are lots of educators playing around in these spaces already who are experimenting with various means and methods as well as some of their short and long term implications.
    I suspect some of the most interesting parts may be more closed off to you  (or possibly more difficult) because in your particular case it looks like you’re being hosted on WordPress.com rather than self-hosting your own site directly. For the richest experience you’d ideally like to be able to install some of the IndieWeb for WordPress plugins like Webmentions, Semantic Linkbacks, Post Kinds, and potentially others. This can be done on WordPress.com, but typically involves a higher level of paid account for the most flexibility.
    For crossposting your content to micro.blog, that portion is fairly simple as you can decide on any variety of post formats (standard, aside, status, images, etc.), post kinds, categories, or even tags and translate those pieces into RSS feeds your WordPress installation is already creating (most often just by adding /feed/ to the end of common URLs for these items). Then you can plug those particular feeds into your micro.blog account and you’re good to go for feeding content out easily without any additional work. Personally I’m using the Post Kinds plugin to create a finer-grained set of content so that I can better pick and choose what gets syndicated out to other sites.
    From within micro.blog, on your accounts tab you can enter any number of incoming feeds to your account. Here’s a list of some of the feeds (from two of my websites one using WordPress and the other using Known) that are going to my account there:

     
     
    As a small example, if you were using the status post format on your site, you should be able to add https://dancohen.org/type/status/feed/ to your feed list on micro.blog and then only those status updates would feed across to the micro.blog community.
    I also bookmarked a useful meta-post a few weeks back that has a nice section on using micro.blog with WordPress. And there are also many nice resources on the IndieWeb wiki for micro.blog and how people are integrating it into their workflows.
    For crossposting to Twitter there are a multitude of options depending on your need as well as your expertise and patience to set things up and the control you’d like to have over how your Tweets display.
    Since micro.blog supports the Webmention protocol, if your site also has Webmentions set up, you can get responses to your crossposts to micro.blog to show up back on your site as native (moderate-able) comments. You can do much the same thing with Twitter and use your website as a Twitter “client” to post to Twitter as well as have the replies and responses from Twitter come back to your posts using webmention in conjunction with the brid.gy website.
    I’ve been playing around in these areas for quite a while and am happy to help point you to particular resources depending on your level of ability/need. If you (or anyone else in the thread as well) would like, we can also arrange a conference call/Google hangout (I’m based in Los Angeles) and walk through the steps one at a time to get you set up if you like (gratis, naturally). Besides, it’s probably the least I could do to pay you back for a small fraction of your work on things like PressForward, Zotero, and DPLA that I’ve gotten so much value out of.
    Because of the power of these methods and their applicability to education, there are an ever-growing number of us working on the issue/question of scaling this up to spread across larger classrooms and even institutions. I’m sure you saw Greg McVerry’s reply about some upcoming potential events (as well as how he’s receiving comments back from Twitter via webmention, if you scroll down that page). I hope you might join us all. The next big event is the IndieWeb Summit in Portland at the end of June. If you’re not able to make it in person, there should be some useful ways to attend big portions remotely via video as well as live chat, which is actually active 24/7/365.
    As is sometimes said: I have made this longer than usual because I have not had time to make it shorter. At least I wasn’t hampered by Twitter’s character constraints by posting it on my own site first.
     
     
     
     
     

    Syndicated copies to:
    Twitter icon
    
    WordPress icon
    

    Syndicated copies:

    Reply

14. @jbj Given the number of people I’ve seen experimenting over the past months, I’d be happy to put together a series of short pieces for @ProfHacker covering the areas of overlap of between #edtech, #DoOO, #indieweb, research, academic publishing, samizdat, commonplace books, etc. Essentially tighter versions of some of https://boffosocko.com/research/indieweb/ but specifically targeting the education space using WordPress, Known, and Grav. Let me know if you’d accept submissions for the community.

    Reply

15. I’ve written about threading comments from one WordPress website to another before. I’ve long suspected this type of thing could be done with Twitter, but never really bothered with it or necessarily needed to do it, though I’ve often seen cases where others might have wanted to do this.
    For a post today, I wrote on my own site and syndicated it to Twitter and got a reply back via webmention through Brid.gy. This process happens for me almost every day, and this all by itself feels magical.  The real magic however, and I don’t think I’ve done this before or seen it done, was that I replied to the backfed comment on my site inline and manually syndicated to Twitter using a permalink of the form http://www.example.com/standard-permalink-structure/?replytocom=57527#respond, where 57527 is the particular comment ID for my inline comment. (This comment ID can typically be found by hovering over the “Reply” or “Comment” button on one’s WordPress website in most browsers.)
    Where to find the comment ID to provide the proper permalink to get properly nested comments backfed to your site.
    When a reply to my second syndicated Twitter post came in, Brid.gy properly sent it as a comment to my comment AND nested it properly!
    I’ve now got a nested copy of the conversation on my site that is identical to the one on Twitter.
    I suspect that by carefully choosing the URL structure you syndicate to Twitter, you’ll allow yourself more control over how backfed comments from Brid.gy nest (or don’t) in your response section on your site.
    Perhaps even more powerfully, non-WordPress-based websites could also use these permalinks structures for composing their replies to WordPress sites to have their replies nest properly too. I think I’ve seen Aaron Parecki do this in the wild.
    Since the WordPress Webmention plugin now includes functionality for sending webmentions directly from the comments section, I’ll have to double check that the microformats on my comments are properly marked up to  see if I can start leveraging Brid.gy publish functionality to send threaded replies to Twitter automatically. Or perhaps work on something that will allow automatic replies via Twitter API. Hmmm…
    Despite the fact that this could all be a bit more automated, the fact that one can easily do threaded replies between WordPress and Twitter makes me quite happy.
    Thread onward!
    For more on my IndieWeb explorations with Twitter, see my IndieWeb Research page.

    Syndicated copies:

    Reply

16. Yes, discovery can be an issue, but if one is providing various feeds (RSS, Atom, JSON, or h-feed) of various post types, then it becomes easier to slice and dice the content coming out of particular websites. I’ve got my website set up so that nearly every post format, post kind, category, and tag has its own feed. Ideally, you should be able to extract almost anything you’d want from my site via a custom feed if necessary.
    As an example if you want to follow what I’m reading, there’s a feed for that. Or you can listen to the things I’m listening to by subscribing to my fauxcast.
    Separately, I maintain a following page which, similar to a blogroll, is a list of sites I’m following along with OPML of the full list or subcategories. Thus if you want to subscribe to the IndieWeb OPML list, it’s there for you. (Even more fun if you’re using functionality like OPML subscriptions as they’re done in Inoreader, so that when I update my list, yours automatically does too.)
    If you’re interested in recreating portions of some of this I’ve tried to document a lot of it (for WordPress at least) at https://boffosocko.com/research/indieweb/.

    Syndicated copies:

    • book

    Reply

17. Replied to a tweet by William Ian O’Byrne (Twitter)

    Also, if this post is the best example of @hypothes_is annotations baked into WordPress site, I’d like to see some #IndieWeb connections so the great discussion with @heatherstaines is pulled into the comments/mentions on the post. This would be just like tweets or other comments— William Ian O’Byrne (@wiobyrne) July 5, 2018

    https://platform.twitter.com/widgets.js

    Ian, thanks for putting together all of these examples. I think my preference is for option three which provides the most context and seems easiest to read and understand. I like the way you’ve incorporated the blue arrow, which makes semantic sense as well.
    I’m sure I’ve seen other versions, but Jon Udell has at least one example of some annotations on his own website like yours too.
    When it comes to the “conversation” side of what you’re looking for, I think the biggest piece you’re really missing and which some on the Hypothes.is side (except perhaps for Nate who may have a stronger grasp of their value after the recent IndiewWeb Summit) are apt to miss is that Hypothes.is doesn’t support sending webmentions. Presently you’re putting your data out there in a one-sided manner and Hypothes.is isn’t pushing the other side or any of the follow up back to you. As a result it’s operating as a social silo the same way that sites like Facebook and Twitter do. Based on their GitHub repository, I know that they’ve considered webmentions in the past, but apparently it got put on a back burner and hasn’t been revisited.
    Ideally they’d want to have webmentions work in two places. It would be great if they could send webmentions of annotations/highlights to the original page itself, so that the site owner is aware that their content is being marked up or used in this manner. This also means that Hypothes.is could be used as a full-blown and simple commenting system as well so that those who aren’t using their own sites to write replies could use Hypothes.is as an alternative. The second thing it might want to do is to send webmentions, particularly for replies, to the original page as well as to any URLs that are mentioned in the comment thread which appears on Hypothes.is. This would mean that you’d want to add the permalink to your post back to the copy you put on Hypothes.is so that you and your website stay in the loop on the entirety of the conversation. In many senses, this is just mirroring what is going on in threaded Twitter conversations that get mirrored back to your WordPress website. [I’ll note that I think I’ve got the last of the moving pieces for this Twitter/WordPress workflow properly linked up in the past week.] Since Twitter doesn’t support webmentions itself, Brid.gy is handling that part for you, but in Hypothes.is’ case you don’t have any of the details coming back for allowing you to display the discussion on your site except by doing so manually. Doing it manually for extended conversations is going to become painful over time.
    From an IndieWeb perspective, you’re primarily implementing a PESOS workflow in which you post first on Hypothes.is and then send a copy of it to your own website. Naturally it would be better if you were posting all the details on your own website and using the Hypothes.is API to syndicate your copy there for additional public conversation outside of the readership of your website. Unfortunately building the infrastructure to do this is obviously quite daunting. Since they’ve got an API, you might be able to bootstrap something webmention-like onto it, but for your purposes it would obviously be easier if they had direct webmention support.
    It would also be wonderful if Hypothes.is supported the micropub specification as well. Then you could ideally log into the system as your website and any annotations you made could be automatically be published to your website for later storage, display, or other use. In some sense, this is what I’m anticipating by making  explicit standalone annotation and highlight post kinds on my website. In practice, however, like you, I’d prefer to have a read, like, or bookmark-type of post that aggregates all of my highlights, annotations, and marginalia of a particular piece for easier future use as well as the additional context this provides. I suspect that if I had the additional tag within the Hypothesis Aggregator plugin for WordPress that would let me specify the particular URL of an individual article, I would have most of the front side PESOS functionality we’re all looking for. The rest will require either webmention or a lot more work.
    I may have mentioned it before, but in case you hadn’t found it I’ve got a handful of posts on annotations, many of which include some Hypothes.is functionality.
    Not itemized in that list (yet?) are some experiments I’d done with the Rory Rosenzweig Center’s PressForward plugin for WordPress. It allowed me to use a simple browser bookmarklet to save a webpage’s content to my personal website with a rel=”canonical” tag for the page pointing at the original page. (Here’s a good example.) Because of the way the canonical set up works within Hypothes.is, I noticed that annotations I (and others) made on the original were also mirrored and available on my website as well. In my case, because PressForward was copying the entirety of the article for me, I used the <mark> HTML tag to make the highlights on my page, but with Hypothes.is enabled, it also shows the other public annotations as well. (Use of the title attribute adds some additional functionality when the mark tagged text is hovered over in most browsers.)
    In another example, I annotated a copy of one of Audrey Watters’ articles (after she’d disabled the ability for Hypothesis to work on her site, but before she changed the Creative Commons licensing on her website). But here I added my annotations essentially as pull-quotes off to the side and syndicated copies to Hypothes.is by annotating the copy on my website. If you visit Audrey’s original, you’ll see that you cannot enable Hypothesis on it, but if you’re using the Chrome extension it will correctly indicate that there are five annotations on the page (from my alternate copy which indicates hers is the rel=”canonical”).
    In any case, thanks again for your examples and documenting your explorations. I suspect as time goes by we’ll find a more IndieWeb-centric method for doing exactly what you’ve got in mind in an even easier fashion. Often doing things manually for a while will help you better define what you want and that will also make automating it later a lot easier.
     
     

    Syndicated copies to:

    Reply

18. Replied to a tweet by Unix Sys Admin (Twitter)

    @jgmac1106 Out of interest what are you using to generate ‘pingbacks’ from Tweets to your website? #seemsneat— Unix Sys Admin (@UnixSysAdmin) July 17, 2018

    These are called webmentions they are the glue of the #IndieWeb https://t.co/p3TnFqXuD5 (https://t.co/Iv1xaki5t6)— Greg McVerry (@jgmac1106) July 17, 2018

    Do you need to manually paste your URL into the tweets or is there a plug-in for browsers?— Unix Sys Admin (@UnixSysAdmin) July 17, 2018

    https://platform.twitter.com/widgets.js

    Articles 1, 5, and 6 in this highlighted series for Twitter will get you most of the functionality (and then some). However once you’ve enabled some of these related plugins, you can also do so much more than just use your site to interact with Twitter.

    Syndicated copies to:

    Reply

19. IndieWeb Collection by Chris Aldrich (BoffoSocko) Over the past several years I’ve written a broad number of pieces about the IndieWeb. I find that many…

    Reply

20. Chris Aldrich provides an introduction to webmentions. This includes unpacking the specification, the notion of mentions, the idea of kinds and way in which sites are potentially able to connect two-ways. This continues Aldrich’s efforts to document the IndieWeb, which has included a thorough overview of the IndieWeb and the future of feed readers. This introduction is different to Aaron Parecki’s guide to sending your first webmentions or breakdown of the oAuth standard.

    Reply

21. silo-quits << 2018-07-20 Maggie Haberman quitting using Twitter as dialog: [https://www.nytimes.com/2018/07/20/sunday-review/maggie-haberman-twitter-donald-trump.html Maggie Haberman: Why I Needed to Pull Back From Twitter] <blockquote>After nearly nine years and 187,000 tweets, I have used Twitter enough to know that it no longer works well for me. I will re-engage eventually, but in a different way.</blockquote>

    Reply

22. My Month of July
    LinkedIn recently reminded me that it has been two years in my current position. I was shocked, time has flown. As I touched on recently, it has been a whirlwind of an experience as is the nature I imagine of working within a transformational project. The biggest lesson learnt is that in a lean environment (or at least an attempt at a lean environment) you sometimes get stuck doing what needs to be done, rather than what you may prefer to be doing, which in my case is working with teachers and schools. I am currently working on refining a scale-able implementation process associated with student reporting.
    At home, the common cold came back, again. I swear we had overcome it for this season, but no. Also, new term and new song for my daughter’s school. So I think I am up to 20+ listens of Try Everything from Zootopia. Another great growth mindset anthem. Might also say something about the algorithms at play.
    I am learning through practice that the easiest way to learn something is to watch and copy somebody else. Scary how quickly our youngest picks everything up. Understanding Mal Lee and Roger Broadie’s point about the young being digitally proficient by the age of three.
    I attended DigiCon18. Although I went to some interesting sessions and sparktalks, what was great were the conversations in-between. This included discussing the Ultranet with Rachel Crellin, the pedagogy associated to ongoing reporting with Chris Harte, connected learning with Jenny Ashby, parenting and partnerships with Lucas Johnson, implementing the Digital Technologies curriculum with Darrel Branson, purpose and leadership with Riss Leung and direct instruction with Richard Olsen.
    In other areas, I have been listening to Amy Shark, Florence and the Machine, DJ Shadow, The National and Guy Pearce. I started reading Adam Greenfield’s Radical Technologies. I also updated my site, moving back to ZenPress and adding in a new series of header images developed by JustLego101.
    In regards to my writing, here was my month in posts:

    REVIEW: New Dark Age – Technology and the End of the Future

    My Life in Black and White

    Here then are some of the thoughts that have also left me thinking …
    Learning and Teaching

    Teaching Game Design with Bill Cohen (TER Podcast): Cameron Malcher interviews Bill Cohen about game-design through play-based learning. Cohen goes beyond the usual coding and computer-aided approaches to focusing on ‘low-tech’ games. This included engaging with board games and outdoor games. This play-based approach focuses on developing clear metalanguage, feedback for mastery and working with an iterative design process. This reminds me in part of Amy Burvall’s notion of ‘rigorous whimsy‘ and BreakoutEDU. Some resources Cohen shared include Boardgame Geek and Lady Blackbird, while in a seperate post, Clare Rafferty shared a list of games associated with History. For a different take on games, in a recent episode of the IRL Podcast, Veronica Belmont and Ashley Carman take a look at gamification in everyday life. Some examples of this include notifications on smartphones, likes and retweets on Twitter or the endorsements on Linkedin.

    If there is one thing that I have learnt as a teacher is that nothing leaches out fun more than dropping a layer of education over the top of it – Bill Cohen

    Encountering harmful discourses in the classroom: Ian O’Byrne discusses the challenges of engaging in harmful discourses. He provides some ways to responding, as well as a number of ways to be proactive. This touches on what danah boyd describes as the weaponisation of worldviews.

    Howard C. Stevenson from Penn’s Graduate School of Education indicates three steps to address these harmful discourses as they enter your classroom.

    Start with you – Process your own feelings, and address your own vulnerabilities before entering the classroom. Develop a support system with your colleagues.
    Practice – Classroom reactions usually happen in a split second. Prepare yourself for these instances by role-playing with colleagues in your building, or online with your PLN.
    After an incident – Resist the urge to condemn the action or content. First try to understand the motivation if is disseminated through your classroom or building. Allow the school’s code of conduct to address instances where students actively spread this information. Strongly explain to students that these harmful discourses and the messages being spread about individuals and groups are not accepted. You will not accept the silencing of voices.
    Keep talking – After these events, the best course of action is to keep talking. Difficult discussions will often ensue, but children and adults alike need to be able to process their feelings and reactions. This is an opportunity to shut down and be silent, or engage and promote change.

    How well do we ‘face up to’ racism?: Anna Del Conte provides some take-aways from a course on racism. Some of the activities included what racism is, a timeline of diversity in Australia and listening to stories. Another resource I am reminded of is Dan Haesler’s interview with Stan Grant. In part this stemmed from Grant’s speech addressing racism.

    Multiculturalism is not an outcome but a process. Racism may not be deliberate BUT anti-racism is always deliberate.

    Can Reading Make You Happier?: Ceridewn Dovey takes a look at bibliotherapy and the act of reading as a cure. Some argue that readers are more empathetic, while others suggest that it provides pleasure, whatever the particular outcome maybe, reading has shown to provide many health benefits. As Kin Lane suggests, when in doubt, read a book. Zat Rana suggests that this reading is not about being right or wrong, but rather about being open new ideas and lessons.

    So even if you don’t agree that reading fiction makes us treat others better, it is a way of treating ourselves better. Reading has been shown to put our brains into a pleasurable trance-like state, similar to meditation, and it brings the same health benefits of deep relaxation and inner calm. Regular readers sleep better, have lower stress levels, higher self-esteem, and lower rates of depression than non-readers. “Fiction and poetry are doses, medicines,” the author Jeanette Winterson has written. “What they heal is the rupture reality makes on the imagination.”

    Historic Tale Construction Kit – Bayeux: This site allows users to recreate the Bayeux Tapestry. Clearly this is a great resource for history students, but it is also an interesting approach to storytelling.

    Two German students originally wrote the Historic Tale Construction Kit, with Flash. Sadly, their work isn’t available anymore, only remembered. This new application is a tribute, but also an attempt to revive the old medieval meme, with code and availability that won’t get lost.

    Edtech

    Webmentions: Enabling Better Communication on the Internet: Chris Aldrich provides an introduction to webmentions. This includes unpacking the specification, the notion of mentions, the idea of kinds and way in which sites are potentially able to connect two-ways. This continues Aldrich’s efforts to document the IndieWeb, which has included a thorough overview of the IndieWeb, the future of feed readers and reimagining academic research. This introduction is different to Aaron Parecki’s guide to sending your first webmentions or breakdown of the oAuth standard.

    Breaking down the walls between the internet’s many social silos, Webmentions offer a new level of freedom for web interactions.

    Twenty Years of Edtech: Martin Weller looks back at twenty years of EdTech, highlighting the various moments that have stood out across the journey. This brings together many of the pieces that he has written for his 25 years of EdTech series that he has written to celebrate 25 years of ALT. As he points out in his introduction, we are not very good at looking back. This post then offers an opportunity to stop and do so in a structured manner. Another interesting take on history is Ben Francis’ post on the Firefox OS.

    What has changed, what remains the same, and what general patterns can be discerned from the past twenty years in the fast-changing field of edtech?

    Learning To Code By Writing Code Poems: Murat Kemaldar discusses the connections between coding and poetry. He re-imagines the various rules and constructs in a more human form. This continues a conversation started between Darrel Branson, Tony Richards and Ian Guest on Episode 234 of the Ed Tech Team Podcast about whether everyone should learn poetry and coding. This is also something Royan Lee shares.

    In all languages, there is probably a word for love. You kinda know what it means, but not really, because it is so subjective. But still, there is a word for it. But in JavaScript, there is no “love,” until you say there is. It can be whatever you want it to be.

    18 best practices for working with data in Google Sheets: Ben Collins provides a guide for working with data in Google Sheets. Some of the useful steps that stood out were documenting the steps you take, adding an index column for sorting and referencing, creating named ranges for your datasets and telling the story of one row to check the data. This is all in preparation for his new course on data analysis. Another tip I picked up from Jay Atwood has been to import data, if moving from Excel to Sheets, rather than simply copying and pasting.

    This article describes 18 best practices for working with data in Google Sheets, including examples and screenshots to illustrate each concept in action.

    Zuck’s Empire of Oily Rags: Cory Doctorow provides a commentary on the current state of affairs involving Facebook and Cambridge Analytica. Rather than blame the citizens of the web, he argues that the fault exists with the mechanics in the garage and the corruption that they have engaged with. The question that seems to remain is if this is so and we still want our car fixed, where do we go? Doctorow has also recorded a reading of the article.

    It’s fashionable to treat the dysfunctions of social media as the result of the naivete of early technologists, who failed to foresee these outcomes. The truth is that the ability to build Facebook-like services is relatively common. What was rare was the moral recklessness necessary to go through with it.

    How the Blog Broke the Web: Amy Hoy reflects on the early days of publishing on the web, where people would handcraft pages and connect them using a contents page. This was superseded by Moveable Type and the chronological blog, subsequently killing off the non-diariest. I was not really engaged in the web back then so it is hard to comment as Jeremey Keith, Duncan Stephen and Kicks Condor have, but it does remind me of the current debates around blogging. I think that all these spaces are forever changing and developing. Sometimes this is based on wholesale changes, but usually people have their own particular reason. Maybe some people will drop off with Gutenberg, but then again sometimes these things have their day.

    Movable Type didn’t just kill off blog customization. It (and its competitors) actively killed other forms of web production.

    Are We Listening?: Jose Picardo argues that the question about whether we should have more or less technology in schools misses the point. What matters is how it is used. For example, those who argue for more knowledge often fail to put the effort into actually understanding how technology is used in education. This comes back to the importance of why and having a framework to guide you. For a different perspective on technology in the classroom, read David Perry’s thread.

    The very teachers who read William and nod vigorously about the need to know stuff before you can understand or do stuff in the context of curriculum are unable to draw parallels between their dismissal of digital technology and their own lack of knowledge about it. Rather than finding virtuosity and pride in learning about how what technology works best and in what context—so as to be able to discern the best tool for particular tasks—we seem happy to eschew whole new toolkits on the dodgy grounds of ignorance and misconception.

    Storytelling and Reflection

    Throwing Our Own Ideas Under the Bus: Ross Cooper discusses the idea of putting your worst foot forward taken from Adam Grant’s book Originals. This involves trusting the idea at hand and starting with reasons why it might fail. Cooper suggests that this can be useful as it disarms the audience, critique involves effort, helps to build trust and leaves audience with a more favourable assessment. He also looks at this alongside Simon Sinek’s concept of ‘start with why’, highlighting the reason why and the challenges that might be faced. I wonder if the challenge in focusing on the why and why not is about finding balance? This reminds me of Malcolm Gladwell’s discussion of Generous Orthodoxy.

    As an elementary school principal, here’s the approach I’ve been taking with change: “Here’s what we’re doing, here’s why we’re doing it, and here are some of the ways I will support you!” Now I’ll be toying around with the idea of also proactively addressing the elephants in the room. Furthermore, we should allow for teachers and staff to respectfully and honestly discuss these obstacles, as opposed to us trying to sweep them under the rug. After all, flaws will be talked about in one way or another, and critical conversation that gives everyone a voice is preferred to potential venting in the faculty room.

    The future will be dockless: could a city really run on ‘floating transport’?: Alex Hern discusses the rise of floating transport, something that I touched on recently with the demise of oBike in Melbourne. Hern captures a number of stories from around the world of hope for efficiency, but also issues associated with shared spaces. I am taken by Hern’s closing remarks concerning reliability over flexibility. This leaves me thinking that sometimes what is required is community and sometimes that involves patience. What is the cost to the public/private transport industry when everyone relies on private personal transport models like Bird or Uber?

    Ultimately, floating transport is going to have to learn another lesson that conventional transportation bodies have taken to heart: flexible may be fun, but cities run on reliable.

    i am sorry: Pernille Ripe reflects on life as a connected educator. She discusses the stress, anxieties and perceived responsibilities that come with being an educelebrity. Although we often talk about the technicalities associated with being (digitally) literate, what is sometimes overlooked are the social consequences. This is something that Austin Kleon also recently reflected upon.

    So it is time for me to step back a bit. To do less work publicly, to share less, to not be so immediately available. To be just Pernille, the person who doesn’t have all of the answers necessarily. That only creates something because she cannot help it. That gives all of her when she is in a public space, but then steps back when she is private.

    Facebook’s Push for Facial Recognition Prompts Privacy Alarms: Natasha Singer discusses Facebook’s continual push for facial recognition. She traces some of the history associated with Facebook’s push into this area, including various roadblocks such as GDPR. She also looks at some of the patent applications. This made me wonder how many patents actually come to fruition and how many are a form of indirect marketing? Elsewhere, Doug Levin explains why facial recognition has no place in schools, especially the way Curtin University is using it.

    Cameras near checkout counters could capture shoppers’ faces, match them with their social networking profiles and then send purchase confirmation messages to their phones.

    The anti-cottonwool schools where kids stare down risk in favour of nature play: This article from the ABC discusses a couple of schools in Western Australia that have reduced the rules on outdoor play. This reminds me of Narissa Leung’s use of old bricks and Adrian Camm’s use of odd material to engage with play.

    Mr Smith said whereas students would previously come to the office complaining of injury, they are now too busy to make a fuss. “Students are becoming more resilient and getting on with it.” The school has just three rules — no stacking milk creates, no walking on the large wooden spools and no tying rope to yourself.

    The Dangers of Distracted Parenting: Erika Christakis discusses the challenges of parenting in a digital age. This all comes down to distractions and as I have touched on before, this is not always digital. I really like danah boyd’s strategy for dealing with this, that is to say why you are using a device. This openness offers a useful point of reflection. I think that the conclusion to this article says it all though, “put down your damned phone.”

    Parents should give themselves permission to back off from the suffocating pressure to be all things to all people. Put your kid in a playpen, already! Ditch that soccer-game appearance if you feel like it. Your kid will be fine. But when you are with your child, put down your damned phone.

    FOCUS ON … SPACE

    I was recently challenged on the place of space in regards to learning. I recorded a microcast on the topic, but I haven’t had the chance to put all my thoughts together. In the interim, I have collected together a number of posts on the topic. If you have any others to add to the mix, I would love to read them.

    Imagining Different Learning Spaces: Jon Corripo provided his suggestions for redesigning a classroom space which again sparked my imagination.

    Flexible Seating: What’s the Point?: Chris Wejr reflects on his experiences in reviewing flexible learning spaces. This includes the reasons to re-design, as well as a series of thoughts associated with the process of re-imagining.

    Why I Hate Classroom Themes: Emily Fintelman reflects on classroom themes and wonders what impact they are really having on learning. She suggests that our focus should be on how spaces are structured and strategies that can be used to give students more voice.

    Flexible Classrooms: Research Is Scarce, But Promising: What is interesting about this report is that rather than discussing furniture in isolation, it is considered as a part of a wider conversation about learning and environment. The impact of flexible spaces though can be almost incidental at times, as is with the case of Maths. This speaks of agency as much as it does of the chairs in the classroom.

    Adding the Learning Back to Space: A reflection on an outdoor learning space and the potential of technology to increase learning and engagement.

    Benefits of Flexible Learning Spaces #1 Teaching in Teams: Stephen Rowe explains that teachers working in teams is a significant benefit that arises from teaching in an open learning space.

    Designing Learning Spaces – putting the cart before the horse: June Wall and Jonathon Mascorella define learning environments as a set of physical and digital locations, context and cultures in which students learn.

    Learning Space Design Inspiration: Steve Brophy collects together a number of ideas and inspirations associated with learning spaces.

    Beanbags in Space: Matt Esterman suggests that what most teachers want is a more shiny version of what they have, because they are not trained as designers (usually) and are so often hemmed in by the expectations of current reality.

    Inquiry, noticing and the changing seasons… A tribute to the late Frank Ryan: Kath Murdoch reflects on the potential of the environment associated with inquiry.

    Coalescent Spaces: Dave White considers the impact of digital technologies on the creation of coalescent learning spaces.

    Seeing Spaces: Bret Victor reimagines the makerspace built around tinkering and argues that it is in ‘seeing’ that we are able to make this a science.

    Communities, Networks and Connected Learning with Google: Technology enables us to easily develop digital communities and networks inside and outside of the classroom. The reality though is that connected learning is as much about creating spaces for learning and building on that.

    READ WRITE RESPOND #031
    So that is July for me, how about you? As always, interested to hear.
    Also, feel free to forward this on to others if you found anything of interest, maybe you want to subscribe or buy me a coffee? Archives can be found here.

    Cover image via JustLego101.

    Syndicated copies:

    Reply

23. I had almost forgotten that it was not so long ago that I’d outlined how I use Hypothesis to own my own highlights and annotations on my website. For the benefit of those in Dr. McVerry’s EDU522 course, I’ve included a link to it here.
    For those who would like to see some examples you can find several below:
    Specific stand-alone highlight posts
    Specific stand-alone annotation posts
    Other posts (typically reads) which I’ve highlighted and/or otherwise annotated things
    I created the stand-alone posts using customized post kinds using some custom code for the Post Kinds Plugin.
    I’ll begin tagging some of these pieces with the tag “backstage” for those in the EDU522 class that wish to follow along with how I’ve built or done certain things. You can subscribe to these future posts by adding /feed/ to the end of the URL for this tag archive.
    To some extent my IndieWeb Collection/Research page has a lot of these “backstage” type posts for those who are interested. As part of the IndieWeb community, I’ve been documenting how and what I’ve been doing on my site for a while, hopefully these backstage posts will help other educators follow in my path without need to blaze as much of it anew for themselves.
    Backstage posts are in actuality a very IndieWeb thing:

    As we discover new ways to do things, we can document the crap out of them. —IndieWeb.org

     

    Syndicated copies to: WordPress icon
    

    Reply

24. IndieWeb Collection (BoffoSocko) Over the past several years I’ve written a broad number of pieces about the IndieWeb. I find that many people are now actively searching for, reading, and implementing various versions of what I’ve done, particularly on the WordPress Platform. Because of some discussions at IndieWebCamp Baltimor…
    Starting to collect my bookmarks on my own sites, and Chris’s indieweb collection is a great place to start.

    Reply

25. Replied to a post by David Shanske (David Shanske)

    Is it time to resurrect the DiSo Project? https://t.co/Sd3p8Gl6M8 Funny, we were here in 2006, @simonw: https://t.co/Vmz06KA1Gp/cc @willnorris @steveivy @singpolyma https://t.co/eWYliJtI2y— Chris Messina™ (@chrismessina) August 18, 2018

    https://platform.twitter.com/widgets.js

    People continued working on it. Everything you need using W3C standards like Webmention, Microformats2…give it a try? https://IndieWeb.org/WordPress/Plugins

    I suspect that @chrismessina could do it quickly, but for those who’d like to leave Twitter for #WordPress with similar functionality (but greater flexibility and independence), I recorded a 2 hour video for an #IndieWeb set up/walk through with some high level discussion a few months back. If you can do the 5 minute install, hopefully most of the rest is downhill with some basic plugin installation and minor configuration. The end of the walk through includes a live demonstration of a conversation between a WordPress site on one domain and a WithKnown site running on another domain.
    tl;dr for the video:

    WordPress base install

    IndieWeb Plugin (gives you quick access to most of the plugins below)
    The SemPress Theme or Independent Publisher Theme

    Webmention and Semantic Linkbacks plugins (for site to site communication and notification)

    IndieAuth plugin (for authenticating with Micropub, Microsub, and other related tools)

    Micropub plugin (for a variety of clients you can use to publish to your site)

    Syndication Links plugin (to indicate which sites, like Twitter, that you syndicate your content to to stay in touch with those left behind)

    WebSub plugin (to ping feed readers for real-time communication)

    Brid.gy for WordPress plugin (to pull in backfed comments from other social silos)

    Post Kinds plugin (for better delineating articles, status updates (notes), replies, favorites, likes, etc. with appropriate microformats markup)

    Aperture Plugin (allows you to sign into a variety of Microsub readers which also act as your stream and allow you to reply to others directly from your reading interface. This part is still a bit experimental, but the kinks are being worked out presently for a richer experience.)

    Additional pieces are discussed on my IndieWeb Research Page (focusing mostly on WordPress), in addition to IWC getting started on WordPress wiki page. If you need help, hop into the IndieWeb WordPress chat.
    For those watching this carefully, you’ll notice that I’ve replied to David Shanske’s post on his website using my own website and sent him a webmention which will allow him to display my reply (if he chooses). I’ve also automatically syndicated my response to the copy of his reply on Twitter which includes others who are following the conversation there. Both he and I have full copies of the conversation on our own site and originated our responses from our own websites. If you like, retweet, or comment on the copy of this post on Twitter, through the magic of Brid.gy and the Webmention spec, it will come back to the comment section on my original post (after moderation).
    Hooray for web standards! And hooray for everyone in the IndieWeb who are helping to make this type of social interaction easier and simpler with every passing day.

    Syndicated copies to:

    Reply

26. WordPress is open source CMS software used by many on the Indieweb as well as a blog hosting service.

    Reply

27. Here’s a useful collection of #IndieWeb-related content, including WordPress plugins, corralled and curated by @ChrisAldrich:

    boffosocko.com/research/indie…

    #IndieWebCamp #WWW #WordPress #semanticweb

    Reply

28. Great to see you tinkering Clint. Pretty sure the bridge to Facebook died with Cambridge Analytica. If you are looking for any ideas and inspiration, I highly recommend diving into Chris Aldrich’s research. There is always something there I feel I have overlooked.

    Reply

29. Replied to Does anyone else keep their own knowledge wiki? by nikivi (lobste.rs)

    I’ve been extending and improving my personal wiki for 1 year now and it has been one of the best things I’ve done. I found writing blog posts was too high friction and very often didn’t finish things because there is so much you can talk about in any given article. But a wiki is just a living document containing your notes and thoughts on things. I also use it as my public bookmark manager as I collect interesting to me links under each topic.

    For my wiki, I render everything to the web first with GitBook. And I have a macro I run that automatically commits any changes I’ve made with Sublime Text on the mac and Ulysses on the phone so everything is super easy to edit and publish.

    Does anyone else keep their own wiki here? Or you think a blog is enough for you?

    I’ve been considering starting a personal wiki after reading The Garden and the Stream: A Technopastoral by Mike Caulfield a while back. His article has some great set up and philosophy about the wiki versus blog. I’ve been using my own website/blog as a commonplace book for quite a while now to collect everything from what I’m listening to to what I read and even what I’ve highlighted/annotated online. I’ve documented a lot of the pieces I use to create/customize it. (Not everything I write is public either.)
    Ultimately, I think that either way, having a solid search functionality becomes important regardless of which direction one chooses.

    Syndicated copies to:
    
    

    Syndicated copies:

    • book

    Reply

30.  Articles

     Notes

     Replies

     Photos

     Checkins

     Audio

     Microcast

     Listens

     Watches

     RSVPs

     Read

     Highlights

     Annotations

     Favorites

     Likes

     Reposts

     Bookmarks

     Follows

     Jams

     Video

     Quotes

     Chat

     Recipes

     Eat

     Drink

     Exercise

     Plays

     Chickens

     Itches

     Issues

     Wishlist

     Acquisitions

     Firehose

     Microblog

     Linkblog

     Food Diary

     IndieWeb Podcast

    Currently featured on A List Apart
    Webmentions: Enabling Better Communication on the Internet
    Over 1 million Webmentions will have been sent across the internet since the specification was made a full Recommendation by the W3C—the standards body that guides the direction of the web—in early January 2017. That number is rising rapidly, and in the last few weeks I’ve seen a growing volume of chatter on social media and the blogosphere about these new “mentions” and the people implementing them. [click through to read the entire article]

    Featured Posts

    <a href="http://boffosocko.com/2017/07/28/an-introduction-to-the-indieweb/">
</a>

                                An Introduction to the IndieWeb
    
    
    
                            There's a better way to own and control your online identity
    
    
    
                    <a href="https://boffosocko.com/kind/read/">                            
                        </a>
    
    
                            What I'm Reading
    
    
    
                    <a href="http://boffosocko.com/2017/06/09/how-feed-readers-can-grow-market-share-and-take-over-social-media/">                            
                        </a>
    
                                It's time to embrace open & disrupt social media
    
    
    
                            Feed reader revolution
    
    
    
                    <a href="https://boffosocko.com/category/podcast/">                            
                        </a>
    
    
                            An IndieWeb Podcast
    
    
    
                    <a href="http://boffosocko.com/now/">                            
                        </a>
    
                                What I'm up to
    
    
    
    
                    <a href="http://boffosockobooks.com/books/authors/henry-james-korn/amerikan-krazy/">                            
                        </a>
    
    
    
                    <a href="http://www.boffosocko.com/publishing">                            
                        </a>
    
                                Need Help Publishing? 
    
    
    
    
                    <a href="http://boffosocko.com/2015/05/12/popular-science-books-on-information-theory-biology-and-complexity/">                            
                        </a>
    
    
                            Popular Science Books on Information Theory, Biology, and Complexity
    
    
    
                    <a href="https://boffosocko.com/research/indieweb/">                            
                        </a>
    
                                A Collection of IndieWeb Articles
    
    
    
                            Here's a selection of articles and pieces I've written about IndieWeb related technology and philosophy.
    
    
    
                    <a href="http://boffosocko.com/2016/01/27/what-is-information-by-christoph-adami/">                            
                        </a>
    
    
                            What is Information? by Christoph Adami
    

    A proper understanding of information in terms of prediction is key to a number of disciplines beyond engineering, such as physics and biology.

    var slider;

    jQuery(function () {
    switch (singleSlider_2.view) {
    case 'none':
    jQuery('#slider_2').sliderPlugin({
    maxWidth: singleSlider_2.width,
    maxHeight: singleSlider_2.height,
    transition: singleSlider_2.effect,
    controls: singleSlider_2.navigate_by,
    cropImage: hugeitSliderObj.crop_image,
    navigation: hugeitSliderObj.show_arrows,
    delay: +singleSlider_2.pause_time,
    transitionDuration: +singleSlider_2.change_speed,
    pauseOnHover: singleSlider_2.pause_on_hover
    });
    break;
    case 'carousel1':
    var $pager = false,
    $thumb = false;
    switch (singleSlider_2.navigate_by) {
    case 'dot':
    $pager = true;
    $thumb = false;
    break;
    case 'thumbnail':
    $pager = true;
    $thumb = true;
    break;
    case 'none':
    $pager = false;
    $thumb = false;
    break;
    }

            jQuery('#slider_2').RSlider({
                item: +singleSlider_2.itemscount,
                pause: +singleSlider_2.pause_time,
                speed: +singleSlider_2.change_speed,
                pager: $pager,
                gallery: $thumb,
                pauseOnHover: +singleSlider_2.pause_on_hover,
                thumbItem: +hugeitSliderObj.thumb_count_slides,
                controls: +hugeitSliderObj.show_arrows,
                view: singleSlider_2.view,
                maxWidth: singleSlider_2.width,
                maxHeight: singleSlider_2.height
            });
            break;
        case 'thumb_view':
            var $pager = false, $thumb = false;
    
            if (singleSlider_2.pager === '1') {
                $pager = true;
                $thumb = true;
            }
    
            slider = jQuery('#slider_2').RSlider({
                item: 1,
                view: singleSlider_2.view,
                maxWidth: singleSlider_2.width,
                maxHeight: singleSlider_2.height,
                mode: singleSlider_2.mode,
                speed: +singleSlider_2.change_speed,
                pauseOnHover: singleSlider_2.pause_on_hover === '1',
                pause: +singleSlider_2.pause_time,
                controls: singleSlider_2.controls === '1',
                fullscreen: singleSlider_2.fullscreen === '1',
                vertical: singleSlider_2.vertical === '1',
                sliderHeight: +singleSlider_2.height,
                vThumbWidth: +singleSlider_2.vthumbwidth,
                hThumbHeight: +singleSlider_2.hthumbheight,
                thumbItem: 5,
                thumbMargin: +singleSlider_2.thumbmargin,
                thumbPosition: singleSlider_2.thumbposition === '1',
                thumbControls: singleSlider_2.thumbcontrols === '1',
                pager: $pager,
                gallery: $thumb,
                dragdrop: singleSlider_2.dragdrop === '1',
                swipe: singleSlider_2.swipe === '1',
                thumbdragdrop: singleSlider_2.thumbdragdrop === '1',
                thumbswipe: singleSlider_2.thumbswipe === '1',
                title: singleSlider_2.titleonoff === '1',
                description: singleSlider_2.desconoff === '1',
                titlesymbollimit: +singleSlider_2.titlesymbollimit,
                descsymbollimit: 96
            });
            break;
    }
    

    });

    jQuery(window).load(function () {
jQuery('.slider_lightbox_2').lightbox({
slideAnimationType: singleSlider_2.slide_effect,
arrows: singleSlider_2.arrows_style,
openCloseType: singleSlider_2.open_close_effect
});
});


    .share_buttons_2 {
    width: auto;
    height: auto;
    margin-top: 10px
    }
    /*
    Share buttons hover styles
    */
    .icon-link_2 {
    width: 50px;
    height: 50px;
    background-color: #666;
    line-height: 50px;
    text-align: center;
    vertical-align: middle;
    display: inline-block;
    cursor: pointer;
    outline: none;
    margin: 5px;
    box-sizing: content-box;
    }

    .icon-link_2.fill.share_buttons_facebook_2 {
    background-color: #fff;
    }

    .icon-link_2.fill.share_buttons_facebook_2 .fa-facebook {
    color: #3b5998;
    -webkit-transition: color 150ms ease-in-out;
    transition: color 150ms ease-in-out;
    }

    .icon-link_2.fill.share_buttons_twitter_2 {
    background-color: #fff;
    }

    .icon-link_2.fill.share_buttons_twitter_2 .fa-twitter {
    color: #00aced;
    -webkit-transition: color 150ms ease-in-out;
    transition: color 150ms ease-in-out;
    }

    .icon-link_2.fill.share_buttons_gp_2 {
    background-color: #fff;
    }

    .icon-link_2.fill.share_buttons_gp_2 .fa-google-plus {
    color: #dd4b39;
    -webkit-transition: color 150ms ease-in-out;
    transition: color 150ms ease-in-out;
    }

    .icon-link_2.fill.share_buttons_pinterest_2 {
    background-color: #fff;
    }

    .icon-link_2.fill.share_buttons_pinterest_2 .fa-pinterest {
    color: #b81621;
    -webkit-transition: color 150ms ease-in-out;
    transition: color 150ms ease-in-out;
    }

    .icon-link_2.fill.share_buttons_linkedin_2 {
    background-color: #fff;
    }

    .icon-link_2.fill.share_buttons_linkedin_2 .fa-linkedin {
    color: #007bb6;
    -webkit-transition: color 150ms ease-in-out;
    transition: color 150ms ease-in-out;
    }

    .icon-link_2.fill.share_buttons_tumblr_2 {
    background-color: #fff;
    }

    .icon-link_2.fill.share_buttons_tumblr_2 .fa-tumblr {
    color: #32506d;
    -webkit-transition: color 150ms ease-in-out;
    transition: color 150ms ease-in-out;
    }

    .icon-link_2.share_buttons_facebook_2 {
    border: 2px solid #3b5998;
    }

    .icon-link_2.share_buttons_twitter_2 {
    border: 2px solid #00aced;
    }

    .icon-link_2.share_buttons_gp_2 {
    border: 2px solid #dd4b39;
    }

    .icon-link_2.share_buttons_pinterest_2 {
    border: 2px solid #b81621;
    }

    .icon-link_2.share_buttons_linkedin_2 {
    border: 2px solid #007bb6;
    }

    .icon-link_2.share_buttons_tumblr_2 {
    border: 2px solid #32506d;
    }

    .icon-link_2 .fa-facebook {
    color: #3b5998;
    -webkit-transition: color 150ms ease-in-out;
    transition: color 150ms ease-in-out;
    }

    .icon-link_2 .fa-twitter {
    color: #00aced;
    -webkit-transition: color 150ms ease-in-out;
    transition: color 150ms ease-in-out;
    }

    .icon-link_2 .fa-google-plus {
    color: #dd4b39;
    -webkit-transition: color 150ms ease-in-out;
    transition: color 150ms ease-in-out;
    }

    .icon-link_2 .fa-pinterest {
    color: #b81621;
    -webkit-transition: color 150ms ease-in-out;
    transition: color 150ms ease-in-out;
    }

    .icon-link_2 .fa-linkedin {
    color: #007bb6;
    -webkit-transition: color 150ms ease-in-out;
    transition: color 150ms ease-in-out;
    }

    .icon-link_2 .fa-tumblr {
    color: #32506d;
    -webkit-transition: color 150ms ease-in-out;
    transition: color 150ms ease-in-out;
    }

    .icon-link_2 .fa {
    color: #fff;
    line-height: 49px;
    font-size: 26px;
    }

    @media screen and (max-width: 768px){
    .icon-link_2 {
    width: 30px;
    height: 30px;
    line-height: 30px;
    }

    .icon-link_2 .fa {
line-height: 31px;
font-size: 15px;
}


    }

    /* Lightbox styles */

    .lightbox_iframe_cover {position:absolute;width:100%;height:100%;z-index:999}
    a.slider_lightbox > div {width: 100% !important; height: 100% !important; padding: 0 !important}
    .rwd-object{border:10px solid white}
    .rwd-icon{speak:none;font-style:normal;font-weight:400;font-variant:normal;text-transform:none;line-height:1;-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale}
    .rwd-arrows .rwd-next,.rwd-arrows .rwd-prev{background-color:rgba(0,0,0,.9);border-radius:2px;color:#999;cursor:pointer;display:block;font-size:22px;margin-top:-10px;padding:8px 8px 7px;position:absolute;z-index:1080}
    .rwd-arrows .rwd-next.disabled,.rwd-arrows .rwd-prev.disabled{pointer-events:none;opacity:.5}
    .rwd-toolbar{z-index:1082;left:0;position:absolute;top:0;width:100%}
    @media screen and (max-width:768px){.rwd-toolbar{z-index:9999999}}
    .rwd-bar .rwd-icon,.rwd-toolbar .rwd-icon{cursor:pointer;color:#999;float:right;font-size:24px;line-height:27px;text-align:center;text-decoration:none!important;outline:0;-webkit-transition:color .2s linear;-o-transition:color .2s linear;transition:color .2s linear}
    .rwd-bar .rwd-icon{position:absolute;bottom:0;z-index:1081}
    .rwd-icon svg{cursor:pointer}
    .rwd-bar .rwd-icon:hover,.rwd-toolbar .rwd-icon:hover{color:#FFF}
    .rwd-bar .rwd-icon0:hover,.rwd-toolbar .rwd-icon0:hover,.rwd-arrows .rwd-icon0:hover{color:#000}
    .rwd-arrows .rwd-prev, .rwd-arrows .rwd-next, .rwd-close {width: 46px;height: 46px;background:url(https://boffosocko.com/wp-content/plugins/slider-image/assets/images/front/arrows/slightbox_arrows.png);}
    .rwd-arrows.arrows_1 .rwd-next {background-position: 227px 164px;}
    .rwd-arrows.arrows_1 .rwd-prev {background-position: 277px 164px;}
    .rwd-close.arrows_1 {width: 25px;height: 25px;background-position: 266px 194px;background-color: #fff;border-radius: 50%;}
    .rwd-arrows.arrows_2 .rwd-next {background-position: 227px 110px;}
    .rwd-arrows.arrows_2 .rwd-prev {background-position: 277px 110px;}
    .rwd-close.arrows_2 {width: 25px;height: 25px;background-position: 266px 194px;background-color: #fff;border-radius: 50%;}
    .rwd-arrows.arrows_3 .rwd-next {background-position: 227px 63px;}
    .rwd-arrows.arrows_3 .rwd-prev {background-position: 277px 63px;}
    .rwd-close.arrows_3 {width: 25px;height: 25px;background-position: 217px 195px;background-color: #fff;border-radius: 50%;}
    .rwd-arrows.arrows_4 .rwd-next {background-position: 90px 167px;}
    .rwd-arrows.arrows_4 .rwd-prev {background-position: 131px 167px;}
    .rwd-close.arrows_4 {width: 30px;height: 30px;background-position: 38px 158px;}
    .rwd-arrows.arrows_5 .rwd-next {background-position: 97px 108px;}
    .rwd-arrows.arrows_5 .rwd-prev {background-position: 140px 108px;}
    .rwd-close.arrows_5 {width: 25px;height: 25px;background-position: 43px 100px;}
    .rwd-arrows.arrows_6 .rwd-next {background-position: 95px 63px;}
    .rwd-arrows.arrows_6 .rwd-prev {background-position: 139px 63px;}
    .rwd-close.arrows_6 {width: 35px;height: 35px;background-position: 48px 57px;}
    .barCont{background:rgba(0,0,0,.9);width:100%;height:45px;position:absolute;bottom:0;z-index:1071}
    #rwd-counter{color:#999;display:inline-block;font-size:16px;padding-top:12px;vertical-align:middle}
    .rwd-bar #rwd-counter{position:absolute;bottom:11px;left:50%;transform:translateX(-50%);z-index:1090}
    .rwd-next,.rwd-prev,.rwd-toolbar{opacity:1;-webkit-transition:-webkit-transform .35s cubic-bezier(0,0,.25,1) 0s,opacity .35s cubic-bezier(0,0,.25,1) 0s,color .2s linear;-moz-transition:-moz-transform .35s cubic-bezier(0,0,.25,1) 0s,opacity .35s cubic-bezier(0,0,.25,1) 0s,color .2s linear;-o-transition:-o-transform .35s cubic-bezier(0,0,.25,1) 0s,opacity .35s cubic-bezier(0,0,.25,1) 0s,color .2s linear;transition:transform .35s cubic-bezier(0,0,.25,1) 0s,opacity .35s cubic-bezier(0,0,.25,1) 0s,color .2s linear}
    .rwd-cont .rwd-video-cont{display:inline-block;vertical-align:middle;max-width:1140px;max-height:100%;width:100%;padding:0 5px;top:50%;transform:translateY(-50%);position:relative}
    .rwd-cont .rwd-container,.rwd-cont .rwd-image{max-width:100%;max-height:100%;transform:translateY(-50%);-ms-transform: translateY(-50%);-webkit-transform: translateY(-50%);-moz-transform: translateY(-50%);-o-transform: translateY(-50%);}
    .rwd-cont .rwd-video{width:100%;height:0;padding-bottom:56.25%;overflow:hidden;position:relative}
    .rwd-cont .rwd-video .rwd-object{display:inline-block;position:absolute;top:0;left:0;width:100%!important;height:100%!important}
    .rwd-cont .rwd-video .rwd-video-play{width:84px;height:59px;position:absolute;left:50%;top:50%;margin-left:-42px;margin-top:-30px;z-index:1080;cursor:pointer}
    .rwd-cont .rwd-video-object{width:100%!important;height:100%!important;position:absolute;top:0;left:0}
    .rwd-cont .rwd-has-video .rwd-video-object{visibility:hidden}
    .rwd-cont .rwd-has-video.rwd-video-playing .rwd-object,.rwd-cont .rwd-has-video.rwd-video-playing .rwd-video-play{display:none}
    .rwd-cont .rwd-has-video.rwd-video-playing .rwd-video-object{visibility:visible}
    .rwd-autoplay-button{left:50px}
    .rwd-autoplay-button > .pause_bg{display:none}
    .rwd-cont .rwd-caret{border-left:10px solid transparent;border-right:10px solid transparent;border-top:10px dashed;bottom:-10px;display:inline-block;height:0;left:50%;margin-left:-5px;position:absolute;vertical-align:middle;width:0}
    .rwd-cont{width:100%;height:100%;position:fixed;top:0;left:0;z-index:9999999;opacity:0;-webkit-transition:opacity .15s ease 0s;-o-transition:opacity .15s ease 0s;transition:opacity .15s ease 0s}
    .rwd-cont *{-webkit-box-sizing:border-box;-moz-box-sizing:border-box;box-sizing:border-box}
    .rwd-cont.rwd-visible{opacity:1}
    .rwd-cont.rwd-support .rwd-item.rwd-current,.rwd-cont.rwd-support .rwd-item.rwd-next-slide,.rwd-cont.rwd-support .rwd-item.rwd-prev-slide{-webkit-transition-duration:inherit!important;transition-duration:inherit!important;-webkit-transition-timing-function:inherit!important;transition-timing-function:inherit!important}
    .rwd-cont .rwd-container{height:100%;width:100%;position:relative;overflow:hidden;margin-left:auto;margin-right:auto;top:50%;overflow:inherit}
    .rwd-cont .cont-inner{width:100%;height:100%;position:absolute;left:0;top:0;white-space:nowrap}
    .rwd-cont .contInner{width:40%;height:100%;position:absolute;left:60%;white-space:nowrap;z-index: 1200;background: black}
    .rwd-cont.rwd-noSupport .rwd-current,.rwd-cont.rwd-support .rwd-current,.rwd-cont.rwd-support .rwd-next-slide,.rwd-cont.rwd-support .rwd-prev-slide{display:inline-block!important}
    .rwd-cont .rwd-img-wrap,.rwd-cont .rwd-item{display:inline-block;text-align:center;position:absolute;width:100%;height:100%}
    .rwd-cont .rwd-img-wrap{position:absolute;padding:0 5px;left:0;right:0;top:0;bottom:0}
    .rwd-cont .rwd-item.rwd-complete{background-image:none}
    .rwd-cont .rwd-item.rwd-current{z-index:1060}
    .rwd-cont .rwd-image{display:inline-block;vertical-align:middle;width:auto !important;height:auto !important;top:50%;position:relative}
    .rwd-cont.rwd-show-after-load .rwd-item .rwd-object,.rwd-cont.rwd-show-after-load .rwd-item .rwd-video-play{opacity:0;-webkit-transition:opacity .15s ease 0s;-o-transition:opacity .15s ease 0s;transition:opacity .15s ease 0s}
    .rwd-cont.rwd-show-after-load .rwd-item.rwd-complete .rwd-object,.rwd-cont.rwd-show-after-load .rwd-item.rwd-complete .rwd-video-play{opacity:1}
    .rwd-overlay{position:fixed;top:0;left:0;right:0;bottom:0;z-index:9999997;background:rgba(0,0,0,.7);opacity:0;-webkit-transition:opacity .15s ease 0s;-o-transition:opacity .15s ease 0s;transition:opacity .15s ease 0s}
    .rwd-overlay.in{opacity:1}
    .rwd-container .rwd-thumb-cont {position: absolute;width: 100%;z-index: 1080}
    .rwd-container .rwd-thumb {padding: 10px 0;height: 100%}
    .rwd-container .rwd-thumb-item {border-radius: 5px;float: left;overflow: hidden;cursor: pointer;height: 100%;margin-bottom: 5px;}
    @media (min-width: 768px) {.rwd-container .rwd-thumb-item {-webkit-transition: border-color 0.25s ease;-o-transition: border-color 0.25s ease;transition: border-color 0.25s ease;}}
    .rwd-container .rwd-thumb-item img {width: 100%;height: 100%;object-fit: cover;}
    .rwd-container .rwd-toggle-thumb {background-color: #0D0A0A;border-radius: 2px 2px 0 0;color: #999;cursor: pointer;font-size: 24px;height: 39px;line-height: 27px; padding: 5px 0;position: absolute;left: 20px;text-align: center;top: -39px;width: 50px;}

    /* Open/Close effects */
    .rwd-container.open_1 {animation: unfoldIn 1s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    .rwd-container.close_1 {animation: unfoldOut 1s .3s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    @keyframes unfoldIn {0% {transform: translateY(-50%) scaleY(.002);}50% {transform: translateY(-50%) scaleY(.002);}100% {transform: translateY(-50%) scaleY(1);}}
    @keyframes unfoldOut {0% {transform: translateY(-50%) scaleY(1);}50% {transform: translateY(-50%) scaleY(.002);}100% {transform: translateY(-50%) scaleY(.002);}}
    .rwd-container.open_2 {animation: blowUpIn .5s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    .rwd-container.close_2 {animation: blowUpOut .5s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    @keyframes blowUpIn {0% {transform: translateY(-50%) scale(0);}100% {transform: translateY(-50%) scale(1);}}
    @keyframes blowUpOut {0% {transform: translateY(-50%) scale(1);opacity:1;}100% {transform: translateY(-50%) scale(0);opacity:0;}}
    .rwd-container.open_3 {animation: roadRunnerIn .3s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    .rwd-container.close_3 {animation: roadRunnerOut .5s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    @keyframes roadRunnerIn {0% {transform:translate(-1500px, -50%) skewX(50deg) scaleX(1.3);}70% {transform:translate(30px, -50%) skewX(-25deg) scaleX(.9);}100% {transform:translate(0px, -50%) skewX(0deg) scaleX(1);}}
    @keyframes roadRunnerOut {0% {transform:translate(0px, -50%) skewX(0deg) scaleX(1);}30% {transform:translate(-30px, -50%) skewX(-25deg) scaleX(.9);}100% {transform:translate(1500px, -50%) skewX(50deg) scaleX(1.3);}}
    .rwd-container.open_4 {animation: runnerIn .3s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    .rwd-container.close_4 {animation: runnerOut .5s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    @keyframes runnerIn {0% {transform:translate(-1500px, -50%);}70% {transform:translate(30px, -50%);}100% {transform:translate(0px, -50%);}}
    @keyframes runnerOut {0% {transform:translate(0px, -50%);}30% {transform:translate(-30px, -50%);}100% {transform:translate(1500px, -50%);}}
    .rwd-container.open_5 {animation: rotateIn .3s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    .rwd-container.close_5 {animation: rotateOut .5s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    @-ms-keyframes rotateIn {from {-ms-transform: translateY(-50%) rotate(0deg);} to { -ms-transform: translateY(-50%)rotate(360deg);}}
    @-moz-keyframes rotateIn {from {-moz-transform: translateY(-50%) rotate(0deg);} to { -moz-transform: translateY(-50%)rotate(360deg);}}
    @-webkit-keyframes rotateIn {from {-webkit-transform: translateY(-50%) rotate(0deg);} to { -webkit-transform: translateY(-50%)rotate(360deg);}}
    @keyframes rotateIn {from {transform: translateY(-50%) rotate(0deg);} to { transform: translateY(-50%)rotate(360deg);}}
    @-ms-keyframes rotateOut {from {-ms-transform: translateY(-50%) rotate(360deg);} to { -ms-transform: translateY(-50%)rotate(0deg);}}
    @-moz-keyframes rotateOut {from {-moz-transform: translateY(-50%) rotate(360deg);} to { -moz-transform: translateY(-50%)rotate(0deg);}}
    @-webkit-keyframes rotateOut {from {-webkit-transform: translateY(-50%) rotate(360deg);} to { -webkit-transform: translateY(-50%)rotate(0deg);}}
    @keyframes rotateOut {from {transform: translateY(-50%) rotate(360deg);} to { transform: translateY(-50%)rotate(0deg);}}
    .rwd-container.open_1_r {animation: unfold_In 1s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    .rwd-container.close_1_r {animation: unfold_Out 1s .3s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    @keyframes unfold_In {0% {transform: translateY(-50%) scaleX(.002);}50% {transform: translateY(-50%) scaleX(.002);}100% {transform: translateY(-50%) scaleX(1);}}
    @keyframes unfold_Out {0% {transform: translateY(-50%) scaleX(1);}50% {transform: translateY(-50%) scaleX(.002);}100% {transform: translateY(-50%) scaleX(.002);}}
    .rwd-container.open_2_r {animation: blowUp_In .5s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    .rwd-container.close_2_r {animation: blowUp_Out .5s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    @keyframes blowUp_In {0% {transform: translateY(-50%) scale(2);}100% {transform: translateY(-50%) scale(1);}}
    @keyframes blowUp_Out {0% {transform: translateY(-50%) scale(1);opacity:1;}100% {transform: translateY(-50%) scale(2);opacity:0;}}
    .rwd-container.open_3_r {animation: roadRunner_In .3s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    .rwd-container.close_3_r {animation: roadRunner_Out .5s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    @keyframes roadRunner_In {0% {transform:translate(1500px, -50%) skewX(50deg) scaleX(1.3);}70% {transform:translate(-30px, -50%) skewX(-25deg) scaleX(.9);}100% {transform:translate(0px, -50%) skewX(0deg) scaleX(1);}}
    @keyframes roadRunner_Out {0% {transform:translate(0px, -50%) skewX(0deg) scaleX(1);}30% {transform:translate(30px, -50%) skewX(-25deg) scaleX(.9);}100% {transform:translate(-1500px, -50%) skewX(50deg) scaleX(1.3);}}
    .rwd-container.open_4_r {animation: runner_In .3s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    .rwd-container.close_4_r {animation: runner_Out .5s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    @keyframes runner_In {0% {transform:translate(1500px, -50%);}70% {transform:translate(-30px, -50%);}100% {transform:translate(0px, -50%);}}
    @keyframes runner_Out {0% {transform:translate(0px, -50%);}30% {transform:translate(30px, -50%);}100% {transform:translate(-1500px, -50%);}}
    .rwd-container.open_5_r {animation: rotate_In .3s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    .rwd-container.close_5_r {animation: rotate_Out .5s cubic-bezier(0.165, 0.840, 0.440, 1.000);}
    @-ms-keyframes rotate_In {from {-ms-transform: translateY(-50%) rotate(360deg);} to { -ms-transform: translateY(-50%)rotate(0deg);}}
    @-moz-keyframes rotate_In {from {-moz-transform: translateY(-50%) rotate(360deg);} to { -moz-transform: translateY(-50%)rotate(0deg);}}
    @-webkit-keyframes rotate_In {from {-webkit-transform: translateY(-50%) rotate(360deg);} to { -webkit-transform: translateY(-50%)rotate(0deg);}}
    @keyframes rotate_In {from {transform: translateY(-50%) rotate(360deg);} to { transform: translateY(-50%)rotate(0deg);}}
    @-ms-keyframes rotate_Out {from {-ms-transform: translateY(-50%) rotate(0deg);} to { -ms-transform: translateY(-50%)rotate(360deg);}}
    @-moz-keyframes rotate_Out {from {-moz-transform: translateY(-50%) rotate(0deg);} to { -moz-transform: translateY(-50%)rotate(360deg);}}
    @-webkit-keyframes rotate_Out {from {-webkit-transform: translateY(-50%) rotate(0deg);} to { -webkit-transform: translateY(-50%)rotate(360deg);}}
    @keyframes rotate_Out {from {transform: translateY(-50%) rotate(0deg);} to { transform: translateY(-50%)rotate(360deg);}}

    /* Effects */
    .rwd-support.rwd-no-trans .rwd-current,.rwd-support.rwd-no-trans .rwd-next-slide,.rwd-support.rwd-no-trans .rwd-prev-slide{-webkit-transition:none 0s ease 0s!important;-moz-transition:none 0s ease 0s!important;-o-transition:none 0s ease 0s!important;transition:none 0s ease 0s!important}
    .rwd-support.rwd-animation .rwd-item,.rwd-support.rwd-use .rwd-item{-webkit-backface-visibility:hidden;-moz-backface-visibility:hidden;backface-visibility:hidden}
    .rwd-support.slider_effect_1 .rwd-item,.rwd-support.slider_effect_3 .rwd-item,.rwd-support.slider_effect_4 .rwd-item,.rwd-support.slider_effect_5 .rwd-item,.rwd-support.slider_effect_6 .rwd-item,.rwd-support.slider_effect_7 .rwd-item,.rwd-support.slider_effect_8 .rwd-item,.rwd-support.slider_effect_9 .rwd-item,.rwd-support.slider_effect_10 .rwd-item{opacity:0}
    .rwd-support.slider_effect_1 .rwd-item.rwd-current{opacity:1}
    .rwd-support.slider_effect_1 .rwd-item.rwd-current,.rwd-support.slider_effect_1 .rwd-item.rwd-next-slide,.rwd-support.slider_effect_1 .rwd-item.rwd-prev-slide{-webkit-transition:opacity .1s ease 0s;-moz-transition:opacity .1s ease 0s;-o-transition:opacity .1s ease 0s;transition:opacity .1s ease 0s}
    .rwd-support.slider_effect_2.rwd-use .rwd-item{opacity:0}
    .rwd-support.slider_effect_2.rwd-use .rwd-item.rwd-prev-slide{-webkit-transform:translate3d(-100%,0,0);transform:translate3d(-100%,0,0)}
    .rwd-support.slider_effect_2.rwd-use .rwd-item.rwd-next-slide{-webkit-transform:translate3d(100%,0,0);transform:translate3d(100%,0,0)}
    .rwd-support.slider_effect_2.rwd-use .rwd-item.rwd-current{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}
    .rwd-support.slider_effect_2.rwd-use .rwd-item.rwd-current,.rwd-support.slider_effect_2.rwd-use .rwd-item.rwd-next-slide,.rwd-support.slider_effect_2.rwd-use .rwd-item.rwd-prev-slide{-webkit-transition:-webkit-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-moz-transition:-moz-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-o-transition:-o-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;transition:transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s}
    .rwd-support.slider_effect_2.rwd-animation .rwd-item{opacity:0;position:absolute;left:0}
    .rwd-support.slider_effect_2.rwd-animation .rwd-item.rwd-prev-slide{left:-100%}
    .rwd-support.slider_effect_2.rwd-animation .rwd-item.rwd-next-slide{left:100%}
    .rwd-support.slider_effect_2.rwd-animation .rwd-item.rwd-current{left:0;opacity:1}
    .rwd-support.slider_effect_2.rwd-animation .rwd-item.rwd-current,.rwd-support.slider_effect_2.rwd-animation .rwd-item.rwd-next-slide,.rwd-support.slider_effect_2.rwd-animation .rwd-item.rwd-prev-slide{-webkit-transition:left 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-moz-transition:left 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-o-transition:left 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;transition:left 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s}
    .rwd-support.slider_effect_3 .rwd-item.rwd-prev-slide{-moz-transform:scale3d(1,0,1) translate3d(-100%,0,0);-o-transform:scale3d(1,0,1) translate3d(-100%,0,0);-ms-transform:scale3d(1,0,1) translate3d(-100%,0,0);-webkit-transform:scale3d(1,0,1) translate3d(-100%,0,0);transform:scale3d(1,0,1) translate3d(-100%,0,0)}
    .rwd-support.slider_effect_3 .rwd-item.rwd-next-slide{-moz-transform:scale3d(1,0,1) translate3d(100%,0,0);-o-transform:scale3d(1,0,1) translate3d(100%,0,0);-ms-transform:scale3d(1,0,1) translate3d(100%,0,0);-webkit-transform:scale3d(1,0,1) translate3d(100%,0,0);transform:scale3d(1,0,1) translate3d(100%,0,0)}
    .rwd-support.slider_effect_3 .rwd-item.rwd-current{-moz-transform:scale3d(1,1,1) translate3d(0,0,0);-o-transform:scale3d(1,1,1) translate3d(0,0,0);-ms-transform:scale3d(1,1,1) translate3d(0,0,0);-webkit-transform:scale3d(1,1,1) translate3d(0,0,0);transform:scale3d(1,1,1) translate3d(0,0,0);opacity:1}
    .rwd-support.slider_effect_3 .rwd-item.rwd-current,.rwd-support.slider_effect_3 .rwd-item.rwd-next-slide,.rwd-support.slider_effect_3 .rwd-item.rwd-prev-slide{-webkit-transition:-webkit-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-moz-transition:-moz-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-o-transition:-o-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;transition:transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s}
    .rwd-support.slider_effect_4 .rwd-item.rwd-prev-slide{-moz-transform:rotate(-360deg);-o-transform:rotate(-360deg);-ms-transform:rotate(-360deg);-webkit-transform:rotate(-360deg);transform:rotate(-360deg)}
    .rwd-support.slider_effect_4 .rwd-item.rwd-next-slide{-moz-transform:rotate(360deg);-o-transform:rotate(360deg);-ms-transform:rotate(360deg);-webkit-transform:rotate(360deg);transform:rotate(360deg)}
    .rwd-support.slider_effect_4 .rwd-item.rwd-current{-moz-transform:rotate(0deg);-o-transform:rotate(0deg);-ms-transform:rotate(0deg);-webkit-transform:rotate(0deg);transform:rotate(0deg);opacity:1}
    .rwd-support.slider_effect_4 .rwd-item.rwd-current,.rwd-support.slider_effect_4 .rwd-item.rwd-next-slide,.rwd-support.slider_effect_4 .rwd-item.rwd-prev-slide{-webkit-transition:-webkit-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-moz-transition:-moz-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-o-transition:-o-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;transition:transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s}
    .rwd-support.slider_effect_5 .rwd-item.rwd-prev-slide{-moz-transform:rotate(360deg);-o-transform:rotate(360deg);-ms-transform:rotate(360deg);-webkit-transform:rotate(360deg);transform:rotate(360deg)}
    .rwd-support.slider_effect_5 .rwd-item.rwd-next-slide{-moz-transform:rotate(-360deg);-o-transform:rotate(-360deg);-ms-transform:rotate(-360deg);-webkit-transform:rotate(-360deg);transform:rotate(-360deg)}
    .rwd-support.slider_effect_5 .rwd-item.rwd-current{-moz-transform:rotate(0deg);-o-transform:rotate(0deg);-ms-transform:rotate(0deg);-webkit-transform:rotate(0deg);transform:rotate(0deg);opacity:1}
    .rwd-support.slider_effect_5 .rwd-item.rwd-current,.rwd-support.slider_effect_5 .rwd-item.rwd-next-slide,.rwd-support.slider_effect_5 .rwd-item.rwd-prev-slide{-webkit-transition:-webkit-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-moz-transition:-moz-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-o-transition:-o-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;transition:transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s}
    .rwd-support.slider_effect_6 .rwd-item.rwd-prev-slide{-webkit-transform:translate3d(-100%,0,0);transform:translate3d(-100%,0,0)}
    .rwd-support.slider_effect_6 .rwd-item.rwd-next-slide{-moz-transform:translate3d(0,0,0) scale(.5);-o-transform:translate3d(0,0,0) scale(.5);-ms-transform:translate3d(0,0,0) scale(.5);-webkit-transform:translate3d(0,0,0) scale(.5);transform:translate3d(0,0,0) scale(.5)}
    .rwd-support.slider_effect_6 .rwd-item.rwd-current{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}
    .rwd-support.slider_effect_6 .rwd-item.rwd-current,.rwd-support.slider_effect_6 .rwd-item.rwd-next-slide,.rwd-support.slider_effect_6 .rwd-item.rwd-prev-slide{-webkit-transition:-webkit-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-moz-transition:-moz-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-o-transition:-o-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;transition:transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s}
    .rwd-support.slider_effect_7 .rwd-item.rwd-prev-slide{-moz-transform:translate3d(0,0,0) scale(.5);-o-transform:translate3d(0,0,0) scale(.5);-ms-transform:translate3d(0,0,0) scale(.5);-webkit-transform:translate3d(0,0,0) scale(.5);transform:translate3d(0,0,0) scale(.5)}
    .rwd-support.slider_effect_7 .rwd-item.rwd-next-slide{-webkit-transform:translate3d(100%,0,0);transform:translate3d(100%,0,0)}
    .rwd-support.slider_effect_7 .rwd-item.rwd-current{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}
    .rwd-support.slider_effect_7 .rwd-item.rwd-current,.rwd-support.slider_effect_7 .rwd-item.rwd-next-slide,.rwd-support.slider_effect_7 .rwd-item.rwd-prev-slide{-webkit-transition:-webkit-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-moz-transition:-moz-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-o-transition:-o-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;transition:transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s}
    .rwd-support.slider_effect_8 .rwd-item.rwd-prev-slide{-webkit-transform:scale3d(1.1,1.1,1.1);transform:scale3d(1.1,1.1,1.1)}
    .rwd-support.slider_effect_8 .rwd-item.rwd-next-slide{-webkit-transform:scale3d(.9,.9,.9);transform:scale3d(.9,.9,.9)}
    .rwd-support.slider_effect_8 .rwd-item.rwd-current{-webkit-transform:scale3d(1,1,1);transform:scale3d(1,1,1);opacity:1}
    .rwd-support.slider_effect_8 .rwd-item.rwd-current,.rwd-support.slider_effect_8 .rwd-item.rwd-next-slide,.rwd-support.slider_effect_8 .rwd-item.rwd-prev-slide{-webkit-transition:-webkit-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity 1s ease 0s;-moz-transition:-moz-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity 1s ease 0s;-o-transition:-o-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity 1s ease 0s;transition:transform 1s cubic-bezier(0,0,.25,1) 0s,opacity 1s ease 0s}
    .rwd-support.slider_effect_9 .rwd-item.rwd-prev-slide{-webkit-transform:translate3d(0,-100%,0);transform:translate3d(0,-100%,0)}
    .rwd-support.slider_effect_9 .rwd-item.rwd-next-slide{-webkit-transform:translate3d(0,100%,0);transform:translate3d(0,100%,0)}
    .rwd-support.slider_effect_9 .rwd-item.rwd-current{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}
    .rwd-support.slider_effect_9 .rwd-item.rwd-current,.rwd-support.slider_effect_9 .rwd-item.rwd-next-slide,.rwd-support.slider_effect_9 .rwd-item.rwd-prev-slide{-webkit-transition:-webkit-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-moz-transition:-moz-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;-o-transition:-o-transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s;transition:transform 1s cubic-bezier(0,0,.25,1) 0s,opacity .1s ease 0s}
    .rwd-support.slider_effect_10 .rwd-item.rwd-prev-slide {-moz-transform: scale3d(0, 0, 0) translate3d(-100%, 0, 0);-o-transform: scale3d(0, 0, 0) translate3d(-100%, 0, 0);-ms-transform: scale3d(0, 0, 0) translate3d(-100%, 0, 0);-webkit-transform: scale3d(0, 0, 0) translate3d(-100%, 0, 0);transform: scale3d(0, 0, 0) translate3d(-100%, 0, 0);}
    .rwd-support.slider_effect_10 .rwd-item.rwd-next-slide {-moz-transform: scale3d(0, 0, 0) translate3d(100%, 0, 0);-o-transform: scale3d(0, 0, 0) translate3d(100%, 0, 0);-ms-transform: scale3d(0, 0, 0) translate3d(100%, 0, 0);-webkit-transform: scale3d(0, 0, 0) translate3d(100%, 0, 0);transform: scale3d(0, 0, 0) translate3d(100%, 0, 0);}
    .rwd-support.slider_effect_10 .rwd-item.rwd-current {-moz-transform: scale3d(1, 1, 1) translate3d(0, 0, 0);-o-transform: scale3d(1, 1, 1) translate3d(0, 0, 0);-ms-transform: scale3d(1, 1, 1) translate3d(0, 0, 0);-webkit-transform: scale3d(1, 1, 1) translate3d(0, 0, 0);transform: scale3d(1, 1, 1) translate3d(0, 0, 0);opacity: 1;}
    .rwd-support.slider_effect_10 .rwd-item.rwd-prev-slide, .rwd-support.slider_effect_10 .rwd-item.rwd-next-slide, .rwd-support.slider_effect_10 .rwd-item.rwd-current {-webkit-transition: -webkit-transform 1s cubic-bezier(0, 0, 0.25, 1) 0s, opacity 1s ease 0s;=moz-transition: -moz-transform 1s cubic-bezier(0, 0, 0.25, 1) 0s, opacity 1s ease 0s;-o-transition: -o-transform 1s cubic-bezier(0, 0, 0.25, 1) 0s, opacity 1s ease 0s;transition: transform 1s cubic-bezier(0, 0, 0.25, 1) 0s, opacity 1s ease 0s;}

    /* Lightbox styles end */

    ul#slider_2 {
    margin: 0;
    width: 100%;
    height: 100%;
    max-width: 815px;
    max-height: 400px;
    overflow: visible;
    padding: 0;
    }

    .slider_2 {
    width: 100%;
    height: 100%;
    max-width: 815px;
    max-height: 400px;
    margin: 0 auto;}

    .huge-it-wrap:after,
    .huge-it-slider:after,
    .huge-it-thumb-wrap:after,
    .huge-it-arrows:after,
    .huge-it-caption:after {
    content: “.”;
    display: block;
    height: 0;
    clear: both;
    line-height: 0;
    visibility: hidden;
    }

    .video_cover, .playSlider, .pauseSlider, div[class*=playButton] {
    display: none !important;
    }

    .huge-it-thumb-wrap .video_cover {
    display: block !important;
    }

    iframe.huge_it_vimeo_iframe {
    height: 400px;
    }

    div[class*=slider-loader-] {
    background: rgba(0, 0, 0, 0) url(https://boffosocko.com/wp-content/plugins/slider-image/assets/images/front/loading/loading1.gif) no-repeat center;
    height: 90px;
    overflow: hidden;
    position: absolute;
    top: 155px;;
    width: 815px;;
    z-index: 3;
    }

    .huge-it-wrap {
    opacity: 0;
    position: relative;
    border: 0px solid #ffffff;
    -webkit-border-radius: 0px;
    -moz-border-radius: 0px;
    border-radius: 0px;
    overflow: hidden;;
    }

    .huge-it-slide-bg {
    background: rgba(255,255,255,);
    height: 100%}

    .huge-it-caption {
    position: absolute;
    display: block;
    }

    .huge-it-caption div {
    padding: 10px 20px;
    line-height: normal;
    }

    .slider-title {
    width: calc(30% – 20px);
    margin: 10px;
    font-size: 13px;
    color: #000000;
    text-align: right;
    background: rgba(255,255,255,0.7);
    border: 0px solid #ffffff;
    border-radius: 4px;
    right: 0 !important; top: 0;}

    .slider-description {
    width: calc(70% – 20px);
    margin: 10px;
    font-size: 13px;
    color: #ffffff;
    text-align: justify;
    background: rgba(0,0,0,0.7);

    border: 0px solid #ffffff;
border-radius: 0px;


    right: 0 !important; bottom: 0;}

    .slider_2 .huge-it-slider > li {
    list-style: none;
    filter: alpha(opacity=0);
    opacity: 0;
    width: 100%;
    height: 100%;
    margin: 0 -100% 0 0;
    padding: 0;
    float: left;
    position: relative;
    ;
    overflow: hidden;
    }

    .slider_2 .huge-it-slider > li > a {
    display: block;
    padding: 0;
    background: none;
    -webkit-border-radius: 0;
    -moz-border-radius: 0;
    border-radius: 0;
    width: 100%;
    height: 100%;
    }

    .slider_2 .huge-it-slider > li img {
    max-width: 100%;
    max-height: 100%;
    margin: 0;
    cursor: pointer;
    }

    .slider_2 .huge-it-slide-bg, .slider_2 .huge-it-slider > li, .slider_2 .huge-it-slider > li > a, .slider_2 .huge-it-slider > li img {
    ;
    }

    .huge-it-dot-wrap {
    position: absolute;
    top: 5px;height: 20px; left: 50%;
    transform: translateX(-50%);
    z-index: 999;
    }

    .huge-it-dot-wrap a {
    -webkit-border-radius: 8px;
    -moz-border-radius: 8px;
    border-radius: 8px;
    cursor: pointer;
    display: block;
    float: left;
    height: 11px;
    margin: 2px !important;
    position: relative;
    text-align: left;
    text-indent: 9999px;
    width: 11px !important;
    background: #000000;
    box-shadow: none;
    }

    .huge-it-dot-wrap a.active:focus, .huge-it-dot-wrap a:focus,
    .huge-it-thumb-wrap > a:focus, .huge-it-thumb-wrap > a.active:focus {
    outline: none;
    }

    .huge-it-dot-wrap a:hover {
    background: #000000;
    box-shadow: none !important;
    }

    .huge-it-dot-wrap a.active {
    background: #ffffff;
    box-shadow: none;
    }

    .huge-it-thumb-wrap {
    background: #FFFFFF;
    height: 105px;
    margin-left: 0;
    ;
    }

    .huge-it-thumb-wrap a.active img {
    border-radius: 5px;
    opacity: 1;
    }

    .huge-it-thumb-wrap > a {
    height: 100px;
    display: block;
    float: left;
    position: relative;
    -moz-box-sizing: border-box;
    -webkit-box-sizing: border-box;
    box-sizing: border-box;
    background: #FFFFFF;
    }

    .huge-it-thumb-wrap a img {
    opacity: 0.5;
    height: 100px;
    width: 100%;
    display: block;
    -ms-interpolation-mode: bicubic;
    box-shadow: none !important;
    }

    a.thumb_arr {
    position: absolute;
    height: 20px;
    width: 15px;
    bottom: 40px;
    z-index: 100;
    box-shadow: none;
    }

    a.thumb_prev {
    left: 5px;
    width: 15px;
    height: 20px;
    background: url(https://boffosocko.com/wp-content/plugins/slider-image/assets/images/front/arrows/arrows1.png) left top no-repeat;
    background-size: 200%;
    }

    a.thumb_next {
    right: 5px;
    width: 15px;
    height: 20px;
    background: url(https://boffosocko.com/wp-content/plugins/slider-image/assets/images/front/arrows/arrows1.png) right top no-repeat;
    background-size: 200%;
    }

    .huge-it-grid {
    position: absolute;
    overflow: hidden;
    width: 100%;
    height: 100%;
    display: none;
    }

    .huge-it-gridlet {
    position: absolute;
    opacity: 1;
    }

    .huge-it-arrows .huge-it-next,
    .huge-it-arrows .huge-it-prev {
    z-index: 1;
    }

    .huge-it-arrows:hover .huge-it-next,
    .huge-it-arrows:hover .huge-it-prev {
    z-index: 2;
    }

    .huge-it-arrows {
    cursor: pointer;
    height: 40px;
    margin-top: -20px;
    position: absolute;
    top: 50%;
    /transform: translateY(-50%);/
    width: 40px;
    z-index: 2;
    color: rgba(0, 0, 0, 0);
    outline: none;
    box-shadow: none !important;
    }

    .huge-it-arrows:hover, .huge-it-arrows:active, .huge-it-arrows:focus,
    .huge-it-dot-wrap a:hover, .huge-it-dot-wrap a:active, .huge-it-dot-wrap a:focus {
    outline: none;
    box-shadow: none !important;
    }

    .ts-arrow:hover {
    opacity: .95;
    text-decoration: none;
    }

    .huge-it-prev {
    left: 0;
    margin-top: -21px;
    height: 43px;
    width: 29px;
    background: url(https://boffosocko.com/wp-content/plugins/slider-image/assets/images/front/arrows/arrows1.png) left top no-repeat;
    background-size: 200%;
    }

    .huge-it-next {
    right: 0;
    margin-top: -21px;
    height: 43px;
    width: 29px;
    background: url(https://boffosocko.com/wp-content/plugins/slider-image/assets/images/front/arrows/arrows1.png) right top no-repeat;
    background-size: 200%;

    }

    Brief Philosophy
    I use this website as my primary hub for online presence and communication and to some extent as my online commonplace book. I try to follow the tenets of the IndieWeb movement by publishing on my own site and owning all of my own data. When I participate in social silos (Facebook, Twitter, Instagram, etc.), I post here first and syndicate duplicates out to them (POSSE). These posts either originate from here or my social stream. You’re welcome to subscribe to or consume them in any manner or on any platform you prefer.
    Syndicated copies to:

    Reply

31. WordPress is open source CMS software used by many on the Indieweb as well as a blog hosting service.

    Reply

32. Both for my own benefit as well as for that of others who may be following along, I realize that I’ve been tagging a lot of material on my site with the broad category of “IndieWeb”. Some of it is definitely more significant and content rich than others, but in aggregate it may often seem like a firehose. If you’re following the community relatively closely already, you’ll probably be seeing a lot of redundant material.
    As a result, and since it’s easy to do, I’m only going to categorize a much smaller segment of the richer material that I write or which is I deem to be extremely broadly appealing with the IndieWeb category. The remainder of smaller pieces by others, bookmarks, short replies, or other tangential related things (UX, UI, silos, silo quits, etc.) I’m going to use the alternate and separate IndieWeb tag.
    Thus if you’re active in the IndieWeb community and only want my IndieWeb related materials then follow the category  and not the tag. If you’re not closely following the community and want everything then I recommend following the content from both the category and the tag. 
    With the subtle change this may also help IndieWeb related planets like Aaron Parecki’s https://stream.indieweb.org/ or Malcolm Blaney’s https://unicyclic.com/indieweb/ pick up relevant data without needing to do heavy de-duplication for fear of spamming various channels.
    In the coming days/weeks I’ll try to go back into my backlog of posts and re-categorize and re-tag things based on this general scheme.
    My direct content:
    Category Only | feed: https://boffosocko.com/category/indieweb/feed/
    Miscellaneous bookmarks, replies, other content I collect for my commonplace book, etc: 
    Tag Only | feed: https://boffosocko.com/tag/indieweb/feed/
    The firehose of everything IndieWeb related from my site:
    Category AND/OR Tag | feed: https://boffosocko.com/?s=indieweb&feed=rss2
    And of course I still try to  aggregate and orient most of the important pieces in my IndieWeb Collection.

    Syndicated copies to:
    
    
    
    

    Reply

33. Read How to decentralize social media—a brief sketch by Larry Sanger (larrysanger.org)

    The problem about social media is that it is centralized. Centralization empowers massive corporations and governments to steal our privacy and restrict our speech and autonomy.

    Highlights, Quotes, Annotations, & Marginalia

    The social media browser plugins. Here’s the killer feature. Create at least one (could be many competing) browser plugins that enable you to (a) select feeds and then (b) display them alongside a user’s Twitter, Facebook, etc., feeds. (This could be an adaptation of Greasemonkey.) In other words, once this feature were available, you could tell your friends: “I’m not on Twitter. But if you want to see my Tweet-like posts appear in your Twitter feed, then simply install this plugin and input my feed address. You’ll see my posts pop up just as if they were on Twitter. But they’re not! And we can do this because you can control how any website appears to you from your own browser. It’s totally legal and it’s actually a really good idea.” In this way, while you might never look at Twitter or Facebook, you can stay in contact with your friends who are still there—but on your own terms.  ❧

    This is an intriguing idea. In particular, it would be cool if I could input my OPML file of people I’m following and have a plugin like this work with other social readers.
    February 20, 2019 at 12:29PM

    We can look at a later iteration of Everipedia itself as an example. Right now, there is one centralized encyclopedia: Wikipedia. With the Everipedia Network, there will be a protocol that will enable people from all over the web to participate in a much broader project.  ❧

    As I look at this, I can’t help think about my desire to want to be able to link to a wiki in a post and have a Webmention added to that post’s “See Also” or reference section. With the link automatically added to the wiki’s page like this, future readers and editors could have access to my original and could potentially synopsize and include details from my post into the wiki’s article.
    February 20, 2019 at 12:41PM

    But how do we make it happen?  ❧

    Larry, I caught your Twitter conversation with Aaron Parecki earlier about IndieWeb. I’ve added a lot of the open specs he referenced to my own WordPress website with a handful of plugins and would be happy to help you do the same if you like. I think that with some of the IndieWeb tools, it’s always even more impressive if you can see them in action using something you’re already regularly using.
    If nothing else, it’ll give you some direct experience with how the decentralized nature of how these things work. I’m posting my reply to you own my own site and manually syndicating the reply (since you don’t yet support webmention, one of the protocols) which will give at least some idea of how it all works.
    If you’re curious about how you could apply it to your own WordPress site, I’ve collected some research, articles and experiments specific to my experience here: https://boffosocko.com/research/indieweb/
    February 20, 2019 at 12:46PM

    The feed readers. Just as the RSS standard spawned lots of “reader” and “aggregator” software, so there should be similar feed readers for the various data standards described in (1) and the publishers described in (2). While publishers might have built-in readers (as the social media giants all do), the publishing and reading feature sets need to be kept independent, if you want a completely decentralized system.  ❧

    I’ve outlined a bit about how feed readers could be slighly modified to do some of this in the past: https://boffosocko.com/2017/06/09/how-feed-readers-can-grow-market-share-and-take-over-social-media/
    February 20, 2019 at 12:47PM

    Syndicated copies to:
    
    
    
    
    
    
    Twitter icon
    

    Syndicated copies:

    • book

    Reply

34. I really had a grand time at WordCamp Santa Clarita Valley yesterday. I’d like to thank the visionary Joe Simpson, Jr. and his entire group of fantastic organizers and kind volunteers for putting the entire thing together. I couldn’t imagine a better launch for a brand new camp.
    College of the Canyons was a fantastic location for the camp and even had some excellent outdoor patio and dining space for lunch.
    I do wish I’d been able to make my schedule work out to have been able to attend on Friday. I’m particularly bummed that I didn’t get to see Glenn Zucman’s presentation as he’s always doing some of the most interesting and creative things with WordPress. I’ll wait patiently for WordPress.tv to deliver it for me.
    Some of my favorite highlights:

    David Nuon wearing a blonde Richard Dean Anderson wig during his talk MacGyver plays with blocks: Using the Gutenberg editor in new and surprising ways

    Chatting with Kat Christofer of Woo Commerce about how she and the Woo team create better documentation for their product. I think there’s some things we can learn for documenting pieces of the IndieWeb experience with WordPress. She also mentioned the beginning of a new short Mustang road trip.

    Joseph Dickson going old school on Upgrading Kubrick for Gutenberg. His highlighting the fact that the editor is able to better mirror the ultimate output as a time saver is an intriguing idea.
    Not that they aren’t always in general, and I didn’t think about it until reflecting on it today, but I also want to mention the spectacular diversity of speakers and attendees at the camp. It really made for a better and more well-rounded experience. I’ll give all the credit to Joe and his team who I suspect are directly responsible for designing it to be that way from the very beginning.

    On a more personal level, my two favorite parts included:  Seeing the viceral reactions of a handful of people as the proverbial light switch was turned on when they realized the power and flexibility of the posting interfaces provided by micropub clients during my talk. There was also a palpable rush at the end while using a few minutes of extra time demoing some examples of my website and and the power of Micropub, Webmention, and backfeed along with some other IndieWeb goodness. I’ve already had a number of people following up with additional questions, conversations, and emails.
    For those who may have missed them, here is a link to my slides from the Micropub and WordPress talk and a link to some of the bigger pieces I’ve wrtitten about with respect to WordPress and IndieWeb technologies in the past. Naturally, these are only a supplement to the hundreds of others who are working in and documenting the space. 
    I’ll also give a special thanks to Joseph Dickson for the photo/tweet of me just before the talk:

    Micropub Rocks! With @ChrisAldrich @wordcampscv #WCSCV learning about “Micropub and WordPress: Custom Posting Applications” pic.twitter.com/MQnOTFFkWY
    — Joseph Dickson (@joe4ska) April 6, 2019

    https://platform.twitter.com/widgets.js
    Dr. Dianne G. Van Hook University Center on the campus of College of the Canyons Inside the Hook University Center where WordCamp Santa Clarita Valley 2019 was held Clear signage directs pedestrians to WordCamp Santa Clarita at Hook University Center The afterparty for WordCamp Santa Clarita was held at Draconum in Newhall WordCampers from Santa Clarita gathering on the outdoor patio at Draconum

    Hanging out with old friends and new after WordCamp on the patio at Draconum.
    Joseph Dixon, Erik Blair

    Syndicated copies to:
    WordPress
    Twitter icon
    

    Syndicated copies:

    Reply

35. Jeffrey Zeldman does an excellent job of indicating why and what is wrong with the internet and social media and points to IndieWeb.org as a way forward.

    ☛ How did let our beautiful WWW turn into a garbage fire of lies, hate, and privacy violations? I have some thoughts.
    “Nothing Fails Like Success” … by @zeldman in today’s @AListApart.https://t.co/6AqhFGJccr pic.twitter.com/mlGMsCJlku
    — zeldman (@zeldman) April 11, 2019

    https://platform.twitter.com/widgets.js
    If you’re personally using WordPress as a possible solution to those problems, I’m happy to help point to some quicker ways for people to rapidly implement them without struggling as much as many others have along the way.
    (If WordPress isn’t your thing, the wiki has a plethora of other pathways depending on your CMS or programming language of choice–just search. It is abundantly clear that no single CMS is going to dig us out of the hole.)
    I’ve written about and documented how I’ve gotten a lot of IndieWeb related technologies running on my own website. In many cases, these solutions are simple plugin downloads and activations, though it helps to have an idea of what they all do and how they may help.
    I was particularly impressed with Brent Simmons’ post yesterday explaining how he was using his particular talents to further the cause. Though some may feel overwhelmed at the apparent size and scope of the problem, many diverse hands chipping away at small pieces can help to make a major dent in the problem.
    Jen Simmons has indicated a useful paradigm structured around making resolutions with simple concrete steps and deadlines.

    Ok, here’s the deal. Tweet your personal website plan with the hashtag #newwwyear (thanks @jamiemchale!):
    1) When will you start?
    2) What will you try to accomplish?
    3) When is your deadline?
    Improve an existing site. Start a new one. Burn one down & start over. It’s up to you.
    — Jen Simmons (@jensimmons) December 20, 2017

    https://platform.twitter.com/widgets.js
    I have no doubt that even if you’re not a developer or programmer that you can help. If you’re not sure, ask me or others how.
    I hope you’ll join us. Let’s roll up our sleeves and #​LetsFixThis.

    Syndicated copies to: WordPress

    Syndicated copies:

    Reply

36. Interested in becoming part of the #IndieWeb after @t’s talk at #WCUS? I’m happy to help or answer questions. I’ve also got some WordPress specific experiments and documentation (on my own website, of course):
    https://boffosocko.com/research/indieweb/

    Syndicated copies:

    Reply

37. Bookmarking for later, thanks!
    
    

    Reply

38. You just got a mention during the questions and answers 🙂
    
    
    
    

    Reply

39. RT ChrisAldrich: Interested in becoming part of the #IndieWeb after t’s talk at #WCUS? I’m happy to help or answer questions. I’ve also got some WordPress specific experiments and documentation (on my own website, of course):
    boffosocko.com/research/indie…

    Reply

40. Thanks for this, Chris. I read all of your posts but there are many in this that I have missed. Great resource!
    
    
    
    

    Reply

41. Great resource with all kinds of #IndieWeb content. Of interest to #DOoO and #OpenEd folks. #PSUOpen
    
    

    Reply

42. Replied to a tweet thread by John Mark Troyer (Twitter)

    Blogs are designed to never end, only show the last thing you did, and therefore almost always look abandoned.What if, instead of a personal blog, you created a portfolio site and worked on a series of sustainable and discrete projects?— John Mark Troyer (@jtroyer) November 10, 2019

    https://platform.twitter.com/widgets.js

    Yeah, but that’s just another view. I’m thinking overall look and feel of my site. Thinking about changing it to more a portfolio style— Christian Mohn™ (@h0bbel) November 14, 2019

    https://platform.twitter.com/widgets.js

    My problem, or one of them, is that everywhere I look – portfolios are mostly done by more creative types, like designers and so on, so I’m having some problems seeing how I should do it for myself— Christian Mohn™ (@h0bbel) November 14, 2019

    https://platform.twitter.com/widgets.js

    To me, it implies a vision of completion. I wonder if articles can be retrofit into these types of collections. Or maybe I’m not following what you mean by “portfolios”— Matt Broberg (@mbbroberg) November 14, 2019

    https://platform.twitter.com/widgets.js

    I was thinking of anything but displaying by last date – lists of articles by topic, bundling into study guides, etc. Might lead to ideas about other kinds of projects – mini-ebooks, series of talks, collaborative, etc.— John Mark Troyer (@jtroyer) November 14, 2019

    https://platform.twitter.com/widgets.js

    I have no concrete examples (yet) but I haven’t looked really. Driven by 1. seeing dead blogs & realizing blog design trades simplicity for precisely this never-ending treadmill, shaping certain kinds of thinking & content, and…— John Mark Troyer (@jtroyer) November 14, 2019

    https://platform.twitter.com/widgets.js

    2. Listening to podcasts with authors; watching documentaries on artist Olafur Eliasson & Hamilton musical. Thinking how nice it would be to talk about a series of Cool Things you did rather than the rabbit poop of a blog or podcast that you can never wind down cleanly by design.— John Mark Troyer (@jtroyer) November 14, 2019

    https://platform.twitter.com/widgets.js

    I guess that mixed up with speculating if we need personal sites at all when the conversation has shifted to social platforms? Should we publish our everywhere and use IndieWeb/Fediverse tech to syndicate to a central place?— John Mark Troyer (@jtroyer) November 14, 2019

    https://platform.twitter.com/widgets.js

    That’s it.That’s the whole idea. I’ll turn it into a blog post. Then need to look around with fresh eyes for examples, experiment. Maybe it’s just a front page of articles by topic instead date? Or start a new movement of small ebooks? More ideas out there than in my brain.— John Mark Troyer (@jtroyer) November 14, 2019

    https://platform.twitter.com/widgets.js

    Framing things as just using a “blog” in reverse chronological order is a tough one. I might recommend having a website that does much more. It could be a business card, have a blog, have a portfolio, it could have collections, series, etc. The real key at the end of the day is having a website you own and control to put on it what you’d like. This way you can decide not only how to represent yourself on line but how you communicate.
    Perhaps another interesting place to start thinking about this is Mike Caulfield’s post The Garden and the Stream: A Technopastoral, which also looks closely at wikis as a separate framing?
    Other than a blog, another common pattern is to have a /Now page which describes what you’ve been up to lately. (The problem with this is keeping it up to date on a frequent basis, and you might get back to the problem of having a blog which hasn’t been updated in a while.)
    Of course, why not take back control of all of your social presence and put that on your site too? That way your social stream on your site will more frequently be up to date. This is roughly what I do on my site at /blog. It’s not just a stream of longer articles, but of all my social posts, photos, checkins, and other interactions. Of course if you just want the longer form stuff, that’s available too.
    For some examples on portfolios, perhaps try the IndieWeb wiki which has some examples and links to other resources.
    I like John Mark Troyer’s idea of mini-ebooks and collections of projects. I’ve got a collection of some of my IndieWeb experiments with WordPress that touches on his idea, but eventually I’ll roll some of it up into a book of some sort.
    I’ll also indicate another idea being that of having a site that acts like a digital commonplace book, which is roughly how I use my website. I keep a lot of the content primarily for myself, but it does have some social interest for those who may appreciate that I’ve aggregated it in one place.

    I guess that mixed up with speculating if we need personal sites at all when the conversation has shifted to social platforms? Should we publish our everywhere and use IndieWeb/Fediverse tech to syndicate to a central place?
    — John Mark Troyer (@jtroyer) November 14, 2019

    https://platform.twitter.com/widgets.js
    While the conversation has (temporarily?) shifted to social platforms, I don’t think that it’s always going to stay there. The barriers and issues with owning, controlling, and maintaining a website are coming down every day. Why would one want/need dozens or more social sites to communicate when they should be able to do it in one place–on their own site? Just like I can use my phone and phone number with AT&T service to call you on your phone number with Sprint service, I should be able to use WordPress on my domain to chat/@mention you on your domain running any other CMS. Eventually social media will decentralize, though there still may be a place for aggregation hubs for discovery. I’ll mention passingly that individual websites can also act as stand-alone members of the Fediverse. While not the prettiest thing at the moment because of limitations of the Fediverse, you can follow my website here @chrisaldrich from Mastodon and other Fediverse instances. Simultaneously feed readers are improving to better allow users to read what they want without relying on social services to control it for them.

    Two sides of a mirror for sure, although the mf’ers always like to make the API-posted content uglier, and there’s an ineffable “presence” that can get lost with POSSE. Are you “there” or are you just dropping off your posts like some flyer for lessons on a store bulletin board?
    — John Mark Troyer (@jtroyer) November 14, 2019

    https://platform.twitter.com/widgets.js
    In the past, many people have indiscriminately syndicated material from one social site to another, but it generally never looks good unless it’s done very carefully. Naturally none of the corporate silos make this type of syndication easy because it’s not in their financial interest to do so–they’d rather you used their services exclusively. This is part of what makes it look like one is dropping off fliers. However, I would suggest that with a more IndieWeb approach that syndicating via POSSE and using appropriate backfeed via webmention, that one can have not only a reasonably organic experience, but you can add a lot more to a much bigger (and hopefully more substantive) conversation. POSSE is a temporary bandaid until we’ve been able to reshape the web the way we want to consume it rather than being forced into consumption on social media services’ terms.
    Hopefully this post itself is an example of a response to a larger stream of content that provides a bit more space than Twitter’s 280 character limit would have otherwise allowed. This post might also indicate that a conversation online doesn’t need to be so forced and linear or crammed within Twitter’s restrictive confines. Twitter forces us into a stream as a means of getting us to scroll endlessly rather than think, mull, and respond. It’s not unnoticed by me that the tweet that started this thread has branched off into half a dozen different, but related conversations. This makes even Twitter’s UI difficult to navigate and respond to appropriately. We definitely need (and deserve) something better. If they won’t do it for us, then why not take the means of production and do it ourselves.
    You’ve asked some excellent questions. I can’t wait to see your experiments and what you end up making John.

    Syndicated copies to:
    WordPress
    Twitter icon
    
    Twitter icon
    

    Syndicated copies:

    Reply

43. Replied to a post by Helen Hou-Sandí (helen.blog)

    Remember when we used to read each other’s individual blogs? I miss that.

    I not only remember it, but I’ve been actively reliving it by posting everything to my own WordPress site, relying on the power of Webmention for cross-site communication, and reading content with Micropub powered Microsub readers. A quickly growing number of diverse people are doing this too.
    If you’re interested, please do come join us and ask how!

    Syndicated copies to:
    
    

    Syndicated copies:

    • book

    Reply

44. Replied to Five RSS feeds I followed today by Jeremy Felt (jeremyfelt.com)

    I followed several new to me feeds today and then decided—why not share? There may be no other way to rediscover the social network that is blogging.

    Jeremy, it’s great to see someone else following peoples’ content directly from their own websites! I was surprised (but maybe not really) to see that some of the feeds you had followed were those from the IndieWeb community! Did you happen to catch Tantek’s talk at WordCamp US (▶️) just before the State of the Word?
    Coincidentally, I came to your post while playing some feed reading catch up post-WordCamp US and ran across a status update on Helen’s site:

    Remember when we used to read each other’s individual blogs? I miss that.

    I noticed one other person (you) had “liked” it and clicked myself down the rabbit hole that led me to your post. There are still apparently some interesting old-school discovery methods on the open web.
    If you like following interesting sites, I often find Kicks Condor’s HREFHUNT an great regular source for discovery.
    I’m curious what feed reader you use for subscriptions? I wrote a short note the other day about some interesting new developments I’ve been seeing in the feed reader and discovery space.

    And last, but not least, I followed both the IndieNews and This Week in the IndieWeb blogs via the main indieweb.org site as part of an effort to get more familiar with that community and technology.

    If you’d like a crash course on IndieWeb, particularly as it’s applied within WordPress, I’m happy to donate some time to get you up to speed on the next few steps beyond what Tantek outlined. If you’d like to follow more, I have a following page which has a large number of IndieWeb-related developers, designers, and sites including an OPML file for following many of them quickly.
    In any case, welcome to the IndieWeb! I can’t wait to see how your explorations there turn out; I’d love to hear about your experiences in that space. There are a lot of friendly people around to help you get started or chat if you need it.
    And thanks again for tacitly sharing your list of RSS sources. I’d bookmarked Weinberger’s book a short while ago and can’t wait to read it. I’m looking at your other links presently.

    Syndicated copies to:
    Twitter icon
    
    

    Reply

45. Replied to a tweet by Paul Jacobson (Twitter)

    I can’t remember how to mention someone using Webmentions on my WordPress site. @ChrisAldrich, did you write something about this? #indieweb— Paul Jacobson (@pauljacobson) December 23, 2019

    https://platform.twitter.com/widgets.js

    There’s a few quick ways depending on your needs:

    If you’re using the Webmention plugin, it will happen automatically on publish. (If you’re also using it to receive, then I highly recommend using Semantic Linkbacks as well.)
    For quick “manual” webmentions you can use Aaron Parecki’s Telegraph or Kevin Marks’ Mention Tech. Just input your source URL that has a link to a target URL and the services will send the Webmention on your behalf.
    Some sites that receive them will have boxes you can put your URL response in them and click a send button. (See mine below.)

    I also maintain a collection for most of my WordPress IndieWeb-based research, which may answer additional questions or go into more depth. Hopefully the above three can get you started quickly though.

    Syndicated copies to:
    Twitter icon
    
    Twitter icon
    

    Reply

46. In addition to what’s on the IndieWeb wiki, I’ve written quite a bit:  https://boffosocko.com/research/indieweb/.
    If you have specific questions, there are a lot of us who can help in the IndieWeb chat or WordPress specific chat.
    A lot of it depends on what you what to do with it—which features and functionalities. Hopefully one or even a few of the plugins with minimal configuration will get you what you want.
    Syndicating content can be a bit more involved, but only because there are so many methods depending on the level of control you want for the output and what sort of results you may want back from social silos.

    Syndicated copies:

    Reply

47. Editor’s note: This is another in a continuing series of essays about the IndieWeb.

    Where is the IndieWeb?
    Logos
    One might consider the IndieWeb’s indieweb.org wiki-based website and chat the “logos” of IndieWeb. There is a small group of about a hundred active to very active participants who hang out in these spaces on a regular basis, but there are also many who dip in and out over time as they tinker and build, ask advice, get some help, or just to show up and say hello. Because there are concrete places online as well as off (events) for them to congregate, meet, and interact, it’s the most obvious place to find these ideas and people.
    Ethos
    Beyond this there is an even larger group of people online who represent the “ethos” of IndieWeb. Some may have heard the word before, some have a passing knowledge of it, but an even larger number have not. They all act and operate in a way that either seemed natural to them because they grew up in the period of the open web, or because they never felt accepted by the thundering herds in the corporate social enclosures. Many are not necessarily easily found or discovered because they’re not surfaced or highlighted by the sinister algorithms of corporate social media, but through slow and steady work (much like the in person social space) they find each other and interact in various traditional web spaces. Many of them can be found in spaces like Micro.Blog, Tilde Club or NeoCities, or through movements like A Domain of One’s Own. Some can be found through a variety of webrings, via blogrolls, or just following someone’s website and slowly seeing the community of people who stop by and comment. Yes, these discovery methods may involve a little more work, but shouldn’t healthy human interactions require work and care?
    Pathos
    The final group of people, and likely the largest within the community, are those that represent the “pathos” of IndieWeb. The word IndieWeb has not registered with any of them and they suffer with grief in the long shadow of corporate social media wishing they had better user interfaces, better features, different interaction, more meaningful interaction, healthier and kinder interaction. Some may have even been so steeped in big social for so long that they don’t realize that there is another way of being or knowing.
    These people may be found searching for the IndieWeb promised land on silo platforms like Tumblr, WordPress.com, Blogger, or Medium where they have the shadow on the wall of a home on the web where they can place their identities and thoughts. Here they’re a bit more safe from the acceleration of algorithmically fed content and ills of mainstream social. Others are trapped within massive content farms run by multi-billion dollar extractive companies who quietly but steadily exploit their interactions with friends and family.
    The Conversation
    All three of these parts of the IndieWeb, the logos, the ethos, and the pathos comprise the community of humanity. They are the sum of the real conversation online.
    Venture capital backed corporate social media has cleverly inserted themselves between us and our interactions with each other. They privilege some voices not only over others, but often at the expense of others and only to their benefit. We have been developing a new vocabulary for these actions with phrases like “surveillance capitalism”, “data mining”, and analogizing human data as the new “oil” of the 21st century. The IndieWeb is attempting to remove these barriers, many of them complicated, but not insurmountable, technical ones, so that we can have a healthier set of direct interactions with one another that more closely mirrors our in person interactions. By having choice and the ability to move between a larger number of service providers there is an increasing pressure to provide service rather than the growing levels of continued abuse and monopoly we’ve become accustomed to.
    None of these subdivisions—logos, ethos, or pathos—is better or worse than the others, they just are. There is no hierarchy between or among them just as there should be no hierarchy between fellow humans. But by existing, I think one could argue that through their humanity these people are all slowly, but surely making the web a healthier, happier, fun, and more humanized and humanizing place to be.
    I’d appreciate others’ thoughts and perspectives on this regardless of where they choose to post them. 

    Syndicated copies:

    • website

    Reply

48. A refback (remember those?!) today reminded me about this post: Non-technical IndieWeb: Fun, Creativity, Community, and “Content” https://boffosocko.com/2020/12/20/non-technical-indieweb-fun-creativity-community-and-content/
    I should try to add more on #creativity and #fun to my IndieWeb Collection https://boffosocko.com/research/indieweb/

    Syndicated copies:

    Reply

49. @chrisaldrich https://anagora.org/creativityhttps://anagora.org/fun
    [[creativity]] – anagora.org

    Reply

50. If you ever wanted to know about the Indieweb this is a great place to start.
    
    
    

    Reply

51. This Article was mentioned on lobste.rs

    Reply

52. This is a brilliant idea and is broadly what underpins the mission of the IndieWeb space for the past decade. The difference is that it isn’t platform specific and a large portion of it is already built and working! Of course it’s in different stages and forms of usability for various platforms, but most of the building blocks already exist for a broad variety of platforms, including (and especially for) WordPress. 
    Because of the base level design, I can post on my site and syndicate content almost anywhere while often times getting replies and responses back from a number of platforms. Because it’s all built on open specs it means that people on WordPress can communicate directly with those on Drupal, Craft, Hugo, Kirby, Django, a variety of static site generators, Twitter, Mastodon, and almost any platform that chooses to support the broad standards. (Matt Mullenweg has already started down the road to having Tumblr support these building blocks.)
    WordPress already has support for all of the major building blocks and works with a variety of social readers which make reading content and replying to it pretty simple and straightforward. Of course this doesn’t mean that there still isn’t work left to perfect it, smooth the corners, and lower the technical bars, and the costs for a wider diversity of people. For those that don’t want to deal with the hassle and maintenance, there are also several services that support most of the specs out of the box. Micro.blog in particular has a great user interface and does all the heavy lifting for $5/month. Without any cost, you can create an account and join that community using your own WordPress site today. 
    If you’re into the idea, stop by the IndieWeb chat, ask questions, and join the party. I’ve got a collection of posts with a variety of resources, descriptions, how-tos, and videos if you need them: https://boffosocko.com/research/indieweb/
    Here’s a short preview of what some of it looks like in practice: 

    Aside: David Shanske, perhaps we ought to run one of our WordPress IndieWeb install fests one one of these coming weekends to help onboard people? 

    Syndicated copies:

    Reply

53. ?I’m always looking to improve the performance of my website. I’m using the free version of [JetPack Boost] and Google’s PageSpeed Insights services to check…

    Reply

Mentions

• 💬 Khürt Williams
• 💬 Chris Aldrich
• 💬 Brad Enslen
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Cathie LeBlanc
• 💬 This bastard hacked my ACC
• 💬 Evan Hildreth
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Aaron Davis
• 💬 William Borix
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Aaron Davis
• 💬 Aaron Davis
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Khürt Williams
• 💬 Chris Aldrich
• 💬 Juan Hernando
• 💬 Eric Rogers
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich
• 💬 Chris Aldrich

Likes

• 👍 Brad Enslen
• 👍 Kasper Zutterman
• 👍 Phil Barker
• 👍 Pgogy WebStuff
• 👍 Grassroots Journals
• 👍 bourbakis
• 👍 Dan Blickensderfer
• 👍 S Roy Chowdhury
• 👍 Verious B. Smith III
• 👍 Settler in Solidarity
• 👍 Margaret Warren
• 👍 Joe A Simpson Jr #wcus
• 👍 Heinz Wittenbrink
• 👍 Teodora Petkova
• 👍 Noah’s at #wcus
• 👍 Cathie LeBlanc
• 👍 TechnoSiren
• 👍 Alexanne Laplante
• 👍 plasticAudio
• 👍 Aaron Davis
• 👍 Aaron Davis
• 👍 Mike McCallister
• 👍 Jeff
• 👍 Scott Kingery
• 👍 Florian Weil

Reposts

• ♻️ Pgogy WebStuff
• ♻️ Tim Chambers
• ♻️ Teodora Petkova
• ♻️ Noah’s at #wcus
• ♻️ Chris Wiegman
• ♻️ Michael
• ♻️ Amanda J. Rush
• ♻️ Florian Weil

Bookmarks

• 🔖 Amanda
• 🔖 Khürt Williams
• 🔖 John Evdemon