Shower thought: do you think the boxes with context about replies, likes and reposts are needed? I’m trying to reduce the complexity and cut edges that I don’t think are needed. I could just re-style it in a way to show that it is a like or repost with a link without the “entire” information - which, most of the times, is not the entire stuff because I set a maximum length.
If you’re reading this, what’s your opinion? Is it really required? Do you find it useful? Or just pretty?
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…
I’m thinking about adding a photos page to this website and start using Instagram less and less for that purpose. I’d like to serve them with the best resolution possible (not directly, but through a link) but some of them occupy several megabytes of space and I can’t afford to add that to Git. In addition, Hugo doesn’t seem to play well with Git LFS.
I thought about using BunnyCDN’s image optimization service to provide images in different formats and sizes but that costs 9.5€ a month and I do believe that that would be much more than what I need. Hugo’s capable of generating all the pictures I need. However, there’s the space problem. Where do I put them?
Also, do you use any CDN? If so, how do you backup the data you have on it?
I think just successfully added ActivityPub support to my website. You can now follow @[email protected] from any ActivityPub instance and receive my latest posts! Here’s a gist of the changes I made. For now, I just support follow requests and create requests which are converted to webmentions!
I just spent a lot time trying to send signed requests to accept ActivityPub followers. It’s not working! I make the requests to Mastodon and their servers reply with 202 but the ‘Cancel follow request’ button does not change to ‘Unfollow’ and I don’t know what the problem is. In addition, the test suite has not working for over a year it seems. Ugh…
For quite a few time, I used Bear as my go-to Notes application for two reasons: it was single 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.
After searching for a bit I found out an app called Notable. In addition to having all the features I wanted from Bear, it is also storage independent, meaning everything is stored as markdown plain-files that I can version control with Git or some similar software.
This is just a FYI: if you’re interested, I recently added a knowledge base section to the website where I automatically deploy de notes I write with Notable. I actually have some ideas of things to add to these notes when I have time. It’s actually quite simple: just set up a GitHub hook, pull the notes repo, convert them to Hugo’s format and et voilá!
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.
The Trakt API gives you so much information about every episode and every movie: from the title, to the rating, description, channel where it aired, when it aired first, the countries where it aired, etc, etc. I don’t actually need all that information, but it’s never too much to store.
I’m wondering if there’s any interesting software to build git based wikis (or at least with a flat file storage) that support Markdown and ACL for private and public posts and is extensible enough to allow me to customize it the way I want. I have a bunch of notes I’d like to make public just because they might be helpful for someone else. I thought about integrating it into this website but I’d love to have a way to have private posts, as well as easily linking between pages. The most interesting option I found was DokuWiki which was tons of plugins. However, it’s PHP and I’m not sure about how maintained it is nowadays. It looks like wiki software is dying… besides the big beasts.
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.
After publishing the post to which I’m replying to, @jlelse contacted me and I noticed the import directive in Caddy can be used to import files:
import allows you to use configuration from another file or a reusable snippet. It gets replaced with the contents of that file or snippet.
So I just decided to build the redirects file using Hugo itself. First of all, I needed to import a lot of redirects as aliases because I had them in a separate file, but this way it’s much better. After that, I needed to add a new output type to Hugo’s config:
disableAliases: true
outputFormats:
redir:
mediaType: text/plain
baseName: redirects
isPlainText: true
notAlternative: true
outputs:
home:
- redir
Then, I created a layouts/index.redir.txt file with the following content:
{{- range $p := .Site.Pages -}}
{{ range .Aliases }}
{{ . | printf "%-70s" }} {{ $p.RelPermalink -}}
{{ end -}}
{{- end -}}
This is mostly what you can see on this commit of the official hugo docs for their netlify redirects. With this, my Hugo website does not build any HTML aliases (disableAliases), but creates a file on the root called redirects.txt which you see here. I can just block the access through Caddy but there’s no reason I should do so. Is there?
On Caddyland, I just added this snipped:
hacdias.com {
root /the/public/path/
redir 301 {
import /the/public/path/redirects.txt
}
}
And voilá! It works! But now you ask: what if we change the redirects file and we don’t wanna have any downtime? Just configure your Micropub entrypoint or whatever software you’re using on the backend to do a config hot reload by executing the following command:
pkill -USR1 caddy
There it is! 301 redirects working flawlessly!
So I just made a few changes to my website and I hope it didn’t break anything like feeds and such. Here’s a small changelog of the changes:
/note path. So this also changed the URLs, hopefully for better and now it’s easier to restrict access or remove something if I want.partialCached in some places which improved the build time a tiny bit./blog to /articles which I already wanted to do for a while.And… that’s it I think. I’d also love to use this website as a “knowledge base” so I’ll probably create a section for that later. I always want to organize the knowledge I get somehow but I just have tons of files from university and other stuff laying around without any organization. I really loved this braindump from Jethro.
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.
I just set up a media endpoint based on BunnyCDN, inspired by @jlelse’s post. So far, it’s working really well.
For now, I’m not actually using it to post many of the images of the website, even though I could. However, I’m using it to store the webmentions author’s photos. They were being served directly by webmention.io but I think it’s better to serve them myself.
The media endpoint works well: it receives an object and stores it on BunnyCDN. However, I want to add some customization options such as resizings and compressions for images through query parameters, as well as some default ones so I don’t need to always specify them.
Just solved the deadlock! I’m currently using the p-limit package to limit the number of concurrent actions made to the website source. Basically, inside a function wrapped by that limitation, I was waiting for another function that would require the limit to be complete! Of course, that would create a never-ending deadlock. Fixed now!
On a second thought: I don’t actually like the structure of the internal code I use to process all of this. Maybe I should rearrange some things to make them… better.
It wasn’t working on the server because I didn’t pull the changes… Was it that hard?
Just checking if posting this causes a deadlock!
Just found a deadlock on my micropub endpoint! I KNEW IT!
P.S.: This post will trigger the deadlock!
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.
Just made a few updates to my website:
swapoff. It’s a really pretty syntax highlight theme provided by Chroma, the library Hugo is using. The best thing is: using the invert() CSS filter it keeps looking good. This way, I have good syntax highlight on both the light and dark themes.I just noticed the website on the dark mode flickers sometimes (from the light to the dark theme). I know this is caused by the fact that I’m using JavaScript to pick the theme depending on the OS choice + the manual overriding done by the user using the option on the bottom of the page.
One option to remove this problem would be to just follow the user’s OS choice (either dark or light) and there wouldn’t be a manual override. Unfortunately, this wouldn’t let the users pick a different theme if they prefer to read websites on a different light - no pun intended.