Add new file
Comparer les modifications
+ 63
− 0
CTF being one of my hobbies, I often use the Kali one and its command line. GIT was also used as I used to share [some solutions for general CTF](https://github.com/jdesalle/WriteUps) or for the [CSCBE](https://github.com/jdesalle/CSCBE2020Qualifier) publicly after event were finished for people to read and learn, or for people to find alternative solutions to them
I first looked into the current issue and saw one that seemed fitting, concerning the deprecation of the Feature-Policy header in favor of Permissions-Policy. It seemed feeting for two reasons: it was a small feature, but it required to read the (small) code and understand the intent of the program.
My (currently) only conrtribution was toward this issue, but I quite liked this project and will probably looked into the other opened issues, and look and what can be done to improve on the anaysis done, while respecting it's essence of staying a lean tools as expressed in the [contribution guidelines](https://github.com/trailofbits/twa/blob/master/CONTRIBUTING.md).
This repository is a peculiar case. It started in 2011 as an opensource repository for synthesis for student at the Engineering Faculty at UCLouvain, and have been pretty well maintained until COVID, though it currently doesn't have any official current Maintainer, the previous one still check for pull request until somebody take the role. While a lot of people used the synthesis of this repository, the program changes in 2018 made it so most of those synthesis where not up to date, which is when the second generation of maintainer took their role.
What I like about this project is that it's something that was directly used by a lot of people during their studies at uclouvain, quite a few contributors ended up doing pretty well, some of them engaging in a PhD. Maintainers also used to keep in touch whith faculty, removing things that wheren't supposed to be there (example with the ML course).