- https://hackaday.io/project/164694-esp32-air-quality-monitor/details
- https://randomnerdtutorials.com/esp32-bme680-sensor-arduino/
- https://esphome.io/components/esp32_ble_beacon.html
- https://circuitdigest.com/microcontroller-projects/esp32-based-bluetooth-ibeacon
- https://www.electronics-lab.com/project/using-the-ble-functionality-of-the-esp32/
- https://www.instructables.com/id/ESP32-BLE-Android-App-Arduino-IDE-AWESOME/
- https://randomnerdtutorials.com/esp32-bluetooth-low-energy-ble-arduino-ide/
Discover gists
-- Source: http://tylerneylon.com/a/learn-lua/ | |
-- Two dashes start a one-line comment. | |
--[[ | |
Adding two ['s and ]'s makes it a | |
multi-line comment. | |
--]] | |
---------------------------------------------------- |
The purpose of this document is to build Suricata on Windows for the purpose of development and CI. It does not cover installing or running Suricata on Windows.
For a brief user-level introduction to CMake, watch C++ Weekly, Episode 78, Intro to CMake by Jason Turner. LLVM’s CMake Primer provides a good high-level introduction to the CMake syntax. Go read it now.
After that, watch Mathieu Ropert’s CppCon 2017 talk Using Modern CMake Patterns to Enforce a Good Modular Design (slides). It provides a thorough explanation of what modern CMake is and why it is so much better than “old school” CMake. The modular design ideas in this talk are based on the book [Large-Scale C++ Software Design](https://www.amazon.de/Large-Scale-Soft
A fine marzo 2024 è stata messa online la Piattaforma Unica Nazionale dei punti di ricarica per i veicoli elettrici, in cui sono visualizzabili su mappa o in elenchi - e non anche come dati grezzi e aperti - i punti di ricarica per veicoli elettrici presenti in Italia.
Lo saranno in futuro? Non è dato saperlo, ma è molto probabile che avvenga, perché lo prevedono le norme e lo raccomanda il buon senso.
Navigando il sito con un browser (vedi immagine), si legge in chiaro che i dati sono esposti tramite API.
xattr -d com.apple.quarantine /path/to/app/myMacApp.app |
Structured logs are way better than normal logs for a whole bunch of reasons, but they can sometimes be a pain to read in the shell. Take this logline for example:
{"erlang_pid":"#PID<0.1584.0>","level":"error","message":"Got error when retry: :econnrefused, will retry after 1535ms. Have retried 2 times, :infinity times left.","module":"","release":"c2ef629cb357c136f529abec997426d6d58de485","timestamp":"2019-12-17T19:22:11.164Z"}
This format is hard for a human to parse. How about this format instead?
error | 2019-12-17T19:21:02.944Z | Got error when retry: :econnrefused, will retry after 1648ms. Have retried 2 times, :infinity times left.
<!-- country codes (ISO 3166) and Dial codes. --> | |
<select name="countryCode" id=""> | |
<option data-countryCode="GB" value="44" Selected>UK (+44)</option> | |
<option data-countryCode="US" value="1">USA (+1)</option> | |
<optgroup label="Other countries"> | |
<option data-countryCode="DZ" value="213">Algeria (+213)</option> | |
<option data-countryCode="AD" value="376">Andorra (+376)</option> | |
<option data-countryCode="AO" value="244">Angola (+244)</option> | |
<option data-countryCode="AI" value="1264">Anguilla (+1264)</option> | |
<option data-countryCode="AG" value="1268">Antigua & Barbuda (+1268)</option> |