-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
signal-cli
signal-cli provides an unofficial commandline, JSON-RPC and dbus interface for the Signal messenger.
-
Healthchecks
Open-source cron job and background task monitoring service, written in Python & Django
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
mailrise to Telegram, or straight Telegram bot for services that support it.
I do really like https://github.com/fabianonline/telegram.sh
This is a wrapper on signal-cli (https://github.com/AsamK/signal-cli)
I do also value simplicity and compactness, and try hard to limit the number of dependencies the project uses. If you look at requirements.txt, there are relatively few direct dependencies. When I add or upgrade dependencies, I also check what the code quality looks like, how active is the maintainer, what unresolved issues the project has, and so on. For example, I did a bunch of testing on croniter, which resulted in a number of filed issues, PRs from me, and, ultimately, my reimplementation of the library. Of course I cannot guarantee there are no vulnerabilities in the dependencies.
I do also value simplicity and compactness, and try hard to limit the number of dependencies the project uses. If you look at requirements.txt, there are relatively few direct dependencies. When I add or upgrade dependencies, I also check what the code quality looks like, how active is the maintainer, what unresolved issues the project has, and so on. For example, I did a bunch of testing on croniter, which resulted in a number of filed issues, PRs from me, and, ultimately, my reimplementation of the library. Of course I cannot guarantee there are no vulnerabilities in the dependencies.
I do also value simplicity and compactness, and try hard to limit the number of dependencies the project uses. If you look at requirements.txt, there are relatively few direct dependencies. When I add or upgrade dependencies, I also check what the code quality looks like, how active is the maintainer, what unresolved issues the project has, and so on. For example, I did a bunch of testing on croniter, which resulted in a number of filed issues, PRs from me, and, ultimately, my reimplementation of the library. Of course I cannot guarantee there are no vulnerabilities in the dependencies.