Jump to content

Dino: Difference between revisions

From postmarketOS Wiki
m Installation: use <syntaxhighlight>
Unah (talk | contribs)
m Removed outdated note
Line 1: Line 1:
{{note|The mobile fork of Dino referenced below will be added in {{MR|1754|pmaports}}, which as of writing is not merged yet.}}
= Dino on postmarketOS =
= Dino on postmarketOS =
Dino is a new, modern Jabber/XMPP Client using GTK+/Vala, with support for OTR and OMEMO end-to-end encryption, file transfers, and MUCs. The version in postmarketOS is currently an experimental work-in-progress branch that implements a mobile-friendly UI using libhandy.
Dino is a new, modern Jabber/XMPP Client using GTK+/Vala, with support for OTR and OMEMO end-to-end encryption, file transfers, and MUCs. The version in postmarketOS is currently an experimental work-in-progress branch that implements a mobile-friendly UI using libhandy.

Revision as of 21:07, 19 January 2021

Dino on postmarketOS

Dino is a new, modern Jabber/XMPP Client using GTK+/Vala, with support for OTR and OMEMO end-to-end encryption, file transfers, and MUCs. The version in postmarketOS is currently an experimental work-in-progress branch that implements a mobile-friendly UI using libhandy.

Installation

Dino is in the postmarketOS pmaports repository, and can be installed with:

$ sudo apk add dino

Known issues

  • Not all UI elements are adaptive yet (e.g., the 'settings' window displays some items off-screen)
  • The libhandy patches might not work well on desktop resolutions

There's an open issue in the upstream project here with the current status: https://github.com/dino/dino/issues/178

How to help

postmarketOS includes Dino built from the feature/handy branch, found here: https://github.com/dino/dino/tree/feature/handy Contributions to improve the UI, using libhandy, can be made by submitting a merge request to the upstream Dino project. When submitting the merge request, select the feature/handy branch as the target.

Which server should I choose?

See this page for information about compliance with modern XMPP extensions: https://conversations.im/compliance/