IndieWeb is the way
Two months ago I started implementing IndieWeb principles on my website. I use started because it has been a long process of tinkering with different tools and learning to use technologies I never expected to be using.
Naturally, the progress has been slow as I’m often running into problems beyond my skillset. However, by reaching out to other community members I’ve been able to slowly setup things kind of the way I want. Because it’s true that on the IndieWeb everyone assumes you’re a developer, but most people are nice enough to open source their code and even go the extra mile helping with one’s particular use cases.
This website’s original goal was for me to have an online presence that was fully controlled by me, but thanks to the IndieWeb it’s turning into my single Internet channel. And how can it not progress in that direction when there’s many inspiring websites on the IndieWebring alone?
What started as moving my content back to Jekyll from Tumblr, resulted in personal website that implemented microformats, used a Heroku-hosted micropub endpoint and relied on Quill to post updates. Right now everything I need to post or read online is hosted on my personal domain.
I’m using a slightly modified version of this micropub endpoint hosted on Netlify and I’m customizing a micropub client, it’s fully functional at the moment, but I’m still trying to figure out how to get it to store sessions longer (or indefinitely), it deletes them automatically after x time. Self-hosting a social reader like Together or Monocle sounds like the next reasonable step but I love yarr! too much to give up on it, so I finally put everything on a subdomain and this is how I’m posting and reading on the Internet these days:
I know there’s a lot to improve in this setup, and who knows, maybe some day, I can build implementations of IndieAuth, Webmentions, etc… or build something as cool as Tanzawa or Eagle, but as of right now, this is something I’m kind of proud of and felt like that was worth sharing here.