Blog
Thoughts on software engineering, technology, and beyond
Posts cover software engineering, technology, and whatever else catches my interest. This is a journal of personal experiences and evolving thoughts — not ground truth. I may change my mind over time and posts may not always reflect that.
There is a gap in the OAuth 2.0 ecosystem that almost every team with a native mobile app eventually falls into. It does not have a widely agreed-upon name. It is not covered by any RFC. And yet, once you hit it, you quickly realize that everyone else has hit it too, and solved it differently.
The problem: your native app has a perfectly valid session. The user is logged in. Now you want to open a piece of web content (a WebView, an in-app browser tab) and have the user land there already authenticated. No second login screen. No friction.
I’m pretty sure, I’m not the only one working in multiple git contexts with multiple authors.
Maybe you also find yourself in situations where you need to juggle with multiple author configs, including:
- Work
- Private
- Anonymous
- and others…
I found myself multiple times already in situations where I’ve created a commit with my author set from work and vice versa.
After countless errors, I finally found a way to manage this issue at my scale and I’m pretty happy with the solution.
In this post I will explain how I’m using the Windows OpenSSH and Gpg4Win agents inside WSL2 with systemd.
This post is not explained in detail and serves mainly as a reference manual for future setups.
There are also other tools available in the wild, that help with the process, like:
Download npiperelay and wsl-ssh-pageant.
Place both in a suitable directory on the windows side. I created C:\tools for that purpose.
Configure wsl-ssh-pageant for autostart. I chose a simple shortcut in the startup directory for that.
It should be started like this: wsl-ssh-pageant-amd64-gui.exe -force -systray -verbose -wsl C:\tools\wsl-ssh-pageant\wsl-ssh-agent.sock -winssh winssh-pageant
I’ve measured the power draw of my computer and noticed that it only demands about 35W in idle and about 100W if doing CPU-heavy work
The JEE/Spring @Transactional Annotation in Kotlin behaves unintuitively when exceptions are thrown and does not rollback by default
Why twobiers?
Setting upper bounds for failures instead of success goals might improve your mindset