• Timothée Jaussoin's feed

    I'm a Web developer, hacktivist, defending the Net Neutrality and citizens privacy. Author of Movim, a XMPP social-network client written in PHP and HTML5. If you have any questions about Movim, XMPP or something related, please ask it in the official chatroom : movim@conference.movim.eu.

  • Analysis of the Facebook app

    Timothée Jaussoin – Tuesday, 11 April, 2017 - 12:58 - Wednesday, 12 April, 2017 - 17:47

That's crazy. Having to install 250Mb of data on your phone for a simple frontend of a social network is unacceptable.

One funny extract that I got from HackerNews.

Things that are smaller than Facebook's iOS app:

  • Windows, through at least Windows 95, if you count stuff written to disk during install
  • The Java Runtime Environment
  • Eclipse IDE
  • Google Chrome for OS X (beware—updater leaves old versions in the app bundle)
  • Firefox for OS X
  • Pokémon Go
  • A two-disc set encoded in 256kbps AAC
  • I have been using Movim for just one day and these are my impressions*

    Timothée Jaussoin – Wednesday, 5 April, 2017 - 18:09 - Wednesday, 5 April, 2017 - 18:12

I'd like to reply to this post with some details that, I think, could be interesting for the other Movim users :)

When you add a contact they must accept your request and, when they accept it, you have to confirm it again. I sent them the request, of course I want to be friends! This last step doesn’t make much sense

This is actually related to the default XMPP protocol behavior regarding contacts invitations, thanks for the feedback I'll try to see how I can improve that in the upcoming release.

If someone has sent you a friend request you won’t be able to log in on Movim for Android: you’ll have to accept (or decline) the friendship request on a web browser and only then will you be able to sign in on Movim for Android again

This bug doesn't seems related to the friend request to me (I have several pending requests on my account and I didn't had this related authentification issue). However the bug seems serious enough to be investigated.

Polls like on status.net (with more than just two options)

It would be a really a interesting feature indeed but is quite complex when it's done on a decentralized network. Also it will requires some discussion and thought on the XMPP level to see how it can be compatible with the other clients.

Ability to share updates/blog entries only with certain contacts or groups

This is not possible regarding how the current XMPP protocol (especially Pubsub) is working. For the moment we can only change the accesses on the node level (the blog or the community) and not on the item level (the posts).

Autosave for blog entries (and Drafts would be good too, but not essential)

You can open a feature request on GitHub for that one :)

Only public blog entries are visible on a contact’s profile, even if we are friends. I believe that if we are friends and my friend has shared something with their contacts (not publicly), I should be able to see it on their profile, and not only on the news feed

That's another nice feature request that can be implemented quite easily.

Ability to visit a contact’s profile clicking on their name (this works on Newsfeed, but not on Chats)

You can actually do it by clicking on the contact picture in a one-to-on discussion and by going in the contacts box in a chatroom (if the owner has allowed the share of JIDs).

An easier way to create communities. Right now this feature is pretty much hidden

This is mostly UI refactoring, possible but I don't have a clear idea to do it "more easily" for now.

Ability to create private communities

Once your Community is created you can configure using the settings offered by the XMPP server for the Pubsub nodes.

Ability to invite contacts to a chatroom from the chatroom, without sending any link

https://github.com/movim/movim/issues/188

On Safari (both macOS and iOS) textbox takes only 20% of the width of the screen (it happens on chats and comments)

That is a bug. You can open a ticket on GitHub with screenshots :)

Unified timeline for all pods [?]

Quite impossible in a decentralized network without exploring continuously the all graph (and basically reinventing Google for XMPP).

Button to export our data

Not planned. But all the data are saved on the XMPP account of the user so it should be quite trivial to build a tool outside Movim that can do that (and reimporting them? where?).

Ability to share location with contacts

If there is no interesting feature behind that I don't see the point of it in Movim for now.

Movim for Android needs: Proper notifications for chats, comments, news, likes… Different ticks for different statuses (delivered to server, read…) Proper management for chatroom/conference links Send/Attachment button to work as expected

