Each day, it seems there is always something new happening in the world of newsletters. When it’s not someone famous who joins Substack, a company out of nowhere offers a brilliant idea built around supporting newsletters in one way or the other. I’m thinking of Hey in particular.

“Email is the internet’s oldest instant self-publishing platform. Except you have to define a small audience every time you write. But what if you didn’t? What if you could just email the web to reach the world? Introducing the HEY World experiment” - Jason Fried from HEY

Yesterday, the company behind the popular HEY email client tentatively announced a new service for their customers. The idea behind is to allow any HEY users to create newsletters and publish them just by sending them to world@hey.com. The service would then post these newsletters on the web, complete with the author’s name. A simple static page, no tracking, no nothing more. I call this: simply brilliant.

The service is not currently available, only in some form of alpha-stage for internal use only. They announced it to read the room and see if there is some interest in something like this that could become some soft of hyper-distributed publishing platform.

I’m personally interested in this kind of service simply because it removes friction in the publishing process. What could be simpler than just writing the newsletter like we do with emails and then hit “send”!? Simply brilliant. For the reader, they can subscribe by email or by using the available RSS feed.

You can read the announcement here. I like the simplicity of this implementation. Very clean. Very lean. I’m in love. Too bad this isn’t available — yet.

In the last few months, on Twitter and on Micro.blog, I’ve been witnessing something that takes the shape of a small phenomenon: people are moving from one place to another in the digital space. Many are writing about their experience of moving from one hosting site to another. Some are leaving WordPress to return to Ghost. Others are proudly putting together their hosting solutions. The same happens in the newsletters hosting space: people are leaving Mailchimp to go to Substack or Revue. People are looking to get better return on their investment both in time and money. Others are simply trying to optimize their blogging workflow. There is a myriad of reasons why people decide to leave a place for another one.

I find these numeric movements quite fascinating. Are you one of those guys?

So I started another experiment involving Blot.im. For those who don’t know Blot.im, it is a static web site generator that seems popular among the crowd here. On paper, the process of publishing is very simple: you drag and drop files on a specific folder on your computer and they get instantly published on the web. Sound great, right? That’s what I thought.

My goal with Blot.im is to do some “meta blogging”; a place where I could write about the tools, services and my blogger workflow. So I registered a new domain with GoDaddy: numericcitizen.io. Then, I opened my Blot.im account and stated experimenting. The initial setup is pretty simple. And then challenges pretty quickly started to emerge.

First, I wanted my new domain to point my Blot.im domain. Tried to follow the Blot.im instructions to make it work but all attempts failed. GoDaddy doesn’t support ALIAS DNS records as Blot.im ask me to create. I asked for help from Blot.im support. Still a work in progress.

Second, I chose to use Git as the “client” to push content on the service because I don’t want to use Dropbox, a service I despise. By using Git, I need a Git client on my Mac. I’m tentatively settled on Nova. So far so good. After cloning the Git repo from Blot.im to my local machine, I can then use Ulysses to write my posts and push them with Nova. The workflow is very geeky: create .MD file in Ulysses, “commit” within Nova then hit “push” to publish. Not as seamless as I would like. But here another issue: inserting images with a Markdown file is not as easy as it seems. Again, trying to figure out instructions on Blot.im site doesn’t work. The other thing is that if you drop an image within a folder, it will trigger Blot.im to create its own blog post, something that I don’t want. Not cool. Again, I’m asking support to help me here with this supposedly trivial task.

Third, I would like to use Github as the source of truth. Setting up a new repo is simple and cloning it to my local machine too. But, now, how do I make Blot.im to use the Github repo as the source of content? Again, trying to figure out Blot.im instructions but failing to make it work. Still trying to figure that out.

Fourth, tweaking the visual appearance is not as easy as I would have liked. There is a theme editor and I still need to be pretty knowledgeable in HTML and CSS. I did fork one of the theme to make it mine and started to do some tweak but it is a painful trial-and-error process.

All in all, I’m far from positive about Blot.im right now. I spent way too much time on these issues. I’m not sure where this is all going. If you are using Blot.im, please, do me a favour and chime in!

I’m still new to the Indieweb world. Today, I’m learning about webmentions. I like the idea of linking reactions back to the origin. So, after enabling a plugin on my main blog, I’m trying to link back to one of my recent post and see what happens. One day, I wrote “The Journey is the Reward”. I don’t post personal things very often. Thanks for your feedback.

I’m in love with Micro.blog. It’s simple, not too busy. Based on open web standards. But today, I’m a bit frustrated with the bad sad of being too simple. My most important grievance is the lack of design flexibility. Built-in themes are too basics and unappealing. You have to be a HTML and CSS expert to try to figure out how to make simple tweaks. This frustration is behind my recent desire to look elsewhere for hosting the whole thing. I’m willing to invest quite a bit of my time to gin control of the appearance of my online presence. I’m patient. The guys behind Micro.blog are working on the next features and I hope they will address some of my complaints.

It all started with the idea of tweaking my micro.blog visual theme. I don’t like it, but this is the best that I could find from the included themes. After reading for a while and seeing people writing about their blogger workflow, I found out that Micro.blog is using Hugo, a static website generator. Then I started to learn about Hugo by searching for introduction videos on YouTube. Then, I learned about Hugo themes and how they are constructed, and at the center of how a website is displayed. Since static websites need a place to be stored, GIT and Github came into the picture. So, I started to read about GIT and Github. Git and Hugo both can be installed on my Mac mini to locally create content and generate a microblog from that. It a great experimentation place to learn and dig a bit deeper. Github is also a place to find new Hugo-based visual themes. Then I learned that I can import one of those themes on my machine so can change the visual appearance of my local Hugo microblog. Then, came the idea of publishing this content on the web, on Github, for free. To close the loop, services are available to take Github content and generate a static website, again using Hugo, behind a domain name of my choice. Then came the question: why do I need Microblog then? I could own the whole widget! It’s not that simple.

All this because I’m not satisfied with my current Micro.blog visual appearance. The next step is to dig within Micro.blog custom templates and see how I can update them. I’ll have to refresh my memory about HTML and learn a bit of CSS. The latter seems a bit an arid subject. Oh well.

Thought of the day for @manton and @jean: there is something that could be improved regarding micro.blog: opening up the evolution and improvement roadmap of the platform. I do appreciate when a service do put out their roadmaps so the community get a better look at where things will be going in the future. Mailbrew, Plausible and Craft are very vocal about their future plans, you just have to find the place where they talk about it.

So, where is Micro.blog heading? In particular, how do you plan to expand on themes support and customizability? Why the web editor doesn’t allow support for Grammarly? Do you plan an opt-in option to see how many followers a user have? Those are just a few questions that I have regarding Micro.blog future plans. Thanks in advance.

Greg Morris recently on his blog about trying hard as a blogger to make something out of all this:

“I asked, I’m giving, and I am still blogging — now more than ever.”

Strangely, pure coincidence I guess, I wrote this last week-end “The journey is the Reward” in which I said:

“It doesn’t really matter if nobody comes and reads my stuff here or there. What matters is the process and the thinking that took place behind my writing. It’s all the small moments where I had to pause, think, read, learn and write. It’s about feeling creative. Alive. The rest is just another tiny drop in the numeric ocean. A few will taste it, and most won’t. That’s the life of a blogger and a writer in a sea of abundance. So, I’ll keep doing it, no matter what.”

The journey is really the reward for me.