Here’s a handy how-to for building a homemade homebrew setup with Linux, Python, and the Raspberry Pi.
I really want to put together something like this.
In the end, I think technology adoption by stealth is the only way to make an idea dominant. With the open web (I use that term intentionally since “Indie Web” is much more of a community I don’t know well), people weren’t excited to adopt http. They were excited about websites. Older open web technologies, like trackbacks and pingbacks, weren’t successful because of the technology, per se, but instead of the ease in which regular end users could use it to their end.
In adoption in WordPress Core or Jetpack, the technology would need to not seem like technology, but only a feature. “Automatically notify sites you’re linking to about your post” is the feature, which exists in WordPress already through now-antiquated tech, so for webmentions to have a life in Core, they would need to augment that feature. “WordPress now features rich notifications”, for example.
I do fear that the dependence on microformats will be a detriment to widescale adoption, at least via the WordPress vector. For better or worse, markup is theme territory. Genesis already adopted Schema.org, mainly due to the SEO benefits given schema.org is Google-backed. _s has been hesitant to pick sides. If either method is going to get traction, building it into a default theme and, possibly, a
theme_support declaration would be the way it happens. If that happened, then other theme authors may opt to build support and the snowball would begin to roll.
I don’t know the webmention spec at all so ignore me if this is ignorant. Instead of webmentions relying so much on microformats and scraping, what if it could use either microformats or a reference to an API. WordPress now has a REST API, so what if the webmention allowed an alternative data location for structured data? When available, if the receiving site could verify the mention and then pull from the API, then it would likely be more reliable and not markup dependent, thus more likely that Jetpack or WordPress core, etc could add support for it.
In short and to the point, for something like this to gain traction, it would need to just work in a way that reduces fragility and developer error.
My first experience with an online world was dial-up into AOL and exploring their internal experiences. Only rarely did I click the button to go into the unknown and wild internet. AOL controlled everything within their experiences.
For awhile, we had a golden age of blogging. People would comment on each other’s blogs. If you wanted to write a novel in response to someone, you did–on your site. When you did, a trackback or, later on, a pingback would automatically alert the original post and a little ad-hoc social network between two sites was created.
Feed readers provided a place for people to aggregate their blogging experience. From there, easy publishing and content aggregation fell in love and gave birth to social networks. This path wasn’t intended or necessarily in mind when Facebook or Twitter started, but nevertheless.
In all of this, having your home belong to you is important. A business whose online presence is their Facebook page is placing all of their eggs in one basket hoping that it isn’t in Facebook’s business interests to change the system to your detriment. Even on platforms like Wix, which do give you your own website, do not give you any means to take that content with you whenever their platform or your needs change.
Having a home that you control is important, but now you have to maintain your main online presence and your Facebook page and your Instagram account and your Twitter feed and maybe blog on Medium too and so on and so on. The open web is being lost.
I want to see the WordPress ecosystem do more toward building up the new open web. Whether it is directly in Core or experimented with via Jetpack, there is a large user base who would benefit by modern and advanced open web technologies. There is a solid group of folks who believe in an open and independent web who have helped create standards and systems to interoperate, but it’s hard to gain adoption without the baking of something with the heft of Facebook or Twitter.
micro.blog is what turned me on to the modern standards. Micro.blog aims to be, more or less, an open Twitter. You can pay them to run your microblog or it’ll pull in your WordPress site (a special site just for your microblog or, in my case, just a category). Reading more about the tech behind it, such as webmentions–which I had heard of before but never took the time to read up on it–gave me a new excitement for the future of the web that I haven’t had in awhile.
What can we do to help continue this excitement? WordPress has considerable pull. When it supports something, it gets noticed. If we can figure out how many make webmentions work well, would Facebook or Twitter begin to support them in some way?
To this end, I would like to dedicate some of my free time toward exploring this more. Specifically:
The hard part is keeping the end user in mind. I’ve recently setup a few pieces of indieweb concepts on my site, but it isn’t something that I would expect my wife or a random end user to do. It isn’t obvious why one would do this, it is a bit clunky, the workflows aren’t straight-forward yet. I think they can get there.
The dream isn’t to return to the past before social media, but help make social media part of the web in an organic way. For this post, you can like it or comment it on via this site, WordPress.com, Twitter, or Facebook, but all of the comments will appear here using Webmentions. The closed gardens will still exist, but it’ll make it easier for people to reach out between them.
I know I’m very late to the party after a tiny bit of research I’ve done so far. I’ve seen the same names pop up all over the place. These folks have worked very hard to get where it is now and I’m sure they know of dozens of roadblocks I couldn’t imagine today. But, I hope that, even if I’m late, there’s still room at the table.
How about you? What would you like to see move forward in the evolving open web?
I was underwhelmed by the updates. Not the latest chips. A TouchBar that feels more gimmick than innovation. Simple stated, I’m disillusioned with the status quo thought that Apple makes the best devices for geeky work.
After investigating the Surface Book, which is an amazing feeling device from demoing in store, I ended up going with Dell’s new 13-inch XPS 13 2-in-1 device. The keyboard folds completely back to go into tablet mode, Intel i7 7th generation chips, good price, with Thunderbolt 3 support on the USB C ports.
I’m reserving final judgement, but so far, it isn’t as elegant as what Apple once was (the new MacBook Pro’s doggle-city puts this in the past tense). I purchased a power companion which acts as a power adapter, battery back-up, and USB charging device in one. As advertised, it is great for plugging into the laptop while it is in the bag from one place to the next, charging on the go.
I haven’t had a chance to put it through a real-world scenerio, but it was painful once I realized how it all fit together.
First, in comes in five parts. 1, 2, 3 are the power companion components, which requires a power adapter as it does not include any way to plug into the wall.
To make this device functional on the road, I need to have all five items in my bag.
I’m trying to be optimistic and remind myself that my first days on OS X felt strange as I figured out the operating system and the various must-have apps and utilities.
I started a new chat. 35 minutes later they tell me it isn’t available and there are newer models. For an accessory too new to be on the site for a computer announced this week.
I was trying to give them money.