An IndieWeb Podcast: Episode 14 A loose collective of developers and techno-utopians

Episode 14: A loose collective of developers and techno-utopians


Running time: 1h 19m 57s | Download (37.5MB) | Subscribe by RSS | Huffduff

Summary: Our first episode since January. David Shanske and Chris Aldrich get caught up on some recent IndieWebCamps, an article about IndieWeb in The New Yorker, changes within WordPress, and upcoming events.

Recorded: May 19, 2019

Shownotes

6 camps later…
Austin
Online
New Haven
Berlin
Düsseldorf
Utrecht

National Duckpin Bowling Congress
Duck Tours
Streaming rigs for remote participation at IndieWeb Camps
Ad hoc sessions (🎧 00:11:28)

Can “Indie” Social Media Save Us? (The New Yorker) by Cal Newport (🎧 00:13:50)

Swarm Account deletions and posting limits
New Checkin icon within the Post Kinds Plugin: example https://david.shanske.com/kind/checkin/
Weather now has microformats mark up in WordPress
Fatwigoo problems with icons
IndieWeb Bingo

Webmention Project

Project of updating Matthias Pfefferle‘s Webmention and Semantic Linkbacks plugins (🎧 00:26:10)

Readers & Yarns

Readers & Yarns update (🎧 00:40:50)
X-Ray
Indigenous Replacement: Final Indigenous Log: The Future of the App

Post Kinds Plugin

Post Kinds and new exclude functionality (🎧 00:48:15)

  • widgets
  • titleless posts
  • On this day

David’s list of 24 IndieWebCamps he’s attended
Looking back at past IndieWebCamp sessions and wiki pages for interesting ideas and new itches
Date and time stamps on webmentions
Call for tickets in WordPress
Subscribing to h-cards with WebSub
Is Mastodon IndieWeb?
Fixing IndieAuth
Improving scoping, particularly for multi-user sites

Coming up within the community

IndieWeb Book Club

IndieWeb Book Club is coming up featuring Mike Monteiro’s book Ruined by Design(🎧 01:13:04)

IndieWeb Summit 2019

9th annual IndieWeb Summit (Portland) is coming up in June. RSVP now.

Questions?

Feel free to send us your questions or topic suggestions for upcoming episodes. (Use the comments below or your own site using Webmention). 
Perhaps a future episode on Micro.blog?

WPCampus 2019 Draft Proposal: Dramatically extending a Domain of One’s Own with IndieWeb technology

Below is a draft proposal which I’m submitting for a possible upcoming talk at WPCampus from July 25-27, 2019 in Portland, OR. If you don’t have the patience and can’t wait for the details, feel free to reach out and touch base. I’m happy to walk people through it all before then. If you’re looking for other upcoming events or need help, check out any of the upcoming Homebrew Website Clubs, IndieWebCamps, the IndieWeb Summit 2019, or even Domains2019.

Session Title

Dramatically extending a Domain of One’s Own with IndieWeb technology: How to improve your online research notebooks, commonplace books, and digital pedagogy

Session description

(This description will be edited and used on the website. Please include 1-2 paragraphs and a list of key takeaways for the audience.)

Having a Domain of One’s Own and using it as a “thought space” to own your online identity and work is just the tip of the iceberg. Can you imagine how useful it would be if you could use your Twitter account to reply to someone on Facebook (without needing a Facebook account) or vice versa? Open web technology from the IndieWeb movement that utilizes simple plugins, modules, or even built-in functionality now exists so that people can now use WordPress, Drupal, WithKnown, Grav and many other content management systems on any domain name to have rich site-to-site communications in a simple and intuitive way. Third party (and often unethical) corporate platforms are no longer needed to have rich interactions between scholars on the web.

It is now easily possible to have a teacher write a post on their own website and their students to easily reply/react to that post on their own websites (along with a useful reply context) and send that reply to the teacher’s website for possible display. Each participant can now own a copy of both sides of the conversation.

  • Teachers and students will learn how to (individually or together) collect, analyze, write, collaborate, and interact easily online while doing so in a space they own and control without giving away their data to third party platforms.
  • Researchers can now easily bookmark, highlight, or annotate portions of the web and keep this data (public/private) on their own website (aka digital commonplace book or notebook) for future reference or use.
  • We’ll show how courseware can be decentralized so that the instructor and the students each own their own pieces of the learning processes and can keep them for as long as they wish.
  • We will demonstrate how one can use their WordPress-based website with a few simple plugins to own all of the traditional social media types (bookmarks, items read, highlights, annotations, comments/replies, photos, status updates, audio, checkins, etc.) on their own site while still allowing interacting (if desired) with other websites as well as in social spaces like Twitter, Instagram, Swarm, etc.
  • We will demonstrate a new generation of free feed readers that allow composing in-line responses and reactions that post them directly to one’s own website as well as send notification to the site being read and interacted with.

