Posts tagged in GSoC contributor report Page 1 of 3

Stateless File Sharing: Source Attachment and Wrap-Up

Recap Stateless file sharing (sfs) is a generic file sharing message which, alongside metadata, sends a list of sources where the file can be retrieved from. It is generic in the sense, that sources can be from different kinds of file transfer methods.
Read more…

Stateless File Sharing: Async, Metadata with Thumbnails and some UI

Async Asynchronous programming is a neat tool, until you work with a foreign project in a foreign language using it. As a messenger, Dino uses lots of asynchronous code, not always though.
Read more…

Stateless File Sharing: Sources and Compatibility

This is my next progress post about my Google Summer of Code project of implementing Stateless File Sharing (sfs) Storing sfs sources in a database Like everything else we receive, we need to store the sfs sources in a database.
Read more…

Stateless File Sharing: Base implementation

The last few weeks were quite busy for me, but there was also a lot of progress. I’m happy to say that the base of stateless file sharing is implemented and working.
Read more…

Project Stateless File Sharing: First Steps

Hey, this is my first development update! As some of you might already know from my last blog post, my Google Summer of Code project is implementing Stateless File Sharing for Dino.
Read more…

Stateless File Sharing GSoC project

Hey! I’m Patiga, a computer science student from Germany and a new contributor to Dino. The yearly Google Summer of Code has started, and I’m glad to be part of it.
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…