Skip to content

b33p 0.2.0

Latest

Choose a tag to compare

@github-actions github-actions released this 20 Oct 11:53
· 554 commits to main since this release
34bd04a

The first release for others to try. Downloads for Linux (AppImage, .deb, tarball), macOS
(.dmg) and Windows (.zip), each for x86_64 and arm64; see the README for what each needs.

When something goes wrong

  • A failure at the start has a screen of its own that says what happened and what helps:
    Try again, Start over (deletes the messages stored here and links anew, after asking),
    or, when the system keyring is locked on the first start, Use a password instead. A
    keyring that isn't unlocked yet at login is tried again by itself.
  • "Forgot your password?" on the unlock screen, and Unlink this device in Settings.
  • Only a wrong password reads as one: data saved by a newer b33p, or one this build can't read,
    says so, and nothing suggests deleting it.
  • Linking again after the phone removed this device keeps the messages here, also when the
    history transfer fails or is cut off.
  • A second b33p can't open the same data (it would break decryption for both).
  • Error messages say what to do; the banner shows them whole.
  • The chat list says when Signal is out of reach, and while it catches up.

New

  • The device links as "b33p on ", and the name can be changed on the link
    screen and in Settings (it is used the next time this device is linked).
  • Settings → About: the version, the source code, the log folder and where to report a problem.
    b33p --version, --help.
  • A log file (logs/b33p.log in b33p's local data folder), with every line scrubbed of
    messages, names, numbers and IDs, so it can go with a bug report.
  • Select text in messages, and pick several messages to copy, forward or delete together.
  • Send a failed message again from its bubble.
  • Groups: set and remove the picture; invite links (show, copy, turn on or off, reset, approve
    requests); join a group from a link.
  • One start-up screen until the messages that came meanwhile are in.

Safer

  • Photos are sent without their EXIF and XMP data.
  • What senders send is treated as untrusted: only what Signal's own apps accept is taken, sync
    messages only from our own devices, and everything from blocked people is dropped, in groups
    too. Only a message's author can delete or edit it, and deleting for everyone erases its
    content.
  • Link previews only over https, to the internet.
  • Names, numbers and IDs stay out of the log.

Platforms

  • Linux builds run on Debian 12, Ubuntu 23.04, Fedora 38 and newer (they needed Ubuntu 24.04's
    libraries before). The AppImage follows the GTK theme on GNOME and Xfce.
  • Windows: the program has its icon and version; notifications show the icon;
    b33p.exe --unregister removes its registry entries before deleting it. The zip explains
    SmartScreen.
  • macOS: the shortcuts are labelled with ⌘, ⌥ and ⇧, and the notification settings, which
    don't work there yet, are gone.

Known limits

  • macOS has no notifications yet, and its builds aren't notarized (see the README).
  • Renaming a device that is already linked waits for the next link.
  • Calls and payments are out of scope.
  • See PLAN.md for what is still missing.

What's Changed

  • Make ui.rs a module and drop the one-implementation Ui trait by @barafael in #15
  • Read and write the binary ACI fields current Signal apps use by @barafael in #16
  • Treat what senders send as untrusted by @barafael in #17
  • Keep private what should stay private by @barafael in #18
  • Read every unread message, not just those after a mark by @barafael in #19
  • Keep the message rows in line with the messages by @barafael in #20
  • UI fixes from the review by @barafael in #21
  • Tidy up after the review by @barafael in #22
  • Settle what is read before receiving, and hold receipts until the phone's settings are in by @barafael in #24
  • Keep receiving whatever arrives, and stop losing messages to a locked database by @barafael in #23
  • Select text and messages, link bare host names, scrub the log by @barafael in #26
  • Erase content on delete-for-everyone by @felintusun in #25
  • Begin the deletion transaction immediately, like the others by @barafael in #32
  • Add a dev container with the Linux build dependencies by @felintusun in #28
  • Harden link previews and message requests by @felintusun in #29
  • Resolve quote text from the stored original by @felintusun in #30
  • CI: fmt, clippy, tests, cargo-deny, zizmor; pin release actions by @felintusun in #27
  • Name the exact tag the install-action pin is by @barafael in #33
  • An agent harness: drive the window over a socket, and a README with screenshots by @barafael in #34
  • Mock compiles for windows by @maxfunke in #35
  • Scrub errors and paths for PII before they reach the log by @maxfunke in #36
  • test: close db file for windows on test cleanup by @maxfunke in #37
  • Pin the forks with websocket errors that name their cause by @barafael in #38
  • A screen for what stops b33p, and ways out of it by @barafael in #39
  • Keep the store readable across versions by @barafael in #40
  • Device name, connection state, About, and a log file by @barafael in #41
  • Builds that run on more systems (Debian 12, Windows icon, macOS) by @barafael in #42
  • Release notes, install notes, and checks for 0.2.0 by @barafael in #43
  • Note what a web demo of the mock would take by @barafael in #44
  • Run the container jobs' steps with bash by @barafael in #45

New Contributors

Full Changelog: v0.1.0...v0.2.0