Which (fairly simple) C++framework would you recommend for a simple http server that binds to a hard-coded port and does a simple listen, read, write shebang on a server? We don't need nothing fancy or complex, we just want to avoid that native Linux sockets APIs boilerplate coding.
If a service is providing URL to * conversion functionality, how do they protect themselves from malicious URL and code? I should add that there is no Docker available on the host. Only Node, PHP and the usual shebang. Is it a matter of agreeing with the customer on predefined URLs upfront?
If all the services on a website are available only to registered, logged-in users, does one need a consent cookie thingy to begin with? Other than the framework's two essential session and security cookies, no other cookies are generated, there are no trackers and no analytics.
There are, however API interfaces allowing users to interact with the website's services. Some clients might have dedicated databases of their own too.
Can a "Do not consent" button be styled as an outline button and the "Consent" button be styled as as a filled button? If one is using Google's default AdSense consent dialog for the EU? Furthermore, must there be a "Do not consent" button on the dialog or not?