junkie 0.2.1

A temporary room now tells you it's temporary, instead of implying you mistyped the code.

Reaching for a /f/{code} room from the terminal used to fail three different ways, and every one of them blamed the code you typed:

$ junkie EDCAF7-E63221
error: you're not in EDCAF7-E63221

$ junkie room join EDCAF7-E63221
error: no room joined — is EDCAF7-E63221 the right code?

The code was right. It failed that way for the room's creator too. All three paths now say what is actually going on:

$ junkie EDCAF7-E63221
error: EDCAF7-E63221 is a temporary room, and the terminal can't open one yet —
use it in a browser at /f/EDCAF7-E63221. Following along here is issue #3

Opening temporary rooms from the terminal still isn't supported — that's #3, where what "supported" should mean is still an open question. This release only stops the error from sending you off to re-check a code that was never wrong.

A room you are simply not a member of keeps its own message, and a lookup that fails is not guessed at either way.

Also

• junkie watch CODE is gone from the documentation. There is no such command — it became the desk's w zoom a while ago, and the docs page had inherited the claim from a stale note rather than from the code.

Note on v0.2.0 — its release notes mentioned this fix, but the change landed one commit after that tag was cut, so it was never in the v0.2.0 binaries. It is in these.

Install

curl -fsSL https://raw.githubusercontent.com/samnodier/junkie/master/install.sh | sh

Puts a junkie binary in ~/.local/bin (set JUNKIE_INSTALL_DIR to choose elsewhere) and verifies it against checksums.txt below. Re-running the same command upgrades in place. Works on macOS and on any Linux distribution, WSL included — the binaries are static, so there is no glibc requirement.

On Windows, download junkie_windows_amd64.zip and put junkie.exe on your PATH.