You can now have the joy of a Domain of Your Own and still easily interact just as if your site were a (better-than) first class social media platform.

More Information About Your Session

(Please describe your session in greater detail for the organizers. You may be more casual in this description as it will not be posted on the website.)

In some sense, this session will be a crash course on using IndieWeb technologies and building-blocks with WordPress in the Education space. I’ll aim to remove a lot of technical jargon and keep coding examples to a bare minimum (if using any at all) so that those with the technical ceiling of downloading and installing a plugin can immediately benefit from the talk. I will also provide enough pointers and describe the broad outlines that developers will have a broad overview of the IndieWeb space to find and extend these plugins and functionality if they wish.

I’ll be covering the basics of new W3C recommendations like Webmention, Micropub, and WebSub along with forthcoming specs like Microsub in combination with IndieAuth (a version of OAuth2 for login). I’ll show how they can be applied to personal websites in research, teaching, collaboration, and other educational domains like creating Open Educational Resources. Many of these can be easily implemented in WordPress with just a handful of simple plugins that allow the web to become the social media platform we all wish it would be.

I’ll use examples from my own personal website and several others (which use Drupal, WithKnown, Grav, etc.) to show how these plugins can be used in educational settings and will walk through a case study of a course built using DoOO and IndieWeb philosophies and technologies (EDU 522: Digital Teaching and Learning at Southern Connecticut State University) on which I collaborated with Dr. Gregory McVerry.

📑 Publishers build a common tech platform together | Nieman Lab

Annotated Publishers build a common tech platform together by Jonathan GillJonathan Gill (Nieman Lab)

One way to meet the many needs that most if not all publishers share would be to collaboratively develop their digital products. Specifically, they should build for interoperability. One publisher’s CMS, another’s content APIs, a third company’s data offering — they might one day all work together to allow all ships to rise and to reclaim advertising and subscription revenue from the platforms. This might allow publishers to refocus on differentiating where it truly matters for the user: in the quality of their content.  

Some of this is already afoot within the IndieWeb community with new protocols like Webmention, Micropub, WebSub, and Microsub. Journalists should know about this page on their wiki.

👓 Boost your feeds! | Inoreader blog

Read Boost your feeds! (Inoreader blog)
You can also read this post in Chinese. Our servers are dealing with millions of feeds like the ones you read every day. We have to have this smart mechanism which balances them and fetches every feed at different interval. This interval is calculated from many factors and is aimed to provide you with the …
Read Tending towards 1.0 | With Known by Ben WerdmüllerBen Werdmüller (groups.google.com)

Before we begin -

  1. Hi! I'm going to return to spending more time on Known. As you may know, I was Director of Investments at Matter Ventures for the last two years or so, which occupied a disproportionate amount of my time. This is no longer the case. While I'm working on another open source project - Unlock - during the day, I'll be able to devote more attention to Known.
  2. Known deserves a 1.0 release, and will get one. Marcus and I have spoken quite a bit about the route forward.
  3. Commercial enhancements to Known, like the hosted service and Convoy, will get their own update. Going forward, any commercial ambitions or support for Known will be secondary to the open source project, if they exist at all.

Okay. With all of that said, I'd like to put the following out for discussion. Replies, questions, and criticisms are welcome!

This may be some of the best news I’ve heard in months! Known is one of my favorite open source CMSes that’s easy to spin up and use. It also supports so many awesome IndieWeb specs like Webmention, Micropub, WebSub, etc. right out of the box.

The runner up awesome news is that Reclaim Hosting is very likely to revamp their installatron version of it.

A reply to David Shanske regarding implementation of the DiSo Project

Replied to a post by David ShanskeDavid Shanske (David Shanske)

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 with similar functionality (but greater flexibility and independence), I recorded a 2 hour video for an 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:

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.

🎙 The IndieWeb and Academic Research and Publishing

