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.

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.

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.

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.

In 2015, I started a project called http.hugo, which was a just a simple plugin for Caddy, a really fast web server built with Go with automatic HTTPS. At the time, the plugin was exclusive for Caddy and it provided a simple UI to edit your files in the server, rebuild the website and so on. They were just simple features.

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.

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:

The Micropub protocol is used to create, update and delete posts on one’s own domain using third-party clients.

So it’s basically a simple common protocol that could let any website get updated using an arbitrary CMS (Content Management Software) or application that supports it. I really enjoyed the spec and there’s suggestions and issues being worked on.

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!

There are so many, but so many concepts in the IndieWeb world that I could never imagine before, but first: I need to support multiple data types because this website will now on hold more than just long articles like this one. We will support notes, bookmarks and articles for now.

Data, data, data.

Big data, buzz words. I have been wanting to write about data for quite a long time already, but I’ve never found a moment where that would be opportune for me. Data is one of the most important resources for companies right now even though we don’t acknowledge it most of the times.

Some days ago, on the 30th of November, I gave my first talk at BarcampLX, which is a really nice and open event you can go to and present! If you’re interested, you can read more about the concept.

Here’s the talk:

The slides deck.

Protocol Labs (PL) is a research and development institution for improving the Internet technology. Focusing on IPFS, the InterPlanetary File System, we’re building a decentralised, P2P and content-addressable network for future-proofing the web.

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.

As many of you probably know, xkcd is a web comic created in 2005 by Randall Munroe. Its tagline is “A webcomic of romance, sarcasm, math, and language”. You can read more about the web comic itself on their website.

As part of wanting to contribute to IPFS Archives, I decided to look at the issues and find the most interesting one for me, and I did: xkcd! There were some clones already built, but all of them were out of date and weren’t automatically updated.

Recently I’ve been wanting to try out more things in my life. Perhaps not recently, I always have this urge to try out this “new” things that I haven’t done before and that they seem to be… I don’t know… interesting to me.

I’ve been wanting to write about my journey at Protocol Labs for a while already. Well, for a big while but unfortunately I haven’t had the time nor the disposition to write: the last post I wrote was in June 2017. This is something I want to change.

Go is a relatively new player in the world of programming, having been around since 2009. It was created by Google and many open-source contributors.

It has recently reached version 1.9 and 2.0 is on its way. Despite having only 8 years, its popularity has been increasing exponentially, mainly on networking and web server fields.

On 18th June 2015 I went to Lisbon to attend the Landing Festival — a tech jobs event organised by Landing.jobs. I was 15. And now you ask: what was a 15-year-old boy doing in a job fair? So, I was there as a journalist for Pplware. Though that’s not the piece of information that matters, I have to thank a lot to them because they were my ground floor.

Upframe is a movement built by students, professors, companies, incubators and startup founders worldwide with the mission to promote the development of an entrepreneurial mindset in students.

Nowadays, we are used to hear about bits and bytes and sometimes, in the advertising, we see that the Internet speed is about 100 Mbps. Is that 100 megabytes per second? No, it isn’t. There are some differences between bits and bytes. Let’s see.

Bit stands for Binary Digit and it is the smallest unit of information that can be stored or transmitted. A bit can only hold one out of two values: 0 and 1, in other words, the binary code. Bits are represented by a lower case “b”.