Especially for the performance claims these or a Readme on how to replicate them would be great.

There are also decades of articles on how lua works with C and C++, and you can find examples for Rust and others too.

A full BOM and Tutorial will be released FOSS if i manage to finish it.

While for European elections it is usually 40-50% with huge differences by country (https://results.elections.europa.eu/en/turnout/)

My biggest problems with Tidal (except for the price) are: - Music suddenly becomes unavailable (greyed out), only to be become available under the same name later again (but you need to manually re-add it to playlists). - Sometimes it just stops the playback and if i resume it always jumps to one specific song.

I cannot say anything about the mobile player, as i only use it on PC.

Alternativly: Just buy the music you like as FLAC.

"Combination of Classical and PQC Security: The secure implementation of PQC mechanisms, especially with regard to side-channel security, avoidance of implementation errors and secure implementation in hardware, and also their classical cryptanalysis are significantly less well studied than for RSA- and ECC-based cryptographic mechanisms. In addition, there are currently no standardised versions of these mechanisms. Their use in productive systems is currently only recommended together with a classic ECC- or RSA-based key exchange or key transport. In this case, one speaks of a so-called hybrid mechanism. Parallel to a PQC key transport, an ECC-based key exchange using Brainpool or NIST curves with at least 256 bits key length should be performed. The two shared secrets generated in this way should be combined with the mechanism given in Section B.1.1 of this Technical Guideline. Here, the standard [96] in its current version explicitly provides the possibility to combine several partial secrets. A hybrid approach, as proposed here, is further described for example in [5] as the most feasible alternative for a use of PQC mechanisms in the near future. Provided that the restrictions of the stateful mechanisms XMSS and LMS recommended in this TechnicalGuideline are carefully considered, these hash-based signatures can in principle also be used alone (i.e., not hybrid), see Chapter 6"

[0]: English version: https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publicat...

[1]: German version: https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Publikat...

If you encrypt it, this is no longer possible. If a cheater wants to decrypt it, he has to get access to the decryption key, which usually is send over an TLS encrypted connection (with certificate pinning in place) [Or in some cases self made encryption :/].

Therefore he has to either reverse the game to get the certificate or has to attempt to read it while the game is running. In the first case the game developers (and the Anti-Cheat providers) will try there best by obfuscating the specific regions. And the 2nd case is basically what AC is all about, and therefore difficult for modern Anti-Cheats.

This is mostly a result of a previous test, which revealed that in case of a catastrophe, most germans would not be warned (Sirens not functioning, cell broadcast was not used, ...)

Sadly the website of our Federal Office for Civil Protection and Disaster Assistance is not translating every page to english. https://www.bbk.bund.de/DE/Warnung-Vorsorge/Bundesweiter-War...

It's measureable, but in most applications i wouldn't optimize this part.