Dianara, a Diaspora client

I’ve started developing a new program.
This time it’s a Diaspora client, an application for GNU/linux that will allow users to manage their Diaspora accounts without the need to use a web browser.

September 2013 update: Dianara has been turned into a client for the pump.io social network, a powerful system that can be considered an evolution of StatusNet, which includes identi.ca and many other servers. Read more about current Dianara status here: https://jancoding.wordpress.com/dianara/

Dianara, an application to use the Diaspora social network

At the moment, it’s basically an empty shell. The only thing you can do, is enter your Diaspora ID (username@podname) and password, and see how your avatar and full name are fetched from your account information.

Diaspora‘s API is not ready to use yet, so there’s not much that can be done at the moment. Meanwhile, I’ll keep improving the interface, and the little network control there is now.

The code is, as usual, in Gitorious, at http://gitorious.org/dianara

It is, like my other projects, based on Qt, and as an aditional dependency, QJSON. It also supports FreeDesktop.org notifications, so you get nice notifications in KDE Plasma Desktop, Gnome, XFCE and other environments which support that specification.


7 Responses to Dianara, a Diaspora client

  1. MichaelSOG says:

    This is a Good Idea 🙂

  2. Sean Tilley says:

    This is seriously super cool. I’m gonna have to follow this one for sure, a desktop app is something I’ve wanted to see for ages.

    There’s a lot of progress coming with Diaspora adapting backbone.js. You can kind of think of it as a foundation for developing an API from in the long run. Anyway, you might want to look at the source for cubbi.es, as it’s the first Diaspora “Application”. It might give you a few pointers about authentication with a pod.

    • JanKusanagi says:


      I’m eagerly awaiting some API documentation, actually.
      From what I’ve seen until now, there are some notes here, some notes there… some paths you can guess from the D* source code… it’s interesting, but knowing clearly where to shoot would be nicer 😛

      For the OAuth part, I’ve seen the diaspora-client source, but I can’t figure much from that. From what I’ve read, the OAuth stuff is not really ready (maybe there are some internal instructions somewhere?).

      Regarding Cubbi.es (which indeed uses the /oauth/autorize path), where can I find the source for it?

      All I can see in github is the source for the FF extension and some javascript needed, but the auth stuff seems to be part of the web itself.

      I still have plenty to do even if authorization can’t be done yet, but if you have any extra details, let me know! 😀

  3. Hey this is good.
    i would like to help you if you want to do a python version of this

    • JanKusanagi says:


      Making a Python version of Dianara would mean mostly a complete rewrite, actually.

      But if you feel like creating a Python-based client using ideas or code from Dianara, feel free to do it, as long as it’s GPL-compatible 😉

      The problem is that at this point, there’s still no API (and I don’t see it coming anytime soon), so Dianara is on hold for now.

Care to give some feedback?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: