lorikeet VS pinging

Very cool! Reminds me of my tool lorikeet, although not parallel by default (which can be a good thing)

I added simple webhook support in lorikeet for slack. We use it to receive alerts when some stuff has gone wrong.

Looks great! I made a similar general purpose cli tool for things like this called lorikeet.

I've seen issues in lorikeet's http step does not ever return & this was related to a timeout of the http request. In a newer version I set the default timeout to 30 seconds to alleviate this issue.

Whatever you feel like building, scratch an itch. I started with simple tools that I had personal pain points for, like collating markdown documents or having a way to run lightweight smoke tests. In my spare time I'm now working on a scuba diving database and map.

The website does other tests besides web pings. You can read more details on the about page. It is all open source on github.

pinging.net uses Axum and is open source. Axum is connected directly to the internet (i.e. no nginx-like proxy) and it has worked well with very few issues. Axum is also handling the http to https redirect as well as the www subdomain normalization all in a single binary.

Thanks for the FYI. I hadn't heard of that extension before. I'll see if I can display a helpful message if the extension is installed (or maybe more generally if Web RTC connections are blocked for other reasons if I can). Tracking the issue here

GitHub link: https://github.com/benhansenslc/pinging