As you may know, related to a previous post, I was using Aviate launcher on Android. I was so happy with it that I started to speak about it around me and promoted it.
My friend Romaric (@evoxmusic) informed me that this software required too much access in his opinion and that I should look at the privacy policy of Aviate.
After starting reading it, I could find this:
we may collect Personal Information such as your name, email address, phone number, location information, unique device identifier, and third-party account credentials (for example, your log-in credentials for Facebook or other third party sites)
I recently changed my smartphone (yes once again) because I was very interested in Galaxy S5 features compared to Nexus 5:
Waterproof: better when you got child’s and can record video underwater! Better autonomy: I can have a normal day without charging it! Better camera: once again when you have child’s…The camera makes very good photos compared to Nexus 5. Bigger screen: not a big point for me but it is better Storage: can add a micro SD card.

Last week, have been faced on a big sniffing issue on my wiki. The guy wanted to download all my wiki content. In reality I do not really care as it is open, free for read and contribution is welcome. However, the current VM where the blog and wiki are running didn’t support aggressive sniffing that this guy made. That’s why CPUs were at 100% of usage because of PHP requests, PHP-FPM was overloaded (reached my configuration limits).

Today is the dotScale European conference. This is the first time I go to this event and it looks like very interesting.
Thanks to eNovance to give me the possibility to be there.
There is a lot of hackers here. I’ll make a short review about it in the next post…keep connected :-)
To get more information on the event: http://www.dotscale.eu/

Next Tuesday, an OpenZFS conference will take place in Paris. I would like to assist as I’m a ZFS fan, however I couldn’t so easily.
I didn’t really follow OpenZFS and hope we could see videos when the event will be finished. If you don’t really know about ZFS and can have the chance to assist, I strongly recommend it to you.
To get more informations on the event, follow the link.

I started to play with Ansible a little bit more than a week ago and I really enjoy it compared to Puppet. I still do not have all my reflex that I can have on Puppet, however what I can say is how easy it is to start making complicated things on Ansible!
I started to rewrite my Puppet manifests to Ansible playbooks and what I can say is it’s really fast and easy.

Regarding one of my latest post, talking about Fluentd, some of you asked me why I’ve chosen Fluentd instead of Logstash. First of all, I’ve looked at this blog post, which kindly resume the current situation. Looking at this and with feedback I got, I could establish this array:
<td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #c9daf8; font-weight: bold; text-align: center;" data-sheets-value="[null,2,"Logstash"]"> Logstash </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #c9daf8; font-weight: bold; text-align: center;" data-sheets-value="[null,2,"Fluentd"]"> Fluentd </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; text-align: center;" data-sheets-value="[null,2,"Flexibility/Interoperability"]"> Flexibility/Interoperability </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; text-align: center;" data-sheets-value="[null,2,"Simplicity/Robustness"]"> Simplicity/Robustness </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; text-align: center;" data-sheets-value="[null,2,"JRuby"]"> JRuby </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; text-align: center;" data-sheets-value="[null,2,"Cruby"]"> Cruby </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #d9ead3; text-align: center;" data-sheets-value="[null,2,"More"]"> More </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #f4cccc; text-align: center;" data-sheets-value="[null,2,"Fewer"]"> Fewer </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #f4cccc; text-align: center;" data-sheets-value="[null,2,"Basics"]"> Basics </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #d9ead3; text-align: center;" data-sheets-value="[null,2,"Scalables"]"> Scalables </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #f4cccc; text-align: center;" data-sheets-value="[null,2,"Lot"]"> Lot </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #d9ead3; text-align: center;" data-sheets-value="[null,2,"Lot more"]"> Lot more </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #d9ead3; text-align: center;" data-sheets-value="[null,2,"Simple (drop a jar)"]"> Simple (drop a jar) </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #fff2cc; text-align: center;" data-sheets-value="[null,2,"Can be complex (dependancies)"]"> Can be complex (dependencies) </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #d9ead3; text-align: center;" data-sheets-value="[null,2,"Yes"]"> Yes </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #d9ead3; text-align: center;" data-sheets-value="[null,2,"Yes"]"> Yes </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #f4cccc; text-align: center;" data-sheets-value="[null,2,"Forward to 2 hosts"]"> Forward to 2 hosts </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #d9ead3; text-align: center;" data-sheets-value="[null,2,"LB A/A or A/P"]"> LB A/A or A/P </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #f4cccc; text-align: center;" data-sheets-value="[null,2,"Can loss messages"]"> Can loss messages </td> <td style="padding: 2px 3px 2px 3px; vertical-align: bottom; background-color: #d9ead3; text-align: center;" data-sheets-value="[null,2,"No message loss"]"> No message loss </td> Logstash and Fluentd are both powerful solutions, they both got pros and cons.
