After seeing this post by Chris Hannah:

It’s incredible to see the effect of the various recent changes on how the “blue checkmarks” are given out and what they seemingly represent to different demographics of people.

Here’s my take on this. It’s straightforward: you don’t need to be verified by Twitter (or any of these centralizing platforms) to feel that you exist, are relevant and be fabulous! Just be. If you’re uncomfortable with recently introduced changes at Twitter, move on elsewhere. That is all.

I’m fed up with these stories about Twitter removing previously verified check marks! This is stupid. It was bound to bound to fail from the start. Now, here we are. It failed. Look ahead.

Matt, the founder of the WriteFreely ecosystem, recently wrote a promising post:

It’s become clear over time that in order to make WriteFreely (and Write.as) as useful as it can be, it needs to have a much more unified experience.

…

I don’t think it makes sense for our self-hosted product to be chopped up into multiple components like our hosted tools are. Instead, I want to bring all those tools into a single application in WriteFreely.

Earlier this year, I wrote an article (“The Write.freely Ecosystem Explained”) trying to explain the WriteFreely ecosystem because I thought that, in its current form, it was a bit hard to grasp. It’s one of my most popular posts on Write.as. I think there is a need for unification and consolidation into a seamless experience. I’m glad the see that it’s coming.

In my Friday Notes edition #102, I shared my thoughts about my last four months without Twitter and how calm and quiet my digital life has become. I even wrote that I might ignore Bluesky. But that was last week.

Well, it didn’t take long to contradict myself! As you might have guessed, I’m now on Bluesky as @numericcitizen (of course), thanks to a generous donator of an invite link (looking at you @Maique).

Please make no mistake; it’s an experiment. I’m not planning to spend too much time on Bluesky, but I’m genuinely curious about its evolution and the traction it gets, if any.

I’m allowing myself to get on board for a simple reason: Manton from Micro.blog added support for cross-posting content to Bluesky. It didn’t take long. For me, it’s like getting a seal of approval from him. I highly value his opinion on Bluesky and the open web in general. So, I made the jump without really knowing what to do next except to enable the cross-posting of my content posted on MB.

Now, I wish Bluesky doesn’t get filled up with too many dark clouds. My fingers are crossed.

PS. I’m curious how Micro.blog will push that post onto the Bluesky universe. See you on the other side.

PPS. I’m gathering my thoughts and observations for an upcoming experiment status report. Stay tuned.

Today, I unexpectedly came across this announcement from Micro.blog: Highlights are now synced to Readwise.io, provided that you have an account with them and that you are on an Micro.blog Premium plan! How cool is that!

I immediately configured my Readwise.io connection in the Bookmarks section and exported past highlights in a CSV file. Next, I tried the feature on an article from MacRumors.

After a few minutes, I could read the archived version of the article and highlight some portions. And sure enough, my highlights were saved to Readwise.io in a snap.

The nice thing is that Inoreader also supports saving my highlights to Readwise.io. Everything going at the same place. Occasionally, I export and then import my highlights into Craft. Readwise remembers the point of my last export session.

As reported by the Wall Street Journal (since it’s paywalled, look at MacRumors report instead), Apple is supposedly working on its own journaling application. Code named « Jurassic », many interesting details are emerging from this report.

As an avid user of Dayone (read « Documenting My Numeric Life With Dayone »). , I find the prospect of having Apple entering the journaling apps landscape quite exciting. The idea of using journaling to help users with mental health issues is pretty clever. There is so much information available on our devices from which, I guess, we can infer some mental states. I’m guessing machine learning can be of some tremendous help here. Coupled with Apple’s stance on privacy, this provides a potentially very compelling story for a lot of people. Me included. Yet, some people could find this move to be crossing a line that is not acceptable for them. We will see.

The WSJ story is referring to very specific detailed aspects of the rumoured app. For example, journaling suggestions would be based on call history and iMessage conversations, and be ephemeral. After four week they would vanish from suggestions. I’m guessing this would help automate some aspects of daily journaling.

I asked this question to ChatGPT: « _Is the young generation into journal as much as older generations? _». Here is what it has to say:

_ There is no definitive answer to this question, as attitudes towards journaling can vary widely among individuals of all ages. However, some studies suggest that younger generations may be more likely to engage in forms of expressive writing such as blogging or social media updates, which could be seen as a form of journaling._

The debate might still be out if the youngsters generation is very into the writing journey, but having some part of the journaling automated would alleviate some rebarbative aspects of maintaining a journal.

