Validate me on Indiewebify.me
While listening to ep. 6 of season 4 of Mozilla's IRL Podcast by Manoush Zomorodi, I discovered - unfortunately only now - Indieweb.org, the people-focused alternative to the "corporate web".
I got immediately intrigued by its concepts of decentralization and taking back control over our online presences. I'm not against corporations, it's only that I strongly believe the Web should be for everyone to publish freely in whatever format they want and have control over their own Web Presence.
The concepts of the IndieWeb are:
- Your content is yours
- You are better connected
- You are in control
Before visiting Indieweb.org, I had no idea that my site was simply missing MicroFormats as class-names and a couple of links before I could use it for Web Sign-in. Awesome.
I followed the instructions on the Getting Started page and quickly was able to make my personal homepage a key which can be used to authenticate with Indielogin and IndieAuth services.
Users will identify themselves with their website, and can authenticate using one of the supported authentication providers such as Twitter, GitHub, or email. The user ID returned to you will be their website, ensuring that you don't end up creating multiple accounts depending on how the user authenticates.
~ Source: https://indielogin.com/api
Adding the MicroFormats 2 to my existing HTML and Jekyll templates was easy-peasy.
Validate my site on indiewebify.me
Next steps include:
- ✅ Implementing Webmentions - Not sure how to achieve this with my SHTML static Apache pages. - Managed to do this easily with https://webmention.io and https://brid.gy.
- ✅ Set up POSSE - Also here, I'm not sure how to do this from my static pages. - Republishing statuses and posts on social.johanbove.info to Twitter using Brid.gy
- ❎ Attend a Homebrew Website Club meetup event. - I would like to go to the 2019 IndieWebCamp event in Düsseldorf.
- ❎ Create an app which applies https://indielogin.com for authorization using Web Sign In
And that's only the beginning...
Thanks to Greg McVerry for the correct terminology, Aaron Parecki and Tantek Çelik for starting up the IndieWeb movement!
Actively supporting the Known CMS development by offering my spare time to fix open "Known CMS" issues. Looking at the issues list and commenting my remarks and seeing if it's something I can work with too.
Here is the list of Issues on Github that I am currently tracking.
Got in touch with Known developer Marcus Povey and IndieWeb promotor Greg McVerry as part of my contributions and participation to the Known Open Collective.
Haven't been able to set up the Known CMS on my local system yet. I have been risking my own site when testing changes I made myself on my live Known site. Really need to get this LAMP stack going on my Windows 10 + Ubuntu Bash For Windows combo again.
Contributing to the IndieWeb effort by editing the wiki and started contributing to the Known Open Collective groups and monitoring and participating to the IndieWeb IRC channels. The
#indieweb-meta channel especially is really interesting as it integrates Twitter mentions for any IndieWeb related topic. Thanks to this very useful integration I got to know a group of interesting IndieWebbers who are sharing insightfull articles on their own sites and syndicating these on the corporate silos like Twitter and Facebook.
Got the "Known Twitter" plugin working, but I am still using brid.gy for a more stable publication to Twitter. It happens in some cases that the webmention context is not set correctly using the plugin.
Trying to keep up with Marcus Povey with the latest releases of Known. It's not easy however for me as the composer installation fails on my hosted web server. So I need to do manual updates. Also, I haven't had much success installing the Known instance on my local server. In fact, it got to a point where I got frustrated and decided to reinstall WSL (aka "Ubuntu on Windows"). So now I am working without a local server as I hadn't had the time to reset everything.
Trying to promote the IndieWeb movement at work. It seems not many colleagues actually have their own websites. So it's a bit of a hard sell.
Successully Installed Known version 0.9.9-a maintained by Marcus Povey on https://social.johanbove.info.
Including the set up Brid.gy from my site to Twitter, which is an IndieWeb syndication tool by Ryan Barrett, Kyle Mahan, and many other contributors to perform #POSSE to corporate Web silos. It also handles webmentions pretty well.
Had to change the Twitter profile website link to point to my social.johanbove.info site to make Brid.gy work as it authenticates you by checking this a tag which has the
rel="me" attribute. This is an implementation of Web Sign-in.
My Brid.gy profile: https://brid.gy/twitter/johanbove#
Known has a Twitter plugin, but it doesn't seem to authenticate on my server, so I added my vote and comment to this existing issue.
Setting up the application in Twitter requires you to fill in an extensive form declaring - much like in customs - what your intensions are in developing the app. I simply stated the truth as that I only want to syndicate the posts from my personal site to Twitter.
Setting up "Known" on my server for my own social publishing platform.
It's open source and free to host on your own system - which the recommended system requirements of PHP 7 and MySQL.
- ✅ Set up sub domain for https://social.johanbove.info
- ✅ Set up MySQL database (or use SQLLite?) - MySQL is recommended.
- ✅ Follow the installation instructions for Known
- ❎ Set up a local instance of the Known server (Ubuntu bash for Windows) for development and testing.
Figuring out how to include Brid.gy on my site; it supports backfeed, POSSE and webmention support as a service.
I'd like to achieve the same content as this working example of a Brid.gy integration by its creator Ryan Barett.