Today, I picked up my Jolla phone, after more weeks of checking tracking apps much more often than I care to admit.

This will be very unsorted, but I want to try and keep track of how my impressions evolve.

So far, I have played around with what comes in the box (plus the Jolla apps they suggested installing when I logged into my account) and a single third-party app: the Mastodon app Tooter.

It feels … like a fresh blast from the past. When phones were a bit more different from each other. Things were still being figured out.

A while back, it struck me as I was using my max-sixed Iphone that I was missing just having a phone with a different feel in the hand.

The Jolla delivers that difference in a great way. Because it is mainly plastic rather than metal and glass, it feels warmer and friendlier to the touch. Side by side with my Iphone, they are surprisingly close in all dimensions, but the Jolla somehow feels a lot nimbler to hold. I guess that comes down to the weight difference, while the dimensions are very close the Jolla is 32 grams lighter (208 versus 240).

It does not feel premium the way a brand new Iphone or Samsung device does. I would say it feels … approachable. And durable. The back cover is meant to come off, just a thing like that! I bought a protective cover, but I am not sure I will use it much when the hand feel is this nice and there is no dumb glass on the back to crack.

The whole interface of Sailfish OS is also nicely different. A lot of stuff can be done using swipes anywhere on the screen, which is great. The first time after I had got the hang of back and forward swipes and a button needed tapping in the top right of the screen, I almost felt frustrated at having to move a finger up there. One gesture I really like but that also takes some getting used to is being able to pull down in apps to drag down a menu of actions from the top of the screen. You just keep dragging to select the option you want and activate it when you lift your finger. A bit of evolution over pull to refresh, but it also requires a bit more precision. I have activated things by mistake when I intended to just scroll.

The keyboard and autocomplete/suggestions feel better than on Iphone. It has much saner suggestions, fits more of them on screen, and I feel a little bit more accurate without being able to explain why. It has only been a day, so it will be fun to see how my impression evolves.

Oh, and speaking of text: Remember cutting and pasting? On Ios, you select text, then awkwardly tap and hold to get a menu up to select copy from, sometimes getting out of sync with it popping up and stuff? Then find a place to paste and repeat the tap and hold to get the paste menu option without accidentally selecting anything.

Jolla gives you a copy button on the keyboard when you have text selected. Tap it again to paste. So straightforward everyone should steal it, yesterday.

This is my first experience of a phone with a fingerprint-reading power button. The button is perhaps best placed for your thumb if you hold the phone in your right hand, but adding more fingers lets left-handed unlocking work just fine too.

The first banner I saw when I opened Jolla's own app store was for a tracker app. It did not attempt to sell me smurf berries.

Initial setup was very quick. Set up unlocking and encryption, optional login and app downloads (pragmatically including Android app support stuff) which I did, and then a quick introduction to the swipe-based workings of Sailfish OS.

I have not figured out my needs yet. I have not installed Bankid and other necessities for daily driving a phone. I have not figured out how I want to get text and images and other stuff between it and the rest of my technology life. I have no idea if an how much I will try to use it as my full-time phone.

I have not, in fact, even put a SIM card in yet.

In other words: so much exciting stuff left to figure out. I can not wait to see what I do with it!

Writing is at least as fun as programming.

After writing the last post, I felt a part was missing.

What I wanted to underscore from the start - and somehow lost while explaining the background - was how interesting it is to be moving toward the line of understanding.

How everything feels uncertain and risky, and even though you believe you are approaching the line you have little idea of how close or far you are, and whether you are approaching in the best way.

And then, you suddenly find yourself on the other side of the line, relieved and excited and already somewhat unable to understand what was so difficult in the first place.

