GitHub Star History Graph

1

star-history

I am the maintainer of star-history.com. Thanks for posting this on HN. Just to share a trick, you can also use markdown to embed a live star history chart to your GitHub README. e.g. ## Star History [](https://star-history.com/#bytebase/star-history&Date) Instruction: https://star-history.com/#bytebase/star-history&Date Enjoy~.

#Productivity #Open Source #Growth Hacking 26 social mentions

2

OSSInsight

We are building a similar tool https://ossinsight.io/ which saves nearly 45B events from GitHub and can let you get more powerful insights from the project, e.g here is the history insights for K8s https://api.ossinsight.io/share/9825e242-4ec4-49b1-9c7a-c5baa134e7e9, enjoy it by yourself :-).

#Open Source #Productivity #Developer Tools 14 social mentions

3

OctoSQL

I recommend adding telemetry to your project (and I know a lot of people feel strongly about this, so I'll add: with a very easy way of disabling it). In OctoSQL[0] I'm literally just sending JSON files with coarse information about 1. Invocations of the CLI, 2. Features used in these invocations, to a VM on DigitalOcean (with a 10-line server receiving them and writing to a JSON file - which I can then process using OctoSQL itself). Thanks to this I knew that until recently most of what I had were stars, not actual usage, and could also see how the big rewrite I released in January (and the following updates) made a lot of people start actually using it since. Very nice feeling :) PS: Keep in mind that https requests take a long time, as they need to do a few roundtrips for the TLS handshake. Don't do that if you have latency-sensitive invocations. I.e. In OctoSQL I'm only sending aggregated telemetry data every 10 invocations (as well as on the very first one). [0]:https://github.com/cube2222/octosql.

#Databases #Big Data #Relational Databases 22 social mentions