# [derive(Clone)] Is Broken
rgbcu.be
New sphere-packing record stems from an unexpected source
quantamagazine.org
Mercury: Ultra-fast language models based on diffusion
arxiv.org
The chemical secrets that help keep honey fresh for so long
bbc.com
LookingGlass: Generative Anamorphoses via Laplacian Pyramid Warping
studios.disneyresearch.com
What Microchip doesn't (officially) tell you about the VSC8512
serd.es
I used o3 to profile myself from my saved Pocket links
noperator.dev
Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec
The Miyawaki Method of micro-forestry
futureecologies.net
Adding a feature because ChatGPT incorrectly thinks it exists
holovaty.com
My first verified imperative program
markushimmel.de
When Figma starts designing us
designsystems.international
What is going on in Unix with errno's limited nature
utcc.utoronto.ca
François Chollet: The Arc Prize and How We Get to AGI [video]
youtube.com
Why are there no good dinosaur films?
briannazigler.substack.com
ChatGPT testing a mysterious new feature called 'study together'
techcrunch.com
Show HN: NYC Subway Simulator and Route Designer
buildmytransit.nyc
Lightfastness Testing of Colored Pencils
sarahrenaeclark.com
Man of Glass: Boccaccio: A Biography
literaryreview.co.uk
Analysing Roman itineraries using GIS tooling
link.springer.com
SIMD.info – Reference tool for C intrinsics of all major SIMD engines
simd.info
I’m a long-time time series nerd, I’ve worked with InfluxDB, TimescaleDB, ClickHouse, and more, across everything from monitoring fleets to tracking medical devices. But recently, I started exploring RedisTimeSeries again… and I was surprised by how much the Redis Stack has evolved.
Between RedisTimeSeries, RedisJSON, RediSearch, and Streams, I realized: this could actually be the backbone for a full observability stack.
So I built rtcollector, a modular, Redis-native observability agent. It’s written in Python, configured with YAML, and designed to push system, container, and database metrics into RedisTimeSeries with labels and retention. Think of it as a Telegraf alternative, but for Redis.
Right now, I’ve implemented input plugins for: • Linux: CPU, memory, disk, I/O, network • macOS: CPU, memory, disk, I/O, network • Docker: container stats via API • Redis, MySQL, PostgreSQL
The idea is to keep it simple, extensible, and Redis-first.
Next steps: • Native logs via RedisJSON + RediSearch (already prototyped!) • Support for Redis Streams (for traces/events) • Dashboards in Grafana using the Redis data source
If you’re into observability, Redis, or just like building small purposeful tools, I’d love your thoughts or contributions. It’s early, but already useful for homelabs, edge boxes, and anyone tired of deploying 10 containers just to get CPU metrics.
Repo: https://github.com/xe-nvdk/rtcollector