A french guide on the rust language. It is not complete as the official documentation but provides a good start with lot's of the rust's features.

Kafka has a good throughput with sequential Writes and Reads.

Kafka can move a lot of data because of the zero copy read principle:
Before:

1. Disc to OS buffer
2. Write the content of the OS buffer to the RAM
3. Copy the data to the application Buffer
4. Copy the data back to the socket buffer
5. Copy the data from the socket to the Network Interface Chip buffer and send it

With zero-copy read principle:

1. Read from the disc and load it into the OS Buffer
2. Directly copy to the NIC Buffer (the CPU is not involved)

Des avantages d'être un développeur ennuyeux.

• le pragmatisme
• la stabilité
• l'économie
• la simplicité

les systèmes de Microsoft utilisent une technique de « brute force » pour tenter de passer outre la protection par mot de passe.

Ils utilisent les mots de passe contenus dans une liste prédéfinie, et « ils extraient aussi les mots de passe contenus dans les emails »

L'éthologie avec le cheval demande l'apprentissage de multiples gestes et postures. Il est donc possible de les identifier, les retracer, et suivre l'évolution de l'avancement.

Another personal blog :)

A curated list of them

C'est cool aussi

C'est cool

How links with an @ in the URL becomes insecure, because they can redirect to a .zip domain simulating a file

A hacky way to store data as video. The proof of concept uses youtube.

a new #project #idea is to build the whole thing, but not only for youtube, but for any possible API endpoint :D

Here is separation of the responsibility of such a program:

• the image processing layer takes the file and converts it into an image or video
• the compression layer reduces the size of the data as much as possible
• the encryption layer guarantees the confidentiality of the data until the algorithm is broken, since the data is shared with a third party anyway. It can intervene
• the network layer allows data to be uploaded and downloaded to different providers (why limit it to youtube?)
• the data layer: it is responsible for storing information about the videos/images (video metadata: at provider X, accessible from such and such a URL, last modification date, etc.). It inserts metadata into the files through the image processing layer in order to decode them correctly (type of compression, etc.).
• the application layer: it allows to use everything with a UI/CLI. In short, an interface for the user.