The Hobo's IoT Animated Clock, With Trust Issues

Manifesto: giving trust to unreliable time providers isn't worse than trusting potentially unreliable access points with personal credentials. This clock has no RTC module and doesn't need to reach a NTP server to adjust its time. It uses WiFi access points openness in order to extract the date/time from the "Date" HTTP header that may be sent by some captive portals. So it will scan all nearby open WiFi AP until it finds a suitable response. Breakout: - Wemos Mini D1 (ESP8266) - SSD1306 OLED (128x64 Monochrome) - TP4056 LiPo Charger - 3.7v LiPo (270mAh, tiny size) Boot sequence: - Enumerate Open WiFi AP - Get an IP address - Connect to captive portal - Look for a "Date" HTTP header (and against common sense, trust its value) - Adjust the clock accordingly (at 0:40) Code: https://github.com/tobozo/ESP8266-Hobo-Clock Expecting unknown networks to provide a HTTP header value and relying on it to estimate time is like counting on other people's wealth to survive, hence the Hobo