Jekyll2026-07-13T17:37:40-07:00https://wlair.us.to/feed/by_tag/rant.xmlxoddf2’s Blogxoddf2's personal blogxoddf2Back to Irssi2021-10-28T07:58:00-07:002021-10-28T07:58:00-07:00https://wlair.us.to/blog/2021/10/28/back-to-irssiFor several years, I used Irssi in tmux on a shell server. A few months ago, I started using Circe as my IRC client (connected to a ZNC bouncer) after a brief stint with ERC. Circe had various issues:

  • Basic features, such as the display of my current nick, current channel modes, and /LIST, were not implemented.
  • The tab completion omitted the colon after the nick, even with circe-completion-suffix set to the default : . It also occasionally gave odd tab completion suggestions based on obscure substrings.
  • The currently focused channel(s) still appeared in the tracker regardless of lui-track-behavior’s value.
  • Even with circe-lagmon-mode, Circe did not reconnect to my bouncer after losing the network connection.
  • circe-lagmon-mode did not work with some servers.
  • circe-lagmon-mode would cause Circe to spam “*** User away: <current nick>” when I was set as away, at least with multiple instances of Circe running.
  • Circe would set my away message to my nick instead of what I typed as an argument to /[G]AWAY.
  • The topic was not always visible à la Irssi, WeeChat, or ERC’s top bar. I would rather not type /TOPIC constantly.
  • WHOIS output would appear in random buffers.

Early this month, I switched back to Irssi (with ZNC this time) after getting tired of Circe’s bugs. With multiple clients at least, it is not as good as bare Irssi in a terminal multiplexer, but it works better than Circe did.

]]>xoddf2I Feel Slower Now2019-01-09T19:46:00-08:002019-01-09T19:46:00-08:00https://wlair.us.to/blog/2019/01/09/i-feel-slower-nowDuring the first week of 2019, nomad ran OpenBSD 6.4. Here is how that went:

The good: Unlike under FreeBSD 10.3 a few years earlier, hardware support was better. The Wi-Fi signal strength thing turned out to be i3status not supporting %quality under the BSDs. 5 GHz worked fine. Suspension and hibernation worked well. OpenBSD also does not have the headphone jack switching issue that FreeBSD has.

The bad: Performance was unacceptably slow. If audio and/or video was playing, loading a Web page, even a simple one, in Chromium would cause the audio to stutter. Swapping would occur when memory usage reached roughly 1.5 GB (nomad has 3 GB) despite adding my user account to staff and adjusting staff’s resource limits in /etc/login.conf. It would avoid the rest of the RAM as if it were poison or something. Wi-Fi was about half the speed it was under GNU/Linux for some reason. Also, some Web sites, such as Twitch streams (mpv + youtube-dl worked fine, though) and Internet Archive’s JavaScript implementation of MAME, would not work in either Chromium (with sandboxing) or Firefox.

I have reverted to Debian GNU/Linux in the meantime. OpenBSD mostly worked, and I would have stayed with it, if not for the above issue.

]]>xoddf2