I'm open to any contribution on the Android client to improve those points but it's not my priority to work on specific features for a dedicated platform (I'm already quite busy by building the generic things :)).

As of today Conversations for Android would be the best option if your goal is to exchange messages, but then you wouldn't be able to take advantage of Movim's newsfeed or blog posts, which are the added values of this network and what makes Movim stand out over any other xmpp service. I believe that the team shouldn’t neglect the development of mobile apps knowing as we know that more and more people connect to the internet mainly via smartphone. What do I think about it?

I agree but I really have a limited amount of time on the project so I'm focusing more on features that will have a bigger impact for most of the users for now. I'd like to wok more in per device/OS/platform integration but that can takes a lot of time to "do it well".

Movim is seven (?) years which shows the developing team is committed to the platform. And that's great news. This feeling could be reinforced if they posted blog entries more often (maybe once a month?).

That's true, also because of the limited amount of time that I have for the project here. But I'm trying (like with the current post).

I believe that Movim would benefit from a better Android app as it could be gateway to gaining more users, boost social interest, and –who knows– attract more brains to help take it further. But I understand that they have prioritised their website which is universal and it does the job really well.

You got it, but I'm always really happy to talk about and integrate external contributions in Movim and the related projects.

Despite the far-from-perfect Android app, Movim is the most developed decentralised social network platform I have seen. It’s full of interesting features and if you come from pump.io or tent.io you’ll find many similarities and promising improvements. I would say that Movim has strong bones, it ticks more than just the basics and now it just needs to polish its features before adding new ones.

<3


  • Original post deleted

  • Configurer MPV pour les bandes son 5.1

    Timothée Jaussoin – Monday, 13 March, 2017 - 23:45 - Monday, 13 March, 2017 - 23:46

MPV est mon lecteur de vidéo de référence depuis plusieurs années maintenant. Son évolution rapide rend néanmoins sa configuration délicate. En effet beaucoup de paramètres de configurations, issues de mplayer, ont été dépréciés au cours du temps.

J'utilise principalement MPV pour lire des films sur un système de son compatible Dolby Digital et DTS.

Voici donc quelques lignes de configurations que vous allez pouvoir mettre dans ~/.mpv/config afin de profiter au mieux de votre système de son home-cinéma sur la dernière version, à ce jour, de MPV (0.24.0).

audio-channels=2
audio-spdif=ac3,dts
af=scaletempo,lavcac3enc=yes:640:3

Quelques explications sont nécessaires. La première ligne force la sortie audio en stéréo, en effet, même si cela peut paraître surprenant les flux audios Dolby Digital et DTS sont envoyés dans un flux qui est déclaré en stéréo (pour des raisons de compatibilité ?).

La deuxième ligne force MPV à envoyer les bandes son qui sont dans les formats Dolby Digital (AC3) et DTS en "passthrough". Le flux de donnée est transmit directement à l'amplificateur qui se chargera de le décoder lui même.

La troisième ligne permet d'utiliser le module lavcac3enc pour encoder à la volée les flux 5.1 qui ne sont pas en DTS ou Dolby Digital en AC3. En effet il devient de plus en plus courant de trouver des films et séries en AAC 5.1 par exemple.

That's all folks!

  • Quelques nouvelles concernant Movim

    Timothée Jaussoin – Wednesday, 8 March, 2017 - 23:47

Je n'ai pas donné beaucoup de nouvelles ces dernières semaines, en particulier concernant le projet Movim. J'ai en effet été pas mal occupé, notamment par un déménagement et des démarches administratives.

Ne vous en faites pas, après cette petite pause, je me remet progressivement au travail. En particulier pour préparer la prochaine release, Movim 0.11. Celle-ci à déjà été repoussée de quelques semaines à cause d'un sérieux bug de gestion des cookies qui s'est soldé par une profonde refonte du système de session au sein du projet.

Néanmoins le code ne devrait plus trop évoluer ces prochaines semaines, vous avez donc entre les mains une version proche de la 0.11 finale.

Des travaux de maintenance et de mises à jour sur les serveurs du projet m'ont également occupés ces derniers temps. Je prépare, entre autres, une migration des deux serveurs XMPP movim.eu et jappix.com de Metronome à ejabberd (jappix.com en priorité). Ce projet devrait encore prendre quelques mois puisque des adaptations doivent êtes faites sur les outils de migration entre ces deux serveurs.

Si vous avez des questions, n'hésitez pas à poster un commentaire ou venir en discuter sur le salon officiel.

  • 7 Comments

  • 9 March, 2017 Marzanna

  • 9 March, 2017 eyome

  • 9 March, 2017 eyome

    Quel est l'avantage d'ejabberd par rapport à Metronome ?

  • 9 March, 2017 Matija Šuklje

  • 10 March, 2017 Emile Schons

    Serait intéresse par les avantages/desavantages aussi concernant metronome "vs" ejabbered ?

  • 13 March, 2017 goffi

    eyome, mulles&gt; c'est maintenu

  • 9 April, 2017 Samel Dorsaz


  • What Have We Learned From This Open Source Project?

    Timothée Jaussoin – Tuesday, 7 March, 2017 - 09:49 - Wednesday, 12 April, 2017 - 17:47

I wanted to post this link for a while, a really interesting list of what I can encounter daily while working on Movim.

  • Utrecht sous la neige

    Timothée Jaussoin – Sunday, 12 February, 2017 - 11:35

Un petit weekend enneigé à Utrecht aux Pays-Bas.

  • Corriger la date des photos avec jhead

    Timothée Jaussoin – Sunday, 12 February, 2017 - 11:31

Si vous avez comme moi un téléphone ou appareil photo qui n'écrit pas correctement les données EXIF des images prises, en particulier le champ DateTime (qui correspond à la date où la photo à été prise), il existe un petit outil appelé jhead qui vous permettra de corriger certaines de ces informations.

J'utilise plus particulièrement la commande suivante:

jhead -dsft <fichiers>

Elle permet de réécrire le champ DateTime (qui est systématiquement à 1970-00-01 pour mon cas) à partir de la date de création du fichier (qui se trouve être la bonne).

Ensuite il ne vous reste plus qu'à importer tout ça dans votre logiciel de gestion de photos préféré (Shotwell dans mon cas) :)

  • What should you think about when using Facebook?

    Timothée Jaussoin – Friday, 3 February, 2017 - 18:21 - Wednesday, 12 April, 2017 - 21:18

A nice article explaining how Facebook is collecting personnal data about you.

TL;DR: Facebook collects data about you in hundreds of ways, across numerous channels. It’s very hard to opt out, but by reading about what they collect, you can understand the risks of the platform and choose to be more restrictive with your Facebook usage.