muxile VS asyncgo

I have plenty of ultra niche projects and I never regretted working on any of them. On the contrary - i use them daily and it brings me much joy. Here are three:

https://github.com/bjesus/muxile lets me continue my tmux session on the phone, bridging the two over WebSockets. How many people use tmux extensively AND want to continue on the phone? Not much i guess...

https://github.com/bjesus/callibella is my way to sync my personal calendar to my work calendar without revealing my personal entries. It's very useful for me but less needed if your personal calendar is Google because i heard they have their own integration.

https://github.com/bjesus/air is my AwesomeWM based Interface to my PostmarketOS Kobo e-reader. Linux on your e-reader isn't a huge market share to begin with...

Love mosh, back when the connection was bad I had it aliased to ssh. Somewhat relevant: if you actually a need to take your shell mobile, check out my tmux plugin that allows you to quickly transfer your tmux session to your phone without any app, using websockets and a QR code: https://github.com/bjesus/muxile

I built something similar. It didn’t really work as a business (or at least I wasn’t able to make it work) so I open sourced it: https://github.com/async-go/asyncgo

If there’s anything useful there feel free to scavenge, or if you’d like to talk about what I learned trying to build it let me know.

I made an async work collaboration app: https://github.com/async-go/asyncgo

I had been working at GitLab, pre-pandemic, for several years and I saw how writing things down was almost like a super power to enable async work. If you start with time zone distributed teams, writing things down in issues/docs just becomes the natural way of working. I also saw that lots of companies didn't really get it - and there was a leap of faith required to try it, because it didn't logically follow that if you write things down more you can have less meetings.

My idea was to build something that provided a really natural place to write things down, and I built and tried to sell AsyncGo as a place for making decisions in a written way. You'd set a topic, a context, and a due date, and then the magic would happen. In theory. The problem I had was that I couldn't find anyone to take the leap and try it. Companies who were interested in async already had some similar process, and the ones who needed it didn't get it and I never found a way to communicate it clearly.

In the end I shut down the hosted version and put an MIT license on it. I don't regret it exactly, I learned a lot making it, but I wish it had helped more people. There's other stuff out there now that's sort of similar, and it seems they are struggling a bit as well, so I don't think the market was really there (yet).