Can you imagine having the journal app assembling photos, messages, phone calls, geo locations into pre populated journaling suggestions? Wow. I’m really looking forward into that one.

I was looking for inspiration all week to write my next Friday Notes edition. Early morning yesterday, I was still unsure if I could make it, but at lunchtime, I tried ChatGPT with “Give me some blog post ideas about the positive effects on creativity of going on vacation for a week”. It came back with phrases that looked taken from a travel agency ad. I tried again with different variations of my question. It failed to impress and to inspire me. I’ll pass this week’s edition.

I’ve been working on this for a while and now I feel it’s time to share with the world. Follow this link, then expand each question to read the answer. It was a lot of fun to put together.

This site is going to be updated as new micro-workflows are documented or tweaked. This document is now joining my Complete Content Creator Toolset.

If you have a question, feel free to ask, using the commenting feature of the website as shown below. I welcomed suggestions for workflow improvements too! Enjoy and I hope you learn a few things along the way or that it triggers some ideas for your own workflows!

🚨 This is post #2000. I have already written more posts in 2023 than for the entire year last year. I’ll probably write more than 2021. The record year, 2020, will be hard to beat. This post was written using Ulysses on my MacBook Air which is the most used device, with 73%. My Mac mini comes second with 20%, and lastly, my iPad with 7%. I love numbers. Returning to normal programming.📺

After reading Gruber’s article about Wavelength, I decided to try it. I’m not sure I require another messaging solution. Besides using Apple’s iMessage and Telegram to get news from Ukraine, the rest of my messaging app usage is anecdotic.

So, what are my thoughts about this? The initial few moments with Wavelength are not what I call an honest onboarding experience. Well, I already shared my surprise at having to enter my phone number at the very first step of the application onboarding. I thought it was brutal. I was quickly reminded that asking for our phone number is the usual thing to ask in a messaging app. M’ok. 🤨 But hey, Wavelength is still in beta, right? So, let’s give them a break.

So I created a group called Microbloggers (invite link) for hosting people coming from Micro.blog (well, anyone with the link can join). As I’m writing this, there are 25 members. I’m surprised. I wasn’t expecting that many people to join. I guess my Micro.blog circle is made of very curious people. I love this. Is @Manton joining? Nope. But @Jean is among the participant, which I find cool!

My general feeling with the application is that its design reminds me of Micro.blog’s simplicity. Wavelength is simple but not simplistic. I love it very much. I’m using Wavelength mainly on the Mac, but also on the iPhone. I prefer the Mac experience. But, again, Wavelength is not complete. I’m looking forward to watching its future evolution.

An interesting byproduct of Wavelength is the inclusion of a ChatGPT client inside. It’s the group called “AI”. We can interact with it at any given time, even include this “guy” in a conversation within a group, using the @AI in a message. Each request to the AI entity is kept as an individual conversation (except the one occurring within a group conversation). It’s fun, valuable and fascinating at the same time.

But now, the big question: why would someone of Micro.blog starts using Wavelength and participates in a group chat? Conversations are already happening on Micro.blog. Just like on Micro.blog, if you are a member of a Wavelength group, conversations are public. I’m still pondering this. I understand people who are also wondering about the usefulness of having Wavelength alongside the Micro.blog. Maybe the instant nature of such messaging platform is something missing on Micro.blog? This is something I liked on Twitter: this ability to enter a private conversation with one of your followers.

Well, that’s it for now.

You can join the “Microbloggers” Wavelength group with this invite link. I plan to leave the group open as long as my experiment with Wavelength lasts.

One last thing: after launching the app for the first time, this wave animation is mesmerizing.

Another thing: my avatar photo is me at 5. 😊

From the Numeric Citizen Blog

to the Numeric Citizen Space.

The former was my WordPress site, now on Ghost and merged with what used to be the Numeric Citizen Introspection, the home for my Friday Notes Series newsletter. It took me a while, but here I am. I’m so relieved from not having to use WordPress anymore. I have learned quite a bit about WordPress since 2015, but my desire to simplify my digital life was pressing me to make some changes.

From now on, in Ulysses, I got two places to push my articles, here or Ghost. That’s it.

Both are under the same domain name, which is something that I wanted for a while. Now, I hope to spend more time writing than moving things around. I will publish my migration process in the upcoming days on my Numeric Citizen I/O, my metablog.

From a design perspective, I’m using Ghost’s Casper default theme, which is relatively close to what I was using on WordPress. I’m ok with this for the moment. I may hunt for alternatives in the future, but for now, that will be it.

Now, returning to normal programming.