#indieweb

The IndieWeb own-your-data-thing can be complicated sometimes. Since there are no full fledged systems that allow us to interact with other social media without having to implement it ourselves, sometimes we get to the point where we feel kind of limited. I’m trying not to use other services or, if I do, I’m just POSSE’ing to them. Sometimes it’s hard because there are communities that are more connected on some social media (e.g., Twitter) and the bridge is not always perfect.

Edit: I just hope someday we can have a federated social network that can easily interact with all others…

Just wondering if it’s worth it to keep my watches log and checkins on my website. I know I had some work setting that up. But, is it worth it? Is it worth for you, readers?

I like having that data accessible and I still can by just using the APIs and backing up the data myself. It can be useful and it can have many uses. But is it worthy to have on this website?

For maintenance purposes, it’s a bit harder but not impossible. For you, readers. I’d love your opinion on this. I’ve b en thinking about removing swarm checkins because of privacy issues.

About the watches: maybe it’d be nice to have a page listing the series and movies I’ve watched but not as logs.

OwnYourTrakt

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.

It now holds my web interactions, such as replies, likes and reposts, as well as my reading log. Since the beginning, I also wanted to this website as a place to store my watch logs. With watch I mean watching movies and TV series.

Owning my reading log

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.

With university, work and… life… I stop reading as much as I did before. But it’s now time to get back to some reading. Even if it’s not that much, I need to read something. I must do it.

I just added a little form in the webmentions section on the posts so you can send your webmention manually if it didn’t hit my website. Or, you can also use the button ‘Write a comment’ to create a comment (that can be anonymous) through the comment parade service.

For the curious ones out there, the code is simple. Please remember that I’m using Go templates with Hugo:

<form action="https://webmention.io/hacdias.com/webmention" method="post">
  <input name="source" placeholder="Have you written a response? Paste its URL here!" type="url" required>
  <input name="target" value="{{ .Permalink }}" type="hidden">
  <input value="Send Webmention" type="submit">
</form>

<form method="get" action="https://quill.p3k.io/" target="_blank">
  <input type="hidden" name="dontask" value="1">
  <input type="hidden" name="me" value="https://commentpara.de/">
  <input type="hidden" name="reply" value="{{ .Permalink }}">
  <input type="submit" value="Write a comment">
</form>

After talking to @jhelse, I finally decided not to trouble myself with writing my own static website generator and just improve what I have right now. I feel so much better now for some reason. I’ve already imported the small design tweaks for the live website. There are, definitely, some other things to improve. However, I will only focus on that next week 😁

I was going to say that I decided to do incremental builds (this is relative to my previous post) and it’s almost done. However, I feel that I need to regenerate too many pages after each update and I might not need that unless someone wants to visit the page… Maybe I’ll ditch IPFS support while I don’t come up with a good solution for staticness. Or maybe there’s a more flexible, still fast, static website generator that I don’t know of that would let me use whatever organization I want. Need to think about this.

On building my new site system: undecided between 1. all static with a custom static generator that takes much more time than Hugo would, with incremental builds for each post (faster than running Hugo each time) or 2. totally dynamic with pages being rendered on the fly with cache and pinning every day a copy to IPFS.

Build a dynamic website… or not?

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.

I opened a topic on Hugo’s discourse to see to which point it would be reliable to use the watch mode of Hugo in production and it seems, as I was expecting, that it wasn’t made for that and there is no way of making incremental builds as of right now. And I don’t blame Hugo developers — I understand that’s quite a big issue and it needs to be a really thoughtful process.