11–20 of 24 posts
There isn't much of a difference between this and having all notifications enabled.
Yes it's a separate screen but you'll put it where you can see it while working or there is no point in it. And then it will distract you.
There is another neat board that I like, smaller but looks nicer, the "ESP32-C6 1.47Inch LCD Screen" for just ten bucks: https://aliexpress.com/item/1005008465501661.html
> Instead of bolting TLS onto every application protocol (HTTP, MQTT, CoAP, etc.), what if we secure the network layer once and then use simple protocols on top?
IPSec, coming back with a vengeance!
This also makes me wonder what takes less space in ROM, a basic WireGuard implementation or a basic, stripped-down IPSec implementation (with only the ciphers and configuration necessary for the server compiled in). WireGuard has the advantage of being designed for simplicity, but IPSec has its 90s every-cycle-counts legacy that a lot of modern software has ignored since.
Nice project. The $15 price point is genuinely impressive for something like this. I've been curious about e-ink displays for a while but haven't taken the plunge. What's the refresh rate like in practice? And does it actually help you notice interesting posts you'd otherwise miss, or is it more of a fun desk decoration?
That $15 price is only possible because AliExpress operates within a Chinese export system that is indirectly subsidised by the state. AliExpress benefits from significant Chinese government support.
Nice project. The $15 price point is genuinely impressive for something like this. I've been curious about e-ink displays for a while but haven't taken the plunge. What's the refresh rate like in practice? And does it actually help you notice interesting posts you'd otherwise miss, or is it more of a fun desk decoration?
I kinda wonder what the packet loss story of UDP is like for simple protocols like these in the modern day. Clearly, it's good enough that this application runs without issue. > Instead of bolting TLS onto every application protocol (HTTP, MQTT, CoAP, etc.), what if we secure the network layer once and then use simple protocols on top? IPSec, coming back with a vengeance! This also makes me wonder what takes less spa…
For one it can adequately show if your WiFi is performing well...
In a home network setting I've got a UDP display sink (64x64px, RGB) with a custom protocol. It works fine-- no hard number as the performance varies based on other factors, including congestion. I've been able to push it to >90fps, but around 42fps there is virtually no flicker.
For context in my protocol I use all 512bytes, with 3 first being the "line number and such" data and the rest containing ~128 pixels.
Contrary to the second half of the article the display is not stateless (especially not WireGuard). However, the combination of minimum viable state and giving payment details to cloud services does simplify IoT projects.
Why not using MQTT? A Lambda that fetch new comments from HN, parse them into Markdown and push into MQTT; the ESP only needs to subscribes a topic on MQTT and render the messages.
I did find MQTT flavors that support UDP but neither MQTT/UDP nor MQTT-SN seem concerned with WireGuard-level security.
⁰(This article is AI-assisted content marketing good enough that I didn't realize it until ¾ through.)
I kinda wonder what the packet loss story of UDP is like for simple protocols like these in the modern day. Clearly, it's good enough that this application runs without issue. > Instead of bolting TLS onto every application protocol (HTTP, MQTT, CoAP, etc.), what if we secure the network layer once and then use simple protocols on top? IPSec, coming back with a vengeance! This also makes me wonder what takes less spa…
I kinda wonder what the packet loss story of UDP is like for simple protocols like these in the modern day. Clearly, it's good enough that this application runs without issue. > Instead of bolting TLS onto every application protocol (HTTP, MQTT, CoAP, etc.), what if we secure the network layer once and then use simple protocols on top? IPSec, coming back with a vengeance! This also makes me wonder what takes less spa…
> packet-loss For one it can adequately show if your WiFi is performing well... In a home network setting I've got a UDP display sink (64x64px, RGB) with a custom protocol. It works fine-- no hard number as the performance varies based on other factors, including congestion. I've been able to push it to >90fps, but around 42fps there is virtually no flicker. For context in my protocol I use all 512bytes, with 3 first…
- Episodic most often. Something transient causes high loss for a short time. This happens locally and “in the cloud”. - Persistent due to a back connection or very high network load. I only really ever see this locally.
But I can go days at a time and not lose even one of millions of probes and responses.
When connections are good, they’re excellent these days. When they’re bad, well that doesn’t seem to have changed.