Conference au POOP 2014: HackerAgenda aidons nous a mieux nous parler blog - 13/1/o

Une conférence que j'ai donné au POOP 2014 à Paris en Juin dernier sur HackerAgenda, un projet d'agenda automatisé aggregant de très nombreuses sources d'événements pouvant intéresser les hackers en Belgique.

L'idée derrière étant d'essayer d'améliorer la situation "plein de gens font plein de choses géniales mais personne ne se connait".

Dans cette conférence je parle de 2 approches face à cette situation (dont HackerAgenda) et j'essaie de trouver des gens motivés pour lancer un HackerAgenda pour la France.

Some though on building userless website blog - 30/12/o

Right now, one of my toy project is to build a free software ethical alternative to the trio: meetup.com/facebook events/eventbrite (mainly because there seems to be strictly no alternatives available).

While thinking on how to do that, my initial idea was simply to "simply" do a clone of meetup.com. Not especially exciting. Then I realised that there was a funnier and way more interesting way of doing this. My inspiration came from etherpad and doodle (well, framadate), two website where to start working you just have to click on one big button that say "create to new pad/survey for me" and you're done: no user registration, nothing.

Thus came the logical conclusion on making this alternative userless and seeing how far that idea can be pushed.

In a world where the vast majority of proprietary services try to get as much data as possible in exchange of "free" services and where some governmental agencies seems a bit too curious about what we are doing, I think that it's worth a try for the free software movement to explore how far can we build viable tools while collecting as few personal data as possible (because they can't "stole" data you don't have).

And on the other hand, having a tool where you don't have to register an account really lowers the barrier of entry, thus the adoption. This could be an interesting advantage for free software to offer a attracting alternative (in addition to the ethical part).

So, after thinking about it for some time, here are a series of ways that I will probably implement this idea in this alternative (some of those are already done). The strategy is to ask as few as possible and only ask more when "more" is absolutely needed, a "leveraging" strategy (for now, "more" seems only to be an email address).

For reference, the workflow of the application is:

First idea (from doodle): use unique, hard to guess url:

Simple additional security idea: allows the event organiser to password protect the event administration page. Same for the event page (for private events).

Simple privacy idea: allow the user to hide his nick from the public list of attendees (the event organiser will still be able to see it).

Another simple privacy (and also convenient) idea: allow the event organiser to not display the attendees list on the public page of the event. This also allows to have a more "eventbrite"/ticketing approach to the event organisation."

Convenient idea for a minimalist privacy trade-off: temporary link the privates page (the ones that have unique hard to guess urls) to the user cookie/session and display them somewhere for the user to get them back.

Another convenient idea: have a simple form to allow the user to send himself an email containing a link to those uniques pages (after the creation of the pages). Something like "send me this link via email". Do not store the mail address.

First leveraging: ask the user to store his email. Do not expose/share this email via anyone, never.

This allows to:

And this adds one very cool feature: add the possibility for the user to have on one page all the places where his email is "linked" to something: event attending and created event. And of course, give the user links to the "unique urls" pages corresponding to those place and to remove his participation/email from those places.

The way to gain access to this page is a simple form where the user puts his email address, this sends him an email with a link to a "unique url" page valid for a certain period of time.

That's all for the big main patterns I've come up with for now (there are small variations/details like "possibility to suppress event"/"give a life time to events"/"suppress my participation"/"put password at those places" etc... that I haven't write down here because I'm lazy and that they don't bring that much).

I'm interested in your opinion and if you have other big main patterns idea on this subject.

And to finish, some downside of this userless approach:

While I was more interested in discuting the principles in this post, you can find the source code of the project here and a public instance here.

L'autre speed dating des alternatives par esperanzah blog - 6/7/o

Je suis allé ce samedi à l'événement "L'Autre Speed Dating!" organisé, entre autre mais pas que, par le village des possibles de Esperanzah.

J'étais assez méfiant au début de la formule "speed dating" mais en fait ça s'est révélé très cool: en arrivant on marque une association et votre prénom sur un mini badge puis vous piochez 2 bouts de papiers dans un panier, un vous disant quoi faire (eg: demander à la personne de vous présenter quelqu'un qu'elle connait) et l'autre qui rencontrer (eg: quelqu'un de l'association X). Le résultat était très chouette, les gens chaleureux et dans le bon état d'esprit, ça a vraiment bien marché pour rencontrer du monde à qui je ne serai pas allé parler normalement Je ne suis pas convaincu que ça marcherait pour toutes les communautés (/me regarde les hackerspaces) mais c'est clairement une idée à reprendre.

La deuxième partie était en fait extrêmement proche d'un BarCamp, appelé un "Forum Libre" et présenté de manière très chouette et chaleureuse ("les gens avec qui vous êtes sont les bons gens"):

(Description simplifié, j'ai plus les règles à 100% en tête, mais c'était vraiment comme un BarCamp.)

J'étais à une table avec la question "Quel file rouge pour nous rassembler ?" qui était vraiment la question de "Pourquoi on devrait faire ça". Le débat était vraiment riche, toute la question est en fait de comment définir les gens de ces mouvements, autour de quelles valeurs les rassembler et c'est vraiment un exercice difficile tellement ces mouvements sont d'origines différentes et spontanées sans forcement une réflexion derrière autre que résoudre un problème local.

De mémoire, des pistes et partie de définition:

Puis ça s'est malheureusement arrêté là à cause du foot (90% des gens souhaitant le regarder), ça a pas mal brisé le rythme de l'événement, je suis resté dans un pièce d'en haut avec quelques rescapés mais c'était frustrant, l'événement n'ayant duré que 2h30, les gens commençaient à bien être chaud pour discuter de tout et n'importe quoi.

Des mouvements que j'ai découvert/rencontré:

Review: Garrett Smith - Why The Cool Kids Don't Use Erlang reviews - 5/7/o

Garrett Smith - Why The Cool Kids Don't Use Erlang from Erlang Solutions on Vimeo.

In this talk Garrett try to explain why "cool kids" don't use Erlang (instead of Ruby for example). To do so he has made a short survey. He is talking to Erlang people while making this talk.

Questions of the survey (all are open questions):

Then more general questions to have an idea of who answered this survey (he didn't say to who he sent the survey).

He had 181 responses, most of the answers came from experienced and influential developers working in team.

Most of the answers are quite expected (hard to learn, people are fanatic about it, hard to find devs) but some of them are quite noticeable:

Additional informations:

I'm still a bit septic by the fact that to answer this question, the speaker asked the Erlang users instead of asking the "cool kids". And by a matter of fact, he didn't end up concluding with an answer to his question but more with a call for trying to fix this situation and pushing ideas.

Andrew godwin designing djangos migrations pycon 2014 reviews - 5/7/o

A talk by the developper of the Django South migration explaining his work of integrating migrations directly in the core of Django 1.7 (unreleased right now).

Interesting informations:

This talk is quite short (20min of speach, 5 of Q&A) so there isn't that much informations but this give a good otherview of what to news migrations will be like and how it has been done.

Atom feed