The home for design & development of a core WordPress REST API authentication solution - WP-API/authentication
There’s already a version of IndieAuth that does a big chunk of this.
The home for design & development of a core WordPress REST API authentication solution - WP-API/authentication
There’s already a version of IndieAuth that does a big chunk of this.
Unicyclic.com is a social feed reader, which means you can subscribe to feeds and then reply to, like, or share what you're reading from the reader.
If you have your own website, you can use it to log in right here using IndieAuth. If you also support Micropub, all your interactions here will be posted back to your own site.
If you don't have your own website you can also create an account on this site and then log in here. Local accounts will also receive notifications sent from other sites via webmention, including from Twitter via brid.gy.
Unicyclic.com was created by Malcolm Blaney and is powered by a content management system called dobrado. You can also download the software from there and run it on your own server. If you need any help getting started, please use this contact form. If you're interested in following updates to the software please add my blog to your reader. Thanks for visiting!
Those big time motivational speakers who talk about starting to learn with a problem you want to solve have never really accounted for serendipitous learning. Is everything as simple as problem
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
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
Post Kinds and new exclude functionality (🎧 00:48:15)
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?
Improving scoping, particularly for multi-user sites
9th annual IndieWeb Summit (Portland) is coming up in June. RSVP now.
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?
Reminder: What about the idea of creating a stand-alone version of a page builder plugin like Beaver Builder with a layer of IndieAuth and Micropub on top that would make it a potential Micropub client? I’ve pitched the idea that Medium.com could quickly be turned into a micropub client, why not these? Create a page and it’s general layout in a page building client and then send the payload to your website without the need to have the code running directly on your website!
I briefly spitballed the general idea of this with Robby McCullough today.
There’s also the potential that an IndieAuth/Micropub set up could be created to give advertising platforms the ability to access smaller portions of a website to essentially inject advertising into a site’s sidebars, footers, or content directly, maybe on a pay-per-pixel basis. I’d really have to implicitly trust an advertisement server to allow this however.
I still have a few minor tweaks to get things working properly with Post Kinds to display everything correctly, but I feel like I’m almost there. Next we’ll have to delve back to May sometime when my system between IndieAuth and OwnYourCheckin fell apart.
Still have my fingers half-crossed that I don’t botch anything up…
The fun, secret part is that Kathleen hasn’t (yet?) discovered IndieAuth so that she can authenticate/authorize micropub clients like Quill to publish content to her own site from various clients by means of a potential micropub endpoint.
I’ll suspect she’ll be even more impressed when she realizes that there’s a forthcoming wave of feed readers1,2 that will allow her to read others’ content in a reader which has an integrated micropub client in it so that she can reply to posts directly in her feed reader, then the responses get posted directly to her own website which then, in turn, send webmentions to the sites she’s responding to so that the conversational loop can be completely closed.
She and Lee will also be glad to know that work has already started on private posts and conversations and posting to limited audiences as well. Eventually there will be no functionality that a social web site/silo can do that a distributed set of independent sites can’t. There’s certainly work to be done to round off the edges, but we’re getting closer and closer every day.
I know how it all works, but even I’m (still) impressed at the apparent magic that allows round-trip conversations between her website and Twitter and Micro.blog. And she hasn’t really delved into website to website conversations yet. I suppose we’ll have to help IndieWebify some of her colleague’s web presences to make that portion easier. Suddenly “academic Twitter” will be the “academic blogosphere” she misses from not too many years ago. 🙂
If there are academics out thee who are interested in what Kathleen has done, but may need a little technical help, I’m happy to set up some tools for them to get them started. (We’re also hosing occasional Homebrew Website Clubs, including a virtual one this coming week, which people are welcome to join.)
Last week was the 8th annual IndieWeb Summit held in Portland, Oregon. While IndieWeb Camps and Summits have traditionally been held on weekends during people’s free time, this one held in the middle of the week was a roaring success. With well over 50 people in attendance, this was almost certainly the largest attendance I’ve seen to date. I suspect since people who flew in for the event had really committed, the attendance on the second day was much higher than usual as well. It was great to see so many people hacking on their personal websites and tools to make their personal online experiences richer.
Last year I wrote the post Feed Reader Revolution in response to an increasingly growing need I’ve seen in the social space for a new sort of functionality in feed readers. While there have been a few interesting attempts like Woodwind which have shown a proof-of-concept, not much work had been done until some initial work by Aaron Parecki and a session at last year’s IndieWeb Summit entitled Putting it all Together.
Over the past year I’ve been closely watching Aaron Parecki; Grant Richmond and Jonathan LaCour; Eddie Hinkle; and Kristof De Jaeger’s collective progress on the microsub specification as well as their respective projects Aperture/Monocle; Together; Indigenous/Indigenous for iOS; and Indigenous for Android. As a result in early May I was overjoyed to suggest a keynote session on readers and was stupefied this week as many of them have officially launched and are open to general registration as relatively solid beta web services.
I spent a few minutes in a session at the end of Tuesday and managed to log into Aperture and create an account (#16, though I suspect I may be one of the first to use it besides the initial group of five developers). I also managed to quickly and easily add a microsub endpoint to my website as well. Sadly I’ve got some tweaks to make to my own installation to properly log into any of the reader app front ends. Based on several of the demos I’ve seen over the past months, the functionality involved is not only impressive, but it’s a properly large step ahead of some of the basic user interface provided by the now-shuttered Woodwind.xyz service (though the code is still available for self-hosting.)
Several people have committed to make attempts at creating a microsub server including Jack Jamieson who has announced an attempt at creating one for WordPress after having recently built the Yarns reader for WordPress from scratch this past year. I suspect within the coming year we’ll see one or two additional servers as well as some additional reading front ends. In fact, Ryan Barrett spent the day on Wednesday hacking away at leveraging the News Blur API and leveraging it to make News Blur a front end for Aperture’s server functionality. I’m hoping others may do the same for other popular readers like Feedly or Inoreader to expand on the plurality of offerings. Increased competition for new reader offerings can only improve the entire space.
Just before the Summit, gRegor Morrill unveiled the beta version of his micropub client Indiebookclub.biz which allows one to log in with their own website and use it to post reading updates to their own website. For those who don’t yet support micropub, the service saves the data for eventual export. His work on it continued through the summit to continue to improve an already impressive product. It’s the fist micropub client of its kind amidst a growing field of websites (including WordPress and WithKnown which both have plugins) that offer reading post support. Micro.blog has recently updated its code to allow users of the platform the ability to post reads with indiebookclub.biz as well. As a result of this spurt of reading related support there’s now a draft proposal to add
read-status support as new Microformats. Perhaps reads will be included in future updates of the post-type-discovery algorithm as well?
Given the growth of reading post support and a new micropub read client, I suspect it won’t take long before some of the new microsub-related readers begin supporting read post micropub functionality as well.
In addition to David Shanske’s recent valiant update to the IndieAuth plugin for WordPress, Manton Reece managed to finish up coding work to unveil another implementation of IndieAuth at the Summit. His version is for the micro.blog platform which is a significant addition to the community and will add several hundred additional users who will have broader access to a wide assortment of functionality as a result.
While work continues apace on a broad variety of fronts, I was happy to see that my proposal for a session on IndieAlgorithms was accepted (despite my leading another topic earlier in the day). It was well attended and sparked some interesting discussion about how individuals might also be able to exert greater control over what they’re presented to consume. With the rise of Indie feed readers this year, the ability to better control and filter one’s incoming content is going to take on a greater importance in the very near future. With an increasing number of readers to choose from, more people will hopefully be able to free themselves from the vagaries of the blackbox algorithms that drive content distribution and presentation in products like Facebook, Twitter, Instagram and others. Based on the architecture of servers like Aperture, perhaps we might be able to modify some of the microsub spec to allow more freedom and flexibility in what will assuredly be the next step in the evolution of the IndieWeb?
While there are miles and miles to go before we sleep, I was happy to have seen a session on diversity pop up at the Summit. I hope we can all take the general topic to heart to be more inclusive and actively invite friends into our fold. Thanks to Jean for suggesting and guiding the conversation and everyone else for continuing it throughout the rest of the summit and beyond.
Naturally, the above are just a few of the bigger highlights as I perceive them. I’m sure others will appear in the IndieNews feed or other blogposts about the summit. The IndieWeb is something subtly different to each person, so I hope everyone takes a moment to share (on your own sites naturally) what you got out of all the sessions and discussions. There was a tremendous amount of discussion, debate, and advancement of the state of the art of the continually growing IndieWeb. Fortunately almost all of it was captured in the IndieWeb chat, on Twitter, and on video available through either the IndieWeb wiki pages for the summit or directly from the IndieWeb YouTube channel.
I suspect David Shanske and I will have more to say in what is sure to be a recap episode in our next podcast.
Finally, below I’m including a bunch of photos I took over the course of my trip. I’m far from a professional photographer, but hopefully they’ll give a small representation of some of the fun we all had at camp.
While I’m thinking about it, I wanted to take a moment to thank everyone who came to the summit. You all really made it a fantastic event!
I’d particularly like to thank Aaron Parecki, Tantek Çelik, gRegor Morrill, Marty McGuire, and David Shanske who did a lot of the organizing and volunteer work to help make the summit happen as well as to capture it so well for others to participate remotely or even view major portions of it after-the-fact. I would be remiss if I didn’t thank Martijn van der Ven for some herculean efforts on IRC/Chat in documenting things in real time as well as for some serious wiki gardening along the way. As always, there are a huge crew of others whose contributions large and small help to make up the rich fabric of the community and we wouldn’t be who we are without your help. Thank you all! (Or as I might say in chat: community++).
And finally, a special personal thanks to Greg McVerry for kindly letting me join him at the Hotel deLuxe for some late night discussions on the intersection of IndieWeb and Domain of One’s Own philosophies as they dovetail with the education sector. With growing interest and a wealth of ideas in this area, I’m confident it’s going to be a rapidly growing one over the coming years.
I’d also like to take a moment to say thanks to all the sponsors who helped to make the event a success including Name.com, GoDaddy, Okta, Mozilla, DreamHost, and likely a few others who I’m missing at the moment.
I’d also like to thank the Eliot Center for letting us hosting the event at their fabulous facility.
In this last episode before David Shanske and I head to the Indieweb Summit in Portland, Oregon, we discuss updates to people’s Indieweb experience, little things David has hidden in plugins, web-signin vs IndieAuth, etc.
We’re both looking forward to seeing those of you who can join us in Portland.
I've made the difficult decision to drop support for Twitter authentication on IndieAuth.com. Some time last week, Twitter rolled out a change to the website which broke how IndieAuth.com verifies that a website and Twitter account belong to the same person.
Another case of “silos gonna silo.”
In these times of centralised services like Facebook, Twitter, and Medium, having your own website is downright disruptive. If you care about the longevity of your online presence, independent publishing is the way to go. But how can you get all the benefits of those third-party services while still owning your own data? By using the building blocks of the Indie Web, that’s how!
Presentation slide-deck: speakerdeck.com/adactio/taking-back-the-web
Summary: At long last, after about three weeks worth of work, David Shanske (along with help from Aaron Parecki) has added the ability for the IndieAuth plugin for WordPress to provide an IndieAuth endpoint for self-hosted versions of WordPress, but it also has the ability to provision and revoke tokens.
This week, David Shanske and I discuss IndieAuth and the WordPress plugin’s new functionality as well as some related micropub work David has been doing. To some extent, I alternate between acting innocent and serving as devil’s advocate as we try to tease out some of the subtleties of what IndieAuth is and what it means to the average user. As usual, David does an excellent job of navigating what can be some complicated territory.
If you need more IndieWeb content, guidance, or even help, an embarrassment of riches can be found on the IndieWeb wiki, including the following resources:
Today I updated the IndieAuth plugin for WordPress, and I can now use my own website as an IndieAuth authorization endpoint (including provisioning and revoking tokens) for a multitude of things including a huge number of micropub clients.
Part of my own project for this week, while taking off for the holiday, was to complete work on an Indieauth endpoint for WordPress.
IndieAuth is layer on top of OAuth 2.0, a standard that grants websites or applications access to their information on other websites but without providing passwords.
OAuth is already being used by a variety of services…Login with Facebook or Login with Google options on sites are usually OAuth based. The difference is that for IndieAuth, users and clients are all represented by URLs.
This is awesome! I can’t wait to use my own website to authenticate myself.
Khürt , The majority of them don’t link back because the silos (like Keybase, Instagram, and Medium which you mention) aren’t putting the rel=”me” microformat on the URLs in your profile like Twitter, Github, and Flicker do. If you view the page source for those silos, you’ll see that they list your URL, but don’t have rel-me’s pointing back at you. Sadly, you can’t control these, though you could file issues with the sites that don’t to encourage them to.
The indiewebify.me site has a parser that is looking at the two sites to see that they not only point at each other, but it requires that the two links have the rel=”me” microformat on them. Most don’t, but this doesn’t mean too much in practice. Whether or not they both have rel=”me”, the only way both sites could point at each other indicates that you “own” or control them both. Kevin marks has proposed/built an interesting decentralized verification service based on them. His version is certainly much better distributed than Twitter’s broken verification set up.
Other than having a stronger two-way ownership indicator, what do you get out of them? As you mention, some have the ability to be used with IndieAuth. Those that can be used with IndieAuth are relying on the service (like Twitter or Github) having a OAuth implementation for signing into their services. This allows an indie site to piggyback on another services’ OAuth implementation without having to go through the trouble to build one themselves, which can be a lot of work to do, much less do correctly (securely). Most of the services you see not linking back not only don’t add the rel=”me” tag, but they also don’t support OAuth, so you wouldn’t get too much more out of having the correct reciprocal link anyway.
Incidentally, one of the benefits the rel=”me” links do have is that they allow you to use your website to log into the IndieWeb wiki to participate directly in that part of the community. (Give it a try!)
Some services like Brid.gy get around services like Instagram or Facebook not having a physical rel=”me” microformat because they’re relying on looking at the appropriate data (usually via API) on your profile page to see if it links back (either in your website field or typically in your bio).
Don’t be overly concerned that the vast majority of sites appear not to link back even if you’ve got links on both pointing back. (And if you think your batting average is bad with only 4 of 43, just imagine how many of my 200+ sites do?!)
Some of these building blocks will likely add a lot more value later on as more and more sites explicitly indicate their relationship to and from each other.