(Resolve's manual is a PDF of 4444 pages, by the way.)

Several times over the past year, I have been encouraged to learn the video and audio editor (IDE? IME? Integrated media editor?) Davinci Resolve. After stewing on a particularly powerful pitch from Harald Achitz after the recording of Kodsnack 703, I eventually got around to downloading the whole package. It took me a while longer to read up on features, and finally decide to buy the studio version before I actually got around to learning to do anything.

Why so many steps before starting? I had a very particular target in mind: being able to ditch Descript for creating clips of Kodsnack. Descript is a completely web-based editor as a service. It keeps creeping up in monthly cost, sometimes forcing me to update, sometimes leaving me behind with fewer features as it goes.

(Oh, and they are AI everything, around every corner, and want you to pay for tokens.)

I do very simple things with my clips, but the one feature I needed and required to be reasonably simple was the creation of captions. I want my clips to have captions moving along with the speech, and that is nothing I want to create by hand.

In Resolve, this turned out to be nice and simple, once you found it. Resolve decided to bundle transcription and caption creation under "AI" features and only enable it in the for-pay studio version. Happily, the studio is a prodly advertised one-time purchase, and a quite affordable one at that. So this is why I did not start actually editing anything before buying.

Studio installed, it was time to set off! Starting to fumble around in Resolve felt … strange and awkward in a good way, if that makes any sense. It was a long time since I felt so lost in a new app, but it felt great to be figuring out something which is completely made for professional use. Things may not be easy to find, but everything is set up with the goal of being efficient.

As usual when learning something new, it felt very intimidating and slow at first. I made very strange mistakes, the kind which feel completely baffling as they happen. The kind you stop making after learning just a little bit more. And once you have done that little bit of learning, it becomes hard to understand what you even did wrong in the first place.

The key for me was watching a few videos, first a general walkthrough of pretty much the whole app, then a few on specific topics as they came up. I found a video specifically on creating clips for Tiktok which really clicked for me. It both answered the main questions I had at the moment, and showed me a bunch of power user setup. Got to love a fifteen-minute video which still spends a minute or two at the start showing you how to set up some useful keyboard shortcuts.

Somewhere soon after watching that video, I stumbled out of the forest of total confusion and into the plain of things starting to make sense. I have created my first clip which looks and feels the way I want it, and I know the steps I want to do and their order so that it feels repeatable. From here, it is just a matter of building habit and speed, and adding new knowledge if and when I want it. There is a whole universe of extra things to learn, and I am excited about the thought of possibly having my own library of effects and setups and things.

We will see where it goes from here, but the initial stage of confusion is definitely over.

(I can leave Descript behind for editing, but annoyingly they also provide the recording solution I use at the moment. They are in the process of enshittifying that, too, so my motivation is high, I just need to figure out to what first …)

I decided to not read a book.

It may not be a first for me, but it is definitely much too rare that I actively decide to stop reading a book. I can leave them around for a long time, sometimes eventually giving up on them. But the giving up is very rare, and a light sense of guilt that I should be finishing them is very easy to awaken.

I am therefore happy to report that I am not finishing Ken Follet's Never. I started it with some hesitation. I know that I can enjoy his writing quite a bit, but I also realized rather quickly that he is such a bastard to his characters. In a medieval story where the plague plays a part, do we really need a detailed description of someone being flayed alive? (If I recally correctly, it was also a total side note to the whole rest of the story.) How much rape do we strictly need to make the story come alive? Does every evil character have to get away with all their bad deeds all the way to the end?

I am not sure why exactly I started to see Follet as the evil puppet master when I have never thought of any other author like that. Perhaps I liked some of the good characters too much? Perhaps starting stories with literally putting someone's feet to the fire and randomly killing somebody's puppy was choosing to start uphill?

Or perhaps I have simply had enough of all the dumb evil shit idiots all over the world get away with daily? I do not mind if my fiction includes a bit more of the wrath of the heavens descending on evil-doers than does the flow of news.

I chose to stop Never when I realized how likely a horrible story of human trafficking centered around a woman and her child were to play a central part of the story.

Sorry Ken, I do not feel like bracing myself before my evening reading right now.

(The annoying part is that I am pretty interested in the bigger story of the book. Oh well.)