I begin again to write after a long time of silence and after I have kept at a safe distance the world of writing. It’s not easy to return on one’s steps, especially if you are a visual creative who uses the writing for the necessary to explain the own projects. It’s hard to explain to people who read you, the reasons which take you to open a publication on web, it’s hard to not think how you can make known the arguments each time you will discuss if you know these arguments are not common but there are few people interested them. I think the first post must be a preface on what we would like write in the following posts. It must represent our imaginary line on which to pin down the topics we would like to talk about, a reference for all those times we lose sight the pourpose for which to write, a note to be read every time it’s missing the reasons to continue, an engagement to be revise to the need to reorganize own work in a new viewpoint and under new scenary....
For many time I have spent awareness on cybersecurity and beta testing in opensource but also on proprietor operating system, softwares and applications. Myself, as graphic programmer, have to meet programming errors bound to development tool so to have the doubt: is there a Zero day? To correct an error doesn’t say there isn’t an hidden Zero day, or rather an exception in the development tool that requests a change of procedure to avoid the unknown obstacle in that moment. Some errors emerge after many time and after the use of software or platform, they are bound wear of the application codes. In a video “Code error - Code correction” I have introduced a tedious argument in the hacking. From a creative point of view I said directly the error is more lovely than the correction. From a security point of view it’s exactly the opposite, or rather an enormous damage for everyone that meets a Zero day that it wasn’t corrected. The moti...