eliabieri / blnscpp

C++ API for the Big List of Naughty Strings

Hi, I'm Elia 🦦

I'm a 27-year-old self-taught programmer from Bern, CH.
Solving everyday problems is what I'm most passionate about.
I strongly believe in learning by doing.
What I love is to iterate fast, try unconventional approaches, and I'm not afraid of doing a deep dive into new technology.
Recently, I've finished by Bachelor in Computer Science at the Bern University of Applied Sciences.
I work as a Fullstack-Developer part-time and also do freelance work. I make apps for different platforms using Flutter.

You can read all about my current projects at eliabieri.dev

blnscpp's Issues

Empty Strings are not ignored

The file blns.txt contains empty strings to split sections. They are retrieved when calling the getString() static method but they should not.

broken link in README.md

On line 71 of README.md, the BLNS repository link goes to https://github.com/minimaxir/big-list-of-naughty-string which omits the final s and therefore goes to a 404 page.

this is what it should be:

[BLNS repository](https://github.com/minimaxir/big-list-of-naughty-strings)

About single header

Hi 😃

This project is presented as a single header API for BLNS. However it has not been the case anymore since I pushed my changes. We could imagine using a tool like Quom to generate the header and release it using Github actions. However the header-only release would not include blns.txt as it is not in this repository anymore.

We have two choices :

• We could deliver the header with a fixed version of blns.txt (downloaded in a github pipeline). This would make the API usable even for people that don't use Cmake. However, as blns.txt version is fixed, we would have to release a new version of the project everytime the list is updated. The user would need to download the release everytime and frequently check for updates. Not very convenient, either for the user and for us.

• We could change the way the project is presented and stop delivering a single header for this.

In my opinion it is important to have an updated version of the list as vulnerabilities may be discovered frequently. The single header could be compromising for the security of the user's app.

NB : With CMake, the list is updated automatically when you run cmake from a clean directory.

What do you think ?