Today I was reminded while thinking about Disqus that I had an Intense Debate account from April 23, 2009. Apparently it’s still functioning all these years later–possibly as a result of their purchase by Automattic in 2008. Not that there was much there, but I took a few minutes and exported out all my data and now own it here on my site.
One of the interesting parts was that it featured a comment about Twitter pulling the rug out from underneath developers–an event that foreshadowed even more of the same in the coming years as well as a conversation about the gamification of follower accounts, something which has gotten us into a sad state of affairs today nearly a decade later. Apparently while they tried to cap follower accounts, their early efforts just didn’t go far enough to help the civility of the platform.
For a quite a while I’ve been thinking about writing a book about the IndieWeb to provide a broader overview of what it is philosophically, how it works, how its community functions, and most specifically how the average person can more easily become a part of it.
Back in January Timo Reitnauer wrote Let’s Make 2017 The Year of the Indie Web. I agree wholehearted with the sentiment of his title and have been personally wanting to do something specific to make it a reality. With the changes I’ve seen in the internet over the past 22 years, and changes specifically in the last year, we certainly need it now more than ever.
As a result, I’m making my 2018 IndieWeb resolution early. For the month of November, as part of NaNoWriMo, I’m going to endeavor to lovingly craft together a string of about 2,000 words a day on the topic of the IndieWeb to create a book geared toward helping non-developers (ie. Generation 2 and Generation 3 people) more easily own their online identities and content.
Over the past year, surely I’ve read, written about, or interacted with the IndieWeb community concretely in one way or another on at least 70 days. This sprint of 30 days should round out a 100 days project. To be honest, I haven’t necessarily posted about each of these interactions on my own site nor are they necessarily visible changes to my site, so it may not follow the exact requirements of the 100 Days of IndieWeb, but it follows the spirit of the creator idea with the hopes that the publicly visible result is ever more people adopting the principles of the movement for themselves.
I’ll focus the book primarily on how the average person can utilize the wealth of off-the-shelf tools of the WordPress content management system and its community–naturally with mentions of other easy-to-use platforms like Known and Micro.blog sprinkled throughout–to own their own domain, own their content, and better and more freely communicate with others online.
If you haven’t heard about the movement before, I’ll direct you to my article An Introduction to the IndieWeb, portions of which will surely inform the introduction of the book.
If you’ve recently joined the IndieWeb, I’d certainly love to hear your thoughts and stories about how you came to it, why you joined, and what the most troublesome parts have been so I can help direct people through them more easily–at least until there are a plurality of one-click solutions to let everyone IndieWeb-ify themselves online.
As a publisher who realizes the value of starting a PR campaign to support the resultant book, I’m also curious to hear thoughts about potentially launching a crowdfunding campaign to support the modest costs of the book, with profits (if any) going toward supporting the IndieWeb community.
I’m happy to entertain any other thoughts or considerations people have, so feel free to reply in the comments below, or better yet, reply on your own site and send me a webmention.
There's a better way to own and control your online identity
Whether you’re starting a blog, building your personal brand, posting a resume, promoting a hobby, writing a personal journal, creating an online commonplace book, sharing photos or content with friends, family, or colleagues, writing reviews, sharing recipes, podcasting, or any one of the thousand other things people do online it all starts with having a presence and an identity online.
The seemingly difficult task these days is deciding where that should be. There’s Twitter for sharing short updates and bookmarks to articles; Instagram, Snapchat, Flickr, and YouTube for photos and videos; Facebook for communicating with family and friends; LinkedIn for work and career related posts; Swarm for sharing your location; and literally thousands of others for nearly every micro-slice of content one could think of.
Can you possibly be on them all? Should you? Would you want to be? Could you keep up with it? Which one really and truly represents the real you? Could any of them?
And what about your friends, family, and potential audience for all of these things? Some will be on Twitter while others only use Facebook. Grandma is worried about privacy and is only on Instagram to see photos of the grandchildren. Mom is on Facebook because she thinks that’s what the internet is, and wants to like everything her children post. Teenagers don’t want to be on any platforms their parents have heard of. It’s obvious that everyone has their own preferences and favorites.
In short, the web and using it for easy communication has become fraught with fragmentation and walls that often make communicating online far more difficult than it should be. Wouldn’t it be better if you had a single website that represented you online and through which you could easily communicate with everyone?
By analogy consider the telephone system which, just like the internet, consists of wires and hardware to access the network. Every user on the network has their own phone and phone number. What would it be like if AT&T users could only speak to other AT&T users and needed another separate phone, account, and phone number to speak to friends and family on Verizon and yet another to talk to friends on Sprint? To a great extent, this is what the internet has evolved to become with monopolistic, for-profit, corporate services like Facebook/Instagram, Twitter, LinkedIn, and all the rest.
Is there a better and more robust solution than these multitudes of social media sites which all come with their own onerous terms of service, limitations on your creativity, reach, ownership, and control of your online identity?
A growing number of people on the web are sure there is and they’re working together in an open yet coordinated way to improve the democratized nature of the decentralized internet. This movement is known as the IndieWeb.
Purpose of IndieWeb
The purpose of the IndieWeb movement is to help put you in control of your web presence, allow you a more true sense of ownership of your content, and to allow you to be better connected to your friends, family, colleagues, and communities. By first owning your own domain name and having your own personal website, the IndieWeb aims to help facilitate the following:
You are in Control
You can post anything you want, in any format you want, with no one monitoring you. In addition, you share simple readable links such as http://www.example.com/ideas. These links are permanent and will always work.
Control and Freedom
You should be able to exercise your freedom of speech and publish anything you want whenever you want. You should be able to set your own rules and own limits. You should be able to post content as long or short as you like with no pre-imposed limits or types whether it be text, photos, audio, or video. You should be able to have control over comments and protection against potential harassment, bullying, and online trolls.
Identity & Identity loss
Almost every social media site has a multi-page statement of their terms of service written in complicated legalese. More often that not, these terms are to protect them and not you. As a result people have found their accounts frozen, they’ve been shut out with no notice or warning, their identities have been reassigned, or their content simply disappears with liitle or even no notice. Often there is either no method of recourse, or it is difficult to communicate with these corporations and may take weeks or worse to recover one’s account and data, if at all.
Without care, one can become branded with the identity of the social media network of which they’re a part. If trolls overrun your social service then suddenly by association, you’ve become one too.
User Interface/User EXperience
You should have the ability to control how your site looks and works. Do you want a piece of functionality that one of your social network sites doesn’t have? Add it the way you want it. Create better navigation, better interactivity, better design to reflect your own identity instead of a corporation’s cookie-cutter idea of your identity. Since your data is yours you can add new and interesting pieces of functionality using that data instead of waiting on a social site to think about it and implement it for you. Chances are that unless millions will find it valuable or a company doesn’t think it will scale, most won’t build it, so don’t hold your breath.
Your content is yours
When you post something on the web, it should belong to you, not a corporation. Too many companies have gone out of business and lost all of their users’ data. By joining the IndieWeb, your content stays yours and in your control.
Greater reliability and protection against content loss
Social media is only about 11 years old, and one thing is certainly true: sites will go out of business, they will get acquired, they can and willdisappear. When this happens, your data can disappear overnight without the ability to back it up or export it. A new corporation can take over and change the terms of service and do things with your data that you never intended. Content can accidentally or even willfully disappear without notice to you. In addition to the data, you can also lose contact with family, friends, and community members that also disappear without the service that connected you to them.
You can have greater control of site downtimes, server outages, maintenance, scalability issues, and database failures of silos attempting to solve massive scaling/engineering problems.
A better sense of ownership
Many in the IndieWeb community have found that they post more interesting and thoughtful pieces of content when they’re doing it on their own site rather than the “throw away” content they used to post to sites like Twitter. They feel a greater sense of responsibility and ownership in what they’re posting about and this can have a profound effect on the future of the internet and its level of civility.
When you own your own website, other web sites see that it’s you personally sending traffic to their sites instead of a generic social site. You have the ability to edit content at any time or delete it if you like.
You also have:
greater choice of public vs. private posts and control of who your audience is;
the ability to fix URL links when they break or disappear;
no outside advertising on your site without your explicit permission;
no one monetizing you;
no censorship of your content;
no terms of service which can often co-op your work without notice for advertising or other use;
ownership and control of affiliate links to monetize your work if you choose.
You are better connected
Your articles and status messages can go to all services, not just one, allowing you to engage with everyone regardless of their choice of platform. Even replies and likes on other services can come back to your site so they’re all in one place.
Since your content isn’t hidden behind the robots.txt of a silo service, you have much better search engine rankings and are more likely to be found, read, or have people interact with your content. If you choose, you can still syndicate your content to one or more social silos while still owning your content in the case that something happens to those silos. This allows you to continue to reach your friends, family, colleagues, and community who may have different ideas about where they prefer to interact online. Comments to and interactions with your content can come back to your original post to create a comprehensive conversation rather than have your conversation disjointed and spread over dozens of sites throughout the web.
How to be a part of the IndieWeb
Now that you’ve got a bit of an idea about what the IndieWeb movement is attempting to help people accomplish, how can you become a part of it and enjoy the benefits for yourself?
Own and use your own domain name
Fifteen or more years ago having your own domain wasn’t as easy or as inexpensive as it is now. There are hundreds and hundreds of domain registrars around the world that can register almost any domain name you can come up with for as little as 99 cents a year with the average closer to the $10-20 range depending on the name and the top level domain (.com, .org, .net, and .edu are examples of top level domains.)
For an extra $0-10 a month you can quickly purchase domain hosting so that when someone visits your fancy URL, it actually connects to a page on the internet. Whether that page is a single page of simple HTML with a line of text and a photo; a plug and play site like Wix or SquareSpace; a full blown professional open source content management system like WordPress or Drupal; a web site you build by hand using your own code; or it points to your Facebook or Twitter account page, you’ve just made a huge step toward better cementing your identity on the internet.
Once you own your own domain name, everything you post to the web will have a permalink URL which you can control. If you wish to change platforms or service providers you can relatively easily move all of your content and the permalinks along with it–much the same way you can move your cell phone number from one provider to another. People who visit your URLs will always be able to find you and your content.
If nothing else, owning your own domain name will give you something useful to put into the ubiquitous field labeled “your website” that exists on literally every social media website out there. (Even they are subtly telling you that you should have your own domain name.)
Added bonus: even most inexpensive domain registrars and hosting services will give you free email for your domain so you can create a custom branded personal email address like firstname.lastname@example.org. Even if you rely on G-mail or some other third party service for your email, it’s pretty easy to connect your own personal email address to your pre-existing account. It’ll make you look a lot more professional and will be far easier for your friends, family, and business colleagues to remember.
So you own your domain now?! Congratulations, you are officially a full-fledged member of the IndieWeb!
Own your data
Wait, it can’t be that simple can it? It is! But now that you’ve got your own website, it’s time to start using it to own your online identity and own your own content.
Next you may want to choose a content management system (CMS) in which to store and present your data. The IndieWeb has lists of projects which range from common services as simple as Tumblr and WordPress.com (both managed services with free hosting) to help in building your own site from the ground up in your programming language of choice. Which project you choose depends on your needs, desires for the future, and your abilities. There is something available for people of nearly every level of ability. Most domain registrars and internet host providers provide one or more means to quickly get up and running–just ask their customer service departments or see what they’ve got available online.
Most of these CMS solutions will give people a far bigger range of flexibility in terms of what they can write, record, and broadcast online. You don’t need to be limited to 140 characters if you choose not to be. Want to post more multi-media-based content with text, video, audio, and photos all at once? The online world can be your oyster and your social media platform no longer limits what is possible.
Ideally, what a lot of the IndieWeb developer community is rapidly building and iterating upon is an open and broadly distributeable way to make it easier for the everyday person to more easily own and operate all the functionality offered by the hundreds of social media websites without a lot of heavy and difficult-to-maintain overhead. A decade ago allowing Facebook to do everything for you may have been a simple “way out”, but now there are far more robust, diverse, and flexible solutions that aren’t as onerous. There are also newer open and easily supportable web protocols that make publishing and sharing your content far easier than before.
The first big piece most people enjoy implementing is writing their own content on their own site and syndicating it out to other services on the internet if they choose. Continuing to participate in your old siloed networks can help you stay connected to your pre-existing social networks, so you’re not leaving all your friends and family behind. Next, having all your replies/comments, likes, and other interactions come back from social silos to your own site as comments along with notifications is incredibly valuable. (These two processes are commonly known as Post On your Own Site, Syndicate Elsewhere (POSSE) and backfeed, and they can typically be done most easily with a free service like Brid.gy.)
Being able to write replies to articles or status updates on your own website and either @mentioning others as a means of notifying them is also very useful. The IndieWeb calls this universal implementation of @mentions that work across website boundaries Webmention and it’s built on an open and straightforward standard so that it can work with any website on the internet. (Remember the telephone analogy above? Now, thanks to Webmentions, everyone can be communicating on the same network.) As an example, imagine for a moment if you could @mention someone on Facebook from Twitter or vice-versa?! What if you could post a reply to a tweet on Twitter with your Facebook account?Using the Webmention spec, independent websites can easily do this now, though it may be quite a while before for-profit corporations support this simple protocol that is now a W3C recommendation.
With some of the basic building blocks out of the way, people tend to spread out a bit in the types of functionalities they’re looking for. It may range from posting status updates, pictures, or video to hosting your own podcast or or having different user interfaces to post to your own site–Micropub is great for this–to being able to put events on your site and allowing people to RSVP to them easily. Wouldn’t it be nice if you could post an event on your own website and people could use Facebook to RSVP to it? My site allows this possibility. Yours could too.
Everyone’s desires and needs will be different. Work on what you find most interesting and useful first (the IndieWeb calls these itches). Make a list of what you use most often on your old social media silos or wish they had and work on that first. Check out the IndieWeb wiki to see how others have implemented it–there’s no need to reinvent the wheel in darkness. Hop into the IndieWeb chat (there are multiple ways of doing this and interacting) and ask questions. Document what you’ve done in the wiki to make it easier for those who come after you.
Personally, I’ve always just thought about what functions do I use most on social sites and then ask myself how I might be able to do that on my own site. There’s little out there that hasn’t been explored by the bigger community, so searching the wiki for those types of functionality and seeing how others managed it usually makes it far easier. Chatting with folks in the community while I’m working always helps to sharpen my thinking and make me aware of ideas and methods I may have never considered much less come up with on my own.
If you never RSVP for things online or host events, then obviously don’t start there. Do you post photos regularly? Maybe you “like” everything you see online. In my case, I was a heavy user of Goodreads, so I spent parts of the last year working on more easily bookmarking things I’d like to read, posting reading status updates, and keeping notes on what I read, as well as highlights, marginalia, and book reviews after I’d finished reading.
The IndieWeb effort is different in several ways from previous efforts and communities. In particular it values principles over project-centrism. Other efforts have assumed a monoculture of one project as the ultimate solution for everyone. IndieWeb prefers developing a plurality of projects–why not have the same diversity on the web as we do in real life?
The community prefers chat in combination with a wiki to communicate and document its process. Some may prefer email distribution lists, but why? Who likes to read and respond to long email threads where information is typically locked away from the group, ignored, and simply unread? Instead, we utilize a chat (which has multiple methods of access–plurality, remember?) to host searchable conversations after which the best portions are documented on the wiki to be easily searchable and discoverable to all.
In the early days of social media, many talked, emailed and chatted about what they’d like to see. Sadly not much was done about expanding on these ideas, particularly by companies that all had their own profit-driven motives. As a result, the IndieWeb movement values showing before telling. They prioritize development by encouraging people to scratch their own itches, creating what they want to have and use on their own sites, and then iterating on those pieces to improve and refine them. If you won’t use a feature on your own site, why bother to have it?
IndieWeb puts design first and foremost. Protocols & formats come second. They’d prefer to focus on good user experience and user interaction. Users selfdogfood prototypes on their own sites to create minimum necessary formats & protocols.
Perhaps most importantly, the IndieWeb is people-focused instead of project-focused. The community is rich and diverse and has regular in-person meetups as well as camps across the world where everyone is welcome. The IndieWeb community is inclusive and has a code-of-conduct.
Join the IndieWeb Community
Where do I go from here? You said community in there. Where can I find it? How can I interact, get help, or even contribute back?
Regardless of your level of expertise, there are a huge number of resources, events, and even people available to you in a variety of formats. Whether you choose to meet with friends in person at IndieWebCamps or at regularly scheduled Homebrew Website Club meetups or interact online at a nearly continuous worldwide chat (using either web chat, Slack, Matrix, or IRC) there are many means of getting help and interacting to suit your schedule and needs to help build the personal website you’ve always wanted.
Building the indie web is a continuous process. While attending an IndieWebCamp can be an incredibly inspiring and encouraging event, we need to carry on doing so for more than just a few days a year when we can meet up in real life. We can not only support one another; we can share the best way to do things online. As we discover new ways of doing things, we can document them and share them easily with each other and the growing community.
If you’ve made it this far, I invite you to join us, and get started building the internet you’ve always wanted by building your home on the web first.
As of December 2017, the AltPlatform.org site which originally published this article has shut down. I’ve smartly kept a private archived copy of the original of this post here on my personal site and manually syndicated a copy of it to AltPlatform for just such a possibility. (Hooray for PASTA (Publish Anywhere, Save to (Private) Archive)!) As a result of the shutdown, I’m making the original public here.
The University of Mary Washington’s initiative, “Domain of One’s Own,” is phrased thusly as a nod to Virginia Woolf’s essay “A Room of One’s Own,” in which she famously quipped that “A woman must have money and a room of her own if she is to write fiction.” We can critique – and certainly we should – the class implications and expectations in Woolf’s commandment here; and we must consider both the financial burden and the transaction mechanism of a push for domains in education – as Maha notes, for example, many students in Egypt don’t have a credit card with which to make online purchases.
“Give her a room of her own and five hundred a year, let her speak her mind and leave out half that she now puts in, and she will write a better book one of these days,” Woolf wrote in 1929. (That 500 quid is the equivalent to about $37,000 when adjusted for inflation.) But Woolf is not simply talking about having a piece of paper – a title, for example – that decrees she owns the room. It’s about having the financial freedom and a personal space to write.
To own is to possess. To own is to have authority and control. To own is to acknowledge. It implies a responsibility. Ownership is a legal designation; but it’s something more than that too. It’s something more and then, without legal protection, the word also means something less.
There is some important internet philosophy going on in this article. Though written for an education-based audience, I think it’s got an important message for everyone about owning their own space online and being able to write and freely express themselves.
Rel=”me” is a microformat tag put on hyperlinks that indicates that the paged linked to is another representation of the person who controls the site/page you’re currently looking at. Thus on my home page the Facebook bug has a link to my facebook account which is another representation of me on the web, thus it has a rel=”me” tag on it.
His data is a bit old as I now maintain a page entitled Social Media Accounts and Links with some (but far from all) of my disparate and diverse social media accounts. That page currently has 190 rel=”me”s on it! While there was one other example that had rel-mes pointing to every other internal page on the site (at 221, if I recall), I’m proud to say, without gaming the system in such a quirky way, that each and every one of the rel=”me” URLs is indeed a full legitimate use of the tag.
I’m proud to be at the far end of the Zipf tail for this. And even more proud to be tagged as such during the week in which Microformats celebrates its 12th birthday. But for those doing research or who need edge cases of rel-me use, I’m also happy to serve as a unique test case. (If I’m not mistaken, I think my Google+ page broke one of Ryan’s web crawlers/tools in the past for a similar use-case a year or two ago).
The Moral of the Story
The take away from this seemingly crazy and obviously laughable example is simply just how fragmented one’s online identity can become by using social silos. Even more interesting for some is the number of sites on that page which either no longer have links or which are crossed out indicating that they no longer resolve. This means those sites and thousands more are now gone from the internet and along with them all of the data that they contained not only for me but thousands or even millions of other users.
This is one of the primary reasons that I’m a member of the Indieweb, have my own domain, and try to own all of my own data.
While it seemed embarrassing for a moment (yes, I could hear the laughter even in the live stream folks!), I’m glad Ryan drew attention to my rel-me edge case in part because it highlights some of the best reasons for being in the Indieweb.
(And by the way Ryan, thanks for a great presentation! I hope everyone watches the full video and checks out the new site/tool!)
dokieli is a clientside editor for decentralised article publishing, annotations and social interactions.
dokieli envisions research results, analysis and data all being produced interactively on the Web and seamlessly linked to and from articles. Through annotations and notifications, the academic process of peer-review can be open, transparent and decentralised for researchers.
Personal sites, our blogs, these were once our playgrounds. My own site was the first place I added rollover images, CSS for fonts, tried out a “table free” design. I wrote about the web, surrounded by my own experiments with the web. We all did, and it was only in reading those words from 1999 that I realised there was more to owning your own content than simply not publishing your words elsewhere.
Rachel, To a great extent it sounds like you’ve independently discovered and rewritten a lot of the indieweb philosophy which can be found at https://indieweb.org. It’s a diverse group of web developers who have taken back the web and their identities from where things left off around 2007 when the social media silos drastically changed the way we all use the internet.
I suspect that given your interests, background, and what you’ve written here, you’ll not only feel right at home in this group, but you’ll get a lot of real value out of it both personally and professionally. In particular, I think you’ll enjoy concepts like webmention and micropub, services like Brid.gy, and many others. When you have time I invite you to come join us both on the wiki as well as in chat/IRC/Slack as we all continue building and improving our own personal websites in much the same way we did as “kids.”
Next month, two seminal image-sharing communities, FFFFOUND! and MLKSHK, will close their doors within a week of each other. There's a profound difference in how they're doing it as noted by someone who's previously sold off a community.
This is a great little piece comparing and contrasting how to relatively similar online communities and social silos are shutting down their services. One is going a much better route than the other and providing export tools and archive ability to preserve the years of work and effort.
On the anniversary of the death of FriendFeed, I update Louis Gray's flawed social media diagram.
I was reminded this morning that two years ago yesterday FriendFeed, one of my favorite social media sites, was finally shut down after years of flagging support (outright neglect?) after it was purchased by Facebook.
This reminded me of something which I can only call one of the most hurtful diagrams I saw in the early days Web 2.0 and the so-called social web. It was from an article from May 16, 2009, entitled Know and Master Your Social Media Flow by Louis Gray, a well-known blogger who later joined Google almost two years later to promote Google+.
Here’s a rough facsimile of the diagram as it appeared on his blog (and on several syndicated copies around the web):
His post and this particular diagram were what many were experimenting with at the time, and certainly inspired others to do the same. I know it influenced me a bit, though I always felt it wasn’t quite doing the right thing.
Sadly these diagrams all managed to completely miss the mark. Perhaps it was because everyone was so focused on the shiny new idea of “social” or that toys like Twitter, Facebook, FriendFeed, and thousands of others which have now died and gone away were so engaging.
The sad part in searching for new ways to interact was that the most important piece of the puzzle is right there in his original diagram. No, it’s not the sorely missed FriendFeed service represented by the logo in the middle, which has the largest number of arrows pointing into or out of it. It’s not Facebook or Twitter, the companies which now have multi-billion dollar valuations. It’s not even the bright orange icon representing RSS, which many say has been killed–in part because Facebook and Twitter don’t support it anymore. The answer: It’s the two letters LG which represent Louis Gray’s own personal website/blog.
Sadly bloggers, and thousands upon thousands of developers, lost their focus in the years between 2007 and 2009 and the world is much worse off as a result. Instead of focusing on some of the great groundwork that already existed at the time in the blogging space, developers built separate stand-alone massive walled gardens, which while seemingly democratizing the world, also locked their users into silos of content and turned those users into the actual product to monetize them. (Perhaps this is the real version of Soylent Green?) Most people on the internet are now sharecropping for one or more multi-billion dollar companies without thinking about it. Our constant social media addiction now has us catering to the least common denominator, unwittingly promoting “fake news”, making us slower and less thoughtful, and it’s also managing to slowly murder thoughtful and well-researched journalism. Like sugar, fat, and salt, we’re genetically programmed to be addicted, and just like the effect they have on us, we’re slowly dying as a result.
The new diagram for 2017
Fortunately, unlike for salt, fat, and sugar, we don’t need to rely on simple restraint, the diet of the week, or snakeoil to fix the problem. We can do what Louis Gray should have done long ago: put ourselves, our identities, and our web presences at the center of the diagram and, if necessary, draw any and ALL of the arrows pointing out of our own sites. Facebook, Twitter, Instagram, LinkedIn, FourSquare/Swarm, etc. can all still be there on our diagrams, but the arrows pointing to them should all originate from our own site. Any arrows starting with those same social networks should ALL point (only) back to our sites.
This is how I always wanted my online diagram to look:
How can I do this?
In the past few years, slowly, but surely, I’ve managed to use my own website to create my diagram just like this. Now you can too.
A handful of bright engineers have created some open standards that more easily allow for any website to talk to or reply to any other website. Back in January a new W3C recommendation was made for a specification called Webmention. By supporting outgoing webmentions, one’s website can put a link to another site’s page or post in it and that URL serves the same function as an @mention on services like Twitter, Facebook, Medium, Google+, Instagram, etc. The difference here is that these mentions aren’t stuck inside a walled garden anymore, they can reach outside and notify anyone anywhere on the web that they’ve been mentioned. Further, it’s easy for these mentions to be received by a site and be posted as comments on that mentioned page. Because the spec is open and not controlled by a third party corporation, anyone anywhere can use it.
What does this mean? It means I can post to my own site and if you want to write a comment, bookmark it, like it, or almost anything else, you post that to your own website and mine has the option of receiving it and displaying it. Why write your well thought out reply on my blog in hopes that it always lives there when you can own your own copy that, though I can delete from my site, doesn’t make it go away from yours. This gives me control and agency over my own platform and it gives you ownership and agency over yours.
More and more platforms are beginning to support this open protocol, so chances are it may already be available to you. If you’re using an open source platform like WordPress.org, you can download a plugin and click “activate”. If you want to take few additional steps to customize it there’s some additional documentation and help. Other CMSes like Known have it built in right out of the box. Check here to see if your CMS or platform is supported. Don’t see your platform listed? Reach out to the developers or company and ask them to support it.
If you’re a developer and have the ability, you can easily build it right into your own CMS or platform of choice (with many pre-existing examples to model off if you need them) and there are lots of tools and test suites built which will let you test your set up.
Let’s go back to Louis Gray’s blog and check on something. (Note that my intention isn’t to pick on or shame Mr. Gray at all as he’s done some excellent work over the years and I admire it a lot, he just serves as a good public example, particularly as he was recruited into Google to promote and launch G+.)
If you look at his number of posts over time (in the right sidebar of his homepage), you’ll see he was averaging about 500+ posts a year until about the time of his diagram. That number then drops off precipitously to 7 and 5 in 2015 and 2016 respectively!! While life has its vagaries and he’s changed jobs and got kids, I seriously doubt the massive fall off in posts to his blog was because he quit interacting online. I’ll bet he just moved all of that content and all of his value into other services which he doesn’t really own and doesn’t have direct control over.
One might think that after the demise of FriendFeed (the cog at the center of his online presence) not to mention all the other services that have also disappeared, he would have learned his lesson. Even browsing back into his Twitter archive becomes a useless exercise because the vast majority of the links on his tweets are dead and no longer resolve because the services that made them died ignominious deaths. If he had done it all on his own website, I almost guarantee they’d still resolve today and all of that time he spent making them would be making the world a richer and brighter place today. I spent more than twenty minutes or so doing a variety of complicated searches to even dig up the original post (whose original URL had moved in the erstwhile) much less the original diagram which isn’t even linked to the new URL’s post.
Etymologically, the word samizdat derives from sam (Russian: сам, “self, by oneself”) and izdat (Russian: издат, an abbreviation of издательство, izdatel’stvo, “publishing house”), and thus translates as “self-published”.
With exception of the jail portion, these ideas underlie much of the Indieweb movement.
In a project which I started just before IndieWebCamp LA in November, I’ve moved a big step closer to perfecting my “Read” posts!
Thanks in large part to WordPress, PressForward, friends and help on the IndieWeb site too numerous to count, and a little bit of elbow grease, I can now receive and read RSS feeds in my own website UI (farewell Feedly), bookmark posts I want to read later (so long Pocket, Instagram, Delicious and Pinboard), mark them as read when done, archive them on my site (and hopefully on the Internet Archive as well) for future reference, highlight and annotate them (I still love you hypothes.is, but…), and even syndicate (POSSE) them automatically (with emoji) to silos like Facebook, Twitter (with Twitter Cards), Tumblr, Flipboard, LinkedIn, Pinterest, StumbleUpon, Reddit, and Delicious among others.
Syndicated copies in the silos when clicked will ping my site for a second and then automatically redirect to the canonical URL for the original content to give the credit to the originating author/site. And best of all, I can still receive comments, likes, and other responses from the siloed copies via webmention to stay in the loop on the conversations they generate without leaving my site.
Here’s an example of a syndicated post to Twitter: