All posts published on Dino Blog Page 1 of 2

Dino 0.2 Release

Mexican Caribbean Coral Reefs

The 0.2 release adds message correction, improves the file upload functionality and provides more information about message encryption. Besides other smaller changes it also fixes a number of bugs.
Read more…

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.
Read more…

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.
Read more…

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.
Read more…

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.
Read more…

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.
Read more…

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.
Read more…

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).
Read more…

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.
Read more…

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.
Read more…