Blog - Dino. Communicating happiness.

All posts published on Dino Blog Page 1 of 2

Fri Nov 6, 2020 · 4 min read · by fiaxh, Marvin W. Release

Dino 0.2 Release

Mexican Caribbean Coral Reefs

Dino is a secure and open-source messaging application. It uses the XMPP (Jabber) protocol for decentralized communication. We aim to provide an intuitive, clean and modern user interface. The 0.2 release adds message correction, improves the file upload functionality and provides more information about message encryption.

Tue Aug 11, 2020 · 1 min read · by fiaxh, Marvin W. Developer update

Setting out for calls and conferences

Video calls have become a widely used means of communication in personal and in business settings. Especially during the last months, people increasingly used video calls to keep in touch. Unfortunately, many turn to US-based, centralized and closed-source solutions that come with privacy and security issues.

Wed Jan 29, 2020 · 4 min read · by fiaxh, Marvin W. Release

Dino 0.1 Release

We are thrilled to announce the first release of Dino: Version 0.1. This marks an important milestone of the development process that started three years ago and already combined work of 30 contributors, including 4 summer of code students and multiple development sprints.

Mon Aug 26, 2019 · 3 min read · by hrxi GSoC student report

End of the Google Summer of Code

This Google Summer of Code was about adding peer-to-peer file transfers to Dino. Dino is an XMPP client, XMPP is decentralized instant messaging standard. The work was mostly done in two larger pull requests.

Tue Aug 6, 2019 · 3 min read · by hrxi GSoC student report

Ninth and tenth week: Interoperability fun

After finishing the SOCKS5 bytestreams transport for Jingle (S5B, XEP-0065, XEP-0260), I was asked whether I had already done interoperability testing with other clients for the fallback to in-band bytestreams.

Thu Jul 25, 2019 · 3 min read · by hrxi GSoC student report

Eighth week: Standards

Sometimes, XEPs are really imprecise or even lack information about some interactions. Most of the time, it’s about error handling where it’s not really specified what to do in error cases, as the XEP mostly deals with the “happy path” when everything is working.

Mon Jul 22, 2019 · 2 min read · by hrxi GSoC student report

Seventh week: Socks 5 file transfer

The blog posts have slipped somewhat, last blog post covering two weeks. Let’s try to fix that. The next step for file transfers was to implement more Jingle transport methods. Currently, only in-band bytestreams are implemented as transport methods.

Tue Jul 9, 2019 · 1 min read · by hrxi GSoC student report

Fifth and sixth week: File receiving

In the last two weeks, file receiving over Jingle has been implemented. This means that basic Jingle file transfers are available in Dino now (at least once the pull request #577 has been merged).

Thu Jun 27, 2019 · 1 min read · by hrxi GSoC student report

Fourth week: Some UI integration

File sending over Jingle (with in-band-bytestream transport) has now been integrated into the UI. This has fortunately been quite easy as Dino already had support for file sending, via HTTP uploads.

Tue Jun 18, 2019 · 2 min read · by hrxi GSoC student report

Third week: Interoperability testing

I managed to get the basic in-band bytestream file transfers working. It still doesn’t have any user interface, that’s depending on a project by my mentor. For now, it’s simply triggered by a hardcoded target JID that gets a file transfer when it sends a presence.