prometheus-connectivity-exporter VS kindle_clippings_webapp

I don't trust speedtests. There are all kinds of wrong incentives, similar to GPU benchmarks. One thing I noticed was that the data speedtest.net sends has really low entropy. It just repeats 10 bytes. If I ran an ISP I would...

So I wrote chargen2p [1] as an extension to the classical chargen protocol.

I use it together with a Prometheus exporter [2] I wrote to periodically check my laptop's connectivity. The actual check runs over Wireguard, since I didn't want to open my chargen2p server to the public. This only checks download speeds, mind you. (The chargen2p library exports upload metrics, but the exporter doesn't use it.)

My graphs tell me the average is ~5 MBps, so 40 Mbps. This is between me (Switzerland) and a Hetzner DC in Germany. speedtest.net just now claimed 160 Mbps.

[1] https://github.com/tommie/chargen2p

[2] https://github.com/tommie/prometheus-connectivity-exporter

This is the approach I use in most of my hobby projects. It's simpler, and faster and there are no loading screens.

In my kindle-clippings-manager (https://github.com/karlosos/kindle_clippings_webapp) I import highlights from Kindle and store them in localStorage. The major drawback is a size limitation (10MB). This should not be a problem in most cases but if you need to store more data then indexedDB (Web Storage) can solve the issue.

Linear (https://linear.app/) uses its sync engine to store the data in Web Storage. With optimistic updates, it feels like an offline app. You can read more about the sync engine here: https://news.ycombinator.com/item?id=36519448

Live demo • Source code

Source code: https://github.com/karlosos/kindle_clippings_webapp