The IndieWeb and Academic Research and Publishing


Running time: 0h 12m 59s | Download (13.9 MB) | Subscribe by RSS | Huffduff

Overview Workflow

Posting

Researcher posts research work to their own website (as bookmarks, reads, likes, favorites, annotations, etc.), they can post their data for others to review, they can post their ultimate publication to their own website.​​​​​​​​

Discovery/Subscription methods

The researcher’s post can webmention an aggregating website similar to the way they would pre-print their research on a server like arXiv.org. The aggregating website can then parse the original and display the title, author(s), publication date, revision date(s), abstract, and even the full paper itself. This aggregator can act as a subscription hub (with WebSub technology) to which other researchers can use to find, discover, and read the original research.

Peer-review

Readers of the original research can then write about, highlight, annotate, and even reply to it on their own websites to effectuate peer-review which then gets sent to the original by way of Webmention technology as well. The work of the peer-reviewers stands in the public as potential work which could be used for possible evaluation for promotion and tenure.

Feedback mechanisms

Readers of original research can post metadata relating to it on their own website including bookmarks, reads, likes, replies, annotations, etc. and send webmentions not only to the original but to the aggregation sites which could aggregate these responses which could also be given point values based on interaction/engagement levels (i.e. bookmarking something as “want to read” is 1 point where as indicating one has read something is 2 points, or that one has replied to something is 4 points  and other publications which officially cite it provide 5 points. Such a scoring system could be used to provide a better citation measure of the overall value of of a research article in a networked world. In general, Webmention could be used to provide a two way audit-able  trail for citations in general and the citation trail can be used in combination with something like the Vouch protocol to prevent gaming the system with spam.

Archiving

Government institutions (like Library of Congress), universities, academic institutions, libraries, and non-profits (like the Internet Archive) can also create and maintain an archival copy of digital and/or printed copies of research for future generations. This would be necessary to guard against the death of researchers and their sites disappearing from the internet so as to provide better longevity.

Show notes

Resources mentioned in the microcast

IndieWeb for Education
IndieWeb for Journalism
Academic samizdat
arXiv.org (an example pre-print server)
Webmention
A Domain of One’s Own
Article on A List Apart: Webmentions: Enabling Better Communication on the Internet

Synidicating to Discovery sites

Examples of similar currently operating sites:
IndieNews (sorts posts by language)
IndieWeb.xyz (sorts posts by category or tag)
 

Defining the IndieWeb

The concept of IndieWeb is something slightly different to many people and it’s ever evolving and changing, just like the internet itself.

Trying to define it is somewhat akin to trying to define America: while it has a relatively well-defined geographic border and place in time, its people, laws, philosophies, and principles, while typically very similar, can vary and change over time. What it is can be different for everyone both within it as well as outside of it. It can be different things to different people based on their place, time, and even mood. In the end maybe it’s just an idea.

A basic definition of IndieWeb

In broadest terms I would define being part of the IndieWeb as owning your own domain name and hosting some sort of website as a means of identifying yourself and attempting to communicate with others on the internet.

At its simplest, one could say they have an IndieWeb site by buying their own domain name (in my case: boffosocko.com) and connecting it to a free and flexible service like Tumblr.com or WordPress.com. Because you’ve got the ability to export your data from these services and move it to a new host or new content management system, you have a lot more freedom of choice and flexibility in what you’re doing with your content and identity and how you can interact online. By owning your domain and the ability to map your URLs, when you move, you can see and feel the benefits for yourself, but your content can still be found at the same web addresses you’ve set up instead of disappearing from the web.

If you wished, you could even purchase a new domain name and very inexpensively keep the old domain name and have it automatically forward people from your old links to all the appropriate links on your new one.

By comparison, owning your own domain name and redirecting it to your Facebook page doesn’t quite make you IndieWeb because if you moved to a different service your content might be able to go with you by export, but all of the URLs that used to point to it are now all dead and broken because they were under the control of another company that is trying to lock you into their service.

Some more nuanced definition

Going back to the analogy of America, the proverbial constitution for the IndieWeb is generally laid out on its principles page. If you like, the pre-amble to this “constitution” is declared on the IndieWeb wiki’s front page and on its why page.

Some people may choose to host the business card equivalent of a website with simply their name and contact information. Others may choose to use it as the central hub of their entire online presence and identity. In the end, what you do with your website and how you choose to use it should be up to you. What if you wanted to use your website like Twitter for short status updates or sharing links? What if you wanted to use it like Facebook to share content and photos with your friends and family? What if you want to host audio or video like Soundcloud, YouTube, or Vimeo allow?

The corporate social media revolution was a lovely and useful evolution of what the blogosphere was already doing. Thousands of companies made it incredibly easy for billions of people to be on the internet and interact with each other. But why let a corporation own and monetize your data and your ability to interact with others? More importantly, why allow them to limit what you can do? Maybe I want to post status updates of more than 280 characters? Maybe I want the ability to edit or update a post? Maybe I want more privacy? Maybe I don’t want advertising? Why should I be stuck with only the functionality that Twitter, Facebook, Instagram, Google+, LinkedIn and thousands of others allow me to have? Why should I be limited in communicating with people who are stuck on a particular service? (Would you use your phone to only call friends who use AT&T?) Why should I have hundreds of social accounts and an online identity shattered like just so many horcruxes when I could have one that I can fully control?

By decentralizing things to the level of owning a domain and having a simple website with control of my URLs, I can move to cheaper or more innovative web hosts or service providers. I can move to more innovative content manage systems that allow me to do more and communicate better or more broadly with others online. As a side effect of empowering myself, I can help create more competition and innovation in the space to do things I might not otherwise be capable of doing solely by myself.

Web standards

Almost all of the people behind the IndieWeb movement believe in using some basic web standards as a central building block. Standards help provide some sort of guidance to allow sites to be easier to build and provide a simpler way for them to communicate and interact with each other.

Of course, because you have control of your own site, you can do anything you wish with it. (In our America analogy we could consider standards to be like speech. Then how might we define free speech in the IndieWeb?) Perhaps a group of people who want some sort of new functionality will agree on a limited set of new standards or protocols? They can build and iterate and gradually create new standards that others can follow so that the infrastructure advances and new capabilities emerge. Generally the simpler and easier these standards are to implement, the more adoption they will typically garner. Often simple standards are easier to innovate on and allow people to come up with new ways of using them that weren’t originally intended.

This type of growth can be seen in the relatively new W3C recommendation for the Webmention specification which grew out of the IndieWeb movement. Services like Facebook and Twitter have a functionality called @mentions, but they only work within their own walled gardens; they definitely don’t interoperate–you can’t @mention someone on Facebook with your Twitter account. Why not?! Why not have a simple standard that will allow one website to @mention another–not only across domain names but across multiple web servers and even content management systems? This is precisely what the Webmention standard allows. I can @mention you from my domain running WordPress and you can still receive it using your own domain running Drupal (or whatever software you choose). People within the IndieWeb community realized there was a need for such functionality, and so, over the span of several years, they slowly evolved it and turned it into a web standard that anyone (including Facebook and Twitter) could use. While it may have been initially meant as a simple notifications protocol, people have combined it with another set of web standards known as Microformats to enable cross-site conversations and a variety of other wonderous functionalities.

Some people in the IndieWeb might define it as all of the previous ideas we’ve discussed as well as the ability to support conversations via Webmentions. Some might also define an IndieWeb site as one that has the ability to support Micropub, which is a standard that allows websites to be able to accept data from a growing variety of applications that will allow you to more easily post different types of content to your site from articles and photos to what you’re drinking or reading.

Still others might want their own definition of IndieWeb to support the functionality of WebSub, MicroSub, IndieAuth, or even all of the above. Each small, free-standing piece expands the capabilities of what your personal website can do and how you can interact online. But since it’s your website and under your control, you have the power to pick and choose what and how you would like it to be able to do.

So what is the IndieWeb really?

Perhaps after exploring the concept a bit, most may not necessarily be able to define it concretely. Instead they might say–to quote United States Supreme Court Justice Potter Stewart“But I know it when I see it […]”.

The IndieWeb can be many different things. It is:

  • a website;
  • an independent network of websites;
  • an idea;
  • a concept;
  • a set of broad-based web standards;
  • a set of principles;
  • a philosophy;
  • a group of people;
  • a support network;
  • an organization;
  • an inclusive community;
  • a movement;
  • a Utopian dream of what the decentralized, open Internet could be.

In some sense it is all of these things and many more.

In the end though, the real question is:

What do you want the IndieWeb to be?

Come help us all define it.

IndieWeb.org