Every test so far ran on a profile with nine accounts and months of history. The first five minutes of a new user's moho have not been seen since early on:
first launch with no accounts: what the window says, and whether adding the first account is obvious
each protocol's add-account flow from nothing, including Tor for Sneedchat
empty states: no buffers, no friends, no history, no events
the Windows installer on the VM, start to finish, and the AppImage on a distribution that is not this one
Run it with a fresh HOME (or a VM) and file what is rough.
Every test so far ran on a profile with nine accounts and months of history. The first five minutes of a new user's moho have not been seen since early on:
- first launch with no accounts: what the window says, and whether adding the first account is obvious
- each protocol's add-account flow from nothing, including Tor for Sneedchat
- empty states: no buffers, no friends, no history, no events
- the Windows installer on the VM, start to finish, and the AppImage on a distribution that is not this one
Run it with a fresh HOME (or a VM) and file what is rough.
Salastil
added this to the v1.0 milestone 2026-10-02 00:00:01 -04:00
Finished. I walked through a clean install on the Windows VM, using the released installer (moho-117bbc0) on a fresh profile.
Fixed:
A new account's rail entry and first conversations didn't appear until a restart. Account groups are never announced, so the window now asks for the rail again when a conversation names a group it doesn't know, when a new account appears, and after a removal (the removed account's entry also used to stay behind).
Kick's "Just watch" and adding an IRC network left the user on "Select a server on the left", with nothing on the left. Both now go straight to the account's join page.
Joining from the join page stayed on the form. The joined conversation now opens (Kick handles in any form, IRC channels and nicks).
A signed-out Kick viewer was offered a message box. It now says it's watching signed out, with a Sign in button.
Disconnect and Remove showed an error toast saying "cancelled".
The welcome text named "nobilis".
Kick over Tor: the HTTP client was built before Tor started and kept a dead-end route for the whole session, so every channel lookup failed instantly and silently. The route is now started first, the router no longer caches dead-end clients, and a failed join now reports its reason. (Kick's API answers Tor with 403, so watching Kick over Tor still can't work, but it now says so.)
Tor on Windows after the arti 0.47 update: Tor started in 7 s on a fresh profile, connections went through it, and the daemon sits at 0 percent CPU, so the Windows hang fix still holds.
Filed:#258 (uninstall leaves saved sign-ins), #259 (Matrix says matrix.org takes no new accounts), #260 (Kick header at small widths), #261 (Remove account has no confirmation), #262 (installer and wording polish), #263 (an IRC server's reason for hanging up is hidden).
Not done: the AppImage on a distribution other than Arch.
Finished. I walked through a clean install on the Windows VM, using the released installer (moho-117bbc0) on a fresh profile.
**Fixed:**
- A new account's rail entry and first conversations didn't appear until a restart. Account groups are never announced, so the window now asks for the rail again when a conversation names a group it doesn't know, when a new account appears, and after a removal (the removed account's entry also used to stay behind).
- Kick's "Just watch" and adding an IRC network left the user on "Select a server on the left", with nothing on the left. Both now go straight to the account's join page.
- Joining from the join page stayed on the form. The joined conversation now opens (Kick handles in any form, IRC channels and nicks).
- A signed-out Kick viewer was offered a message box. It now says it's watching signed out, with a Sign in button.
- Disconnect and Remove showed an error toast saying "cancelled".
- The welcome text named "nobilis".
- Kick over Tor: the HTTP client was built before Tor started and kept a dead-end route for the whole session, so every channel lookup failed instantly and silently. The route is now started first, the router no longer caches dead-end clients, and a failed join now reports its reason. (Kick's API answers Tor with 403, so watching Kick over Tor still can't work, but it now says so.)
**Tor on Windows after the arti 0.47 update:** Tor started in 7 s on a fresh profile, connections went through it, and the daemon sits at 0 percent CPU, so the Windows hang fix still holds.
**Filed:** #258 (uninstall leaves saved sign-ins), #259 (Matrix says matrix.org takes no new accounts), #260 (Kick header at small widths), #261 (Remove account has no confirmation), #262 (installer and wording polish), #263 (an IRC server's reason for hanging up is hidden).
Not done: the AppImage on a distribution other than Arch.
- moho: https://git.salastil.com/Salastil/moho/commit/e207224
- moho: https://git.salastil.com/Salastil/moho/commit/cfd91bc
- nobilis: https://git.salastil.com/Salastil/nobilis/commit/8bcba8b
- nobilis: https://git.salastil.com/Salastil/nobilis/commit/5755c4e
Finished. The last item was the AppImage on a distribution other than Arch.
I ran the released moho-117bbc0.AppImage in containers, on a virtual display, as a fresh user:
Ubuntu 22.04 (glibc 2.35): the window opens on the first-run Add an account screen and the daemon comes up (listening on …/nobilis.sock). The released daemon needs at most GLIBC_2.34, under 22.04's floor.
Fedora 44 (glibc 2.43): the same.
The containers can't use Chromium's sandbox or FUSE, so these runs used --no-sandbox and extract-and-run, and their D-Bus warnings are just the missing session bus. A real desktop has all three.
Everything else from the walkthrough was fixed or filed as #258–#264, all handled since (#262 has one cosmetic item left).
Finished. The last item was the AppImage on a distribution other than Arch.
I ran the released `moho-117bbc0.AppImage` in containers, on a virtual display, as a fresh user:
- **Ubuntu 22.04** (glibc 2.35): the window opens on the first-run Add an account screen and the daemon comes up (`listening on …/nobilis.sock`). The released daemon needs at most GLIBC_2.34, under 22.04's floor.
- **Fedora 44** (glibc 2.43): the same.
The containers can't use Chromium's sandbox or FUSE, so these runs used `--no-sandbox` and extract-and-run, and their D-Bus warnings are just the missing session bus. A real desktop has all three.
Everything else from the walkthrough was fixed or filed as #258–#264, all handled since (#262 has one cosmetic item left).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Every test so far ran on a profile with nine accounts and months of history. The first five minutes of a new user's moho have not been seen since early on:
Run it with a fresh HOME (or a VM) and file what is rough.
Finished. I walked through a clean install on the Windows VM, using the released installer (moho-117bbc0) on a fresh profile.
Fixed:
Tor on Windows after the arti 0.47 update: Tor started in 7 s on a fresh profile, connections went through it, and the daemon sits at 0 percent CPU, so the Windows hang fix still holds.
Filed: #258 (uninstall leaves saved sign-ins), #259 (Matrix says matrix.org takes no new accounts), #260 (Kick header at small widths), #261 (Remove account has no confirmation), #262 (installer and wording polish), #263 (an IRC server's reason for hanging up is hidden).
Not done: the AppImage on a distribution other than Arch.
Finished. The last item was the AppImage on a distribution other than Arch.
I ran the released
moho-117bbc0.AppImagein containers, on a virtual display, as a fresh user:listening on …/nobilis.sock). The released daemon needs at most GLIBC_2.34, under 22.04's floor.The containers can't use Chromium's sandbox or FUSE, so these runs used
--no-sandboxand extract-and-run, and their D-Bus warnings are just the missing session bus. A real desktop has all three.Everything else from the walkthrough was fixed or filed as #258–#264, all handled since (#262 has one cosmetic item left).