# Public responses

2018-01-25

> Since David doesn’t allow public responses, I’ll try and follow his way of publishing letters in personal spaces.

> “HTTPS considered harmful”, yes, but isn’t HTTP too? (cache)

I try to link to any reference/response of my articles and/or to answer myself to feed the helix of knowledge we both create during the exchange (more to come on that concept). It induces to share the responsibility to maintain that content online for both sides (my cache somehow mitigates that but you get the point). I try to answer every email I receive related to my articles and sometimes ask if it is possible to answer publicly. I don’t know how to encourage more and I don’t know if I can actually handle it!

Maybe mentioning explicitly that sending an email can be short and that the reply can even be shorter. Maybe with a more prominent call to dialogue on each page. Maybe it’s okay like that and it serves as a filter for deeper reactions.

Other articles in English: On caching links, Bushcraft retrospective, Into the Raft, Into the Bugs, Meritocracy crisis, The Seller, the Teacher and the Wise, Into the Good, Into the Mice, Into the Camp, Into the Wind, Into the Snow, Into the Cold, Async Python Frameworks, Distributed teams, Into the Wild, Without JavaScript, Inclusive Python, Micro-cultures and governance, Resilient Web and Tools, Bitcoin and energy, Team building, Inclusive developer, Cultural Intimacy, Tools and teams, Senior developer, Slow Data, Inclusive communities, Delivery and value(s), Collaboration debt, Communities and leadership, Specifications and APIs. Oh, and most of the 2018 thoughts.