known as @hacdias
Today I have been thinking about my website. Mainly about ditching Hugo and moving to a completely custom and dynamic website. There are a few reasons about why I would like more flexibility. However, I don’t know if it justifies the effort.
Today I have been thinking about the possibility of writing my own CMS. A very simple CMS. I even hinted that on a small micro post today. This is not a new idea. I’m not going to look at the previous posts where I talked about this, but it’s definitely at least 2 or 3.
My website is growing, not in terms of views, because I’m not aware of that. Maybe I should add some non-intrusive analytics. Anyways, it’s growing in terms of functionality. However, since I’m using a static website generator, it makes it complicated to add some interactive functionalities.
Over the past months, I have been reading more and more posts where people are saying they miss the vibe of the 90s web. Even though I wasn’t alive to see how that web was, I still remember the website of my high school filled with overly saturated colors, GIFs and iframes. Not only that characterizes some of the pages of the early web, but also the pixelation and the footers saying to use X or Y browser.
I decided to make a few updates on my website - again. However, this are a bit more than visuals and I’m mostly reinventing the way I manage IndieWeb posts, namely likes, reposts, notes and replies.
For quite a few time, I used Bear as my go-to Notes application for two reasons: it was simple to use and the syntax was quite similar to markdown. However, it is not markdown and it does not support some things that’d like to see on such software: diagrams, mathematics, wiki-like links, etc.
Today, I decided to readd a watches page, but this time it isn’t built from hundreds of
posts, but from the data that I get directly from Trakt’s API.
I built a small tool called trakt-collector used
to collect your history and save it in JSON format.
For quite some time, I have been getting more and more into the IndieWeb world and trying to own my own data. I have started publishing more to my website and using it as a place to store most of my public data, i.e., data I already published on other social media and platforms.
As Tom once said, it is now time to own my own reading log. Why? Despite all the reasons mentioned on Tom’s post, I also got bored of Goodreads and I ended up not using it as much as I should have.
After digressing a bit about building a Micropub endpoint for my website, I’ve been thinking about the next steps: if I should keep Hugo or move to some other system.
Recently, I have talked about restructuring the URLs of my website and adding IndieAuth so I could use my domain as my main online identity to login into services. Along those lines, I came across Micropub. In their own words:
This is going to be a quick post — I hope.
After updating the structure of the URLs on my website, I felt like the next step would be to implement IndieAuth because almost everything on the IndieWeb needs that.
I’m now working on making my website more IndieWeb friendly, which was triggered by my searches after writing my last post about owning our own data. It has been… harder than I though. But in a positive way!
It was about two years ago, in 2017, that I got to know IPFS through David Dias. This is not the first time I talk about IPFS here, in my website, but here’s a brief description of what it is: IPFS stands for InterPlanetary File System and it is a peer-to-peer, content-addressed and decentralized protocol.
Firstly, a little bit of history - when I begun this blog, I’ve already been using WordPress on Pplware for a while. So, I tought: I know it, it’s simple, it’s easy to use, I’m going to use it on my personal blog.
