Skip to main content

Decarbonation

 Chouette, au travail, mon département va tenir une cession de visu. Nous sommes tous en télétravail complet. Afin de ne pas trop dégrader le service client, la rencontre aura lieu en deux fois, sur deux semaines différentes séparées d'un mois, histoire que tout le monde puisse voyager et se remettre.

J'aime ce genre de rencontre, à Mozilla à la fin, elles avaient lieu deux fois par ans. Elles permettent d'échanger, de rencontrer en chair et en os les gens avec lesquels on interagit au quotidien. Lorsqu'elles sont plus larges, elles permettent aussi de rencontrer d'autres départements et d'avoir de bonnes interactions qui finissent toujours par servir à la fin.

Cette rencontre n'est vraiment pas loin de chez moi, pour une fois.  L'application pour acheter le billet me propose de tenter le train afin de décarboner mon trajet. Je tente mais je rencontre une erreur :


C'est cryptique, comme il est tard, je décide de retenter le lendemain tout en regardant les prix des billets d'avions. J'en profite aussi pour voir si le trajet est disponible en train. Bonne nouvelle, c'est faisable, ça ne prend que 7:30.

Ce matin, j'essaye de nouveau l'option train. Même erreur, j'engage donc le support de l'applicatif par lequel je passe afin de comprendre cette erreur. La réponse tombe, ce trajet en train n'est pas achetable via la plateforme.

Comme je n'aimais pas d'avoir reçu une erreur, j'avais commencé à engager mon management. Réponse de ceux-ci, si la plateforme ne propose pas de train, achète ailleurs et faire une note de frais. Je me mets donc à comparer les prix de manière sérieuse. 338€ par avion, 498€ par le train ........... C'est impossible a justifier.

Comments

Popular posts from this blog

Firefox OS's story from a mozilla insider not working on the project

  I clearly remember, but can't date it. I was working for Mozilla messaging at the time ( momo ), being the QA lead for Thunderbird. It was at the end of one of the Mozilla All-hands, maybe in 2011 or 2012. At one of the ending keynotes, we were introduced to Boot 2 Gecko. A hack that would let US - Mozilla own the platform to run a mobile browser on. At the time, the iPhone was going strong and Google was trying to catch up with Android. MeeGo had been in development at Nokia for a while but was going nowhere even when Intel tried to help. Blackberry was slowly starting to die. In the Silicon Valley everything was about mobile, mobile, mobile and the emerging South Easter Asian market, where people would skip computers and use smartphones to join the internet revolution. We were struggling with Chrome and the massive investment by Google to take market share. Our Firefox port on Android was having loads of issues. We were denied by Apple's policies to be present on iPhones....

Key signing party at fosdem 2024

I'm organizing a GnuPG key signing party in order to bolster our web of trust , since there is no official ksp this year. I have organized a few in the past using tools like biglumber (website is gone, if someone know of a replacement or where the source code of site is, I might end up running one again) and others tools . I've also run once the KSP at FOSDEM and helped running it a few other times.    === Details below === When, Where   We'll meet in front of the infodesk stand in building K around 12:00 Sunday Feb 4th 2024. I'll have a sing of some sort with KSP and or Key Signing Party . Once enough participants show up we will move outside to proceed with the party. What to Bring Warm cloths as the party will happen outside this year, like in the good old days. I hope it won't rain, but it might. Piece of papers with your fingerprint written on them. Each piece should look like below:  $ gpg --fingerprint 34246C61F792FBCC1F23BFF296BD1F38FEA32B4D pub ...

Are mozilla's fork any good?

To answer that question, we first need to understand how complex, writing or maintaining a web browser is.  A "modern" web browser is : a network stack, and html+[1] parser,  and image+[2] decoder, a javascript[3] interpreter compiler, a User's interface, integration with the underlying OS[4], And all the other things I'm currently forgetting.   Of course, all the above point are interacting with one another in different ways. In order for "the web" to work, standards are developed and then implemented in the different browsers, rendering engines. In order to "make" the browser, you need engineers to write and maintain the code, which is probably around 30 Million lines of code[5] for Firefox. Once the code is written, it needs to be compiled [6] and tested [6]. This requires machines that run the operating system the browser ships to (As of this day, mozilla officially ships on Linux, Microslop Windows and MacOS X - community builds for *BSD do ex...