Spokenly

I came across spokenly via this YouTube video

At first I was reluctant to install it assuming that I will need to create yet another account just to use the app, but that was not the case.

They have two completely free options: First one where Whisper and Parakeet models are used locally. There are other models that can be run locally, but the size of these models keeps growing bigger and bigger.

This is one of those options you don’t know exists till you need it (or sometimes you don’t know even when you need it because you were too afraid to ask lazy to search)

When I started using mac almost a decade ago, I used the built-in screen capture shortcut. It works very well.

Initially I only knew about capturing the entire screen. I would then crop it to the desired area.

Then I learnt that I can select the screen area at the time of capture itself.

Neat!

If I want to add some markup - I would do that separately, after the image is captured.

Last time I wrote about my first experience using opencode, I was using (and learning) opencode CLI

This time, I switched to Zed editor.

Zed is so amazing that it can work with “Agents” installed on your machine (or it can install them for you) via ACP - Agent Control Protocol

It recognized that opencode was already installed on the machine, and show it in the drop down.

I decided to take it for spin.

Everyone is praising opencode - It is like Claude Code, or Codex (or Gemini CLI) except it is not tied to a corporation. It works with models from all of them, and other models, not from these corporations.

I had installed opencode long time ago, but never used it.

Today, I decided to give it a go.

As I was exploring, I came across /editor command. ¹ I had expected /editor command to open a file in an editor

I have been using Helix as an editor, not as an IDE. One of the USP of Helix is LSP support out of the box

Recently, I’ve been programming in rust.

Helix is also written in rust.

So I think it is natural that they would support rust LSP rust-analyzer and it does.

But I wasn’t getting auto completions 😞

After reading (not done) Steve’s Tutorial and Official doc ¹ (which mentions Steve’s tutorial anyway) I decided that actually using it on real projects is the way to go.

Here is the workflow (after a few ² iterations ³) that works

1. jj new : Declare your intention to start new work.
2. jj describe : Intention alone is not enough 😀. What will you be working on ?
3. Now work. Make changes.
4. Time to make our “change” available in git. Get the change id from jj log
5. jj bookmark set main -r <change_id_from_previous_step>
6. jj bookmark track main@origin (or appropriate branch on origin). You’ll need this step only once.
7. jj squash -i : Select the files that need to be “added” to the commit
8. jj git push --allow-new -b main --remote origin ⁴ Done!

Finally, I must say that I’m blown away (and humbled) by the fact that “The Steve Klabnik” who wrote the Jujutsu tutorial and the Rust book, helped me ⁵ (Near real time responses) with my problem.

I learnt about Jujutsu from the “Rust in Production” podcast episode about Git Butler

One of the attractive quality about it is that it works with existing git repos ¹

First superpower : Start using it with existing git repo locally cloned using jj git init --git-repo=. ²

This creates a .jj folder in the existing repo. .jj and .git co-exist peacefully

But I didn’t know that.

So for the first project to try Jujutsu, I jj git cloned my existing repo in a new folder, so that I have “old” git repo as well as jujutsu repo.

I wanted to use Openvibe - an app that allows having a single timeline across multiple social media networks like mastodon and bluesky. It also supports cross posting (and more)

But currently it only has mobile apps (for both iOS and Android)

While the Desktop app is “in the works” - no specifics are provided.

I do not use mobile apps if at all possible. (Except for podcast and messeging apps to keep in touch with Family - on the go. If I’m at my desk, I use the Desktop version)

I initially tried to turn off the type hints via rust-analyzer extension setting, but that did not work 😞

Turns out it is very complicated (at least for me) documentation did not help 😞

Here is what worked for me. Thanks to SO ¹

• Open Command Palette Cmd+Shift+P
• Select Preferences: Open User Settings (JSON) from the drop down
• Add the following to existing settings
  • Or create new one, if empty. You may need to enclose it within { } though.

	"editor.inlayHints.enabled": "offUnlessPressed"

This will turn off the type hint inlays.