Live data from Hacker News

GitHub Star History Graph

star-history.com

31–40 of 79 posts

Re: GitHub Star History Graph

#31
post #29

I get many stars on my last project but no issues or PR. It feels quite lonely and, more importantly, I can't know if my work is going in a good direction. I think people mainly use stars as bookmark.

Is there an established way that people advertise their open source projects to developers for help? I know that GitHub has exploration features but when I last used them it felt like looking for a needle in a haystack.

Re: GitHub Star History Graph

#32
post #11

For me, stars have an inverse correlation with actual usage. I'll star projects I want to look at some day, because they seem cool, like Svelte or Vite. But projects I work with daily, I don't need to star them to remember they exits, like React or Webpack.

For every professional React developer, there's probably ten people who consider React cool and something to learn in the future, while they haven't even heard about Svelte or Vite.

Re: GitHub Star History Graph

#33
post #29

I get many stars on my last project but no issues or PR. It feels quite lonely and, more importantly, I can't know if my work is going in a good direction. I think people mainly use stars as bookmark.

I recommend adding telemetry to your project for this (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 :)

All telemetry logic in OctoSQL is actually contained in a single short file[1].

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 on every invocation 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

[1]:https://github.com/cube2222/octosql/blob/main/telemetry/tele...

Re: GitHub Star History Graph

#34
post #26
post #22

Earlier quoted context omitted.

I’m with you on minimal, 100% anonymous, and aggregated, but why does the data need to be open to the public to not be spying? Genuinely curious, you’ve clearly thought about this a lot.

There are only two reasons it would need to be private: (1) you're collecting data where if it was public, people would be outraged. That's spying. (2) you believe the data is anonymous and valuable, but only you / your group should benefit from the insights it provides. You're afraid someone else is going to 'take your ideas' and execute them better than you can. Point 1 is ethically wrong, in my view. Point 2 is no…

Someone saving all the letters you have written them isn't spying on you, you have just been careless to write down so many private things.

The easier way is to assume all signals emitted by your computer are being consumed somewhere (Hey CIA friends!) and not emit anything you don't want detected.

Re: GitHub Star History Graph

#35
post #29

I get many stars on my last project but no issues or PR. It feels quite lonely and, more importantly, I can't know if my work is going in a good direction. I think people mainly use stars as bookmark.

I recommend adding telemetry to your project for this (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 proc…

Octosql looks very cool! Thanks for posting.

Also agree with you about telemetry. We send some minimal telemetry in Robusta (also easily disabled) and it's been a big help for us as a project.

https://github.com/robusta-dev/robusta

Re: GitHub Star History Graph

#36
post #7

Slightly related, but... what is it with stars? I've never starred a repo and don't understand why I would want to. Yet it seems to be a popularity contest people care about for some reason, even though it correlates strongly with forks/issues/prs so you get the same idea about usage from those. Does it go at all beyond a "like", or am I just too old to get it?

GitHub recently added a feature where you can organize your stars in lists, so you decide what they mean. My lists include for example "useful CLI tools", "languages", and "projects to contribute to". Outside of this feature, I mostly use the stars as a 'like' button.

Re: GitHub Star History Graph

#37
post #29

I get many stars on my last project but no issues or PR. It feels quite lonely and, more importantly, I can't know if my work is going in a good direction. I think people mainly use stars as bookmark.

I recommend adding telemetry to your project for this (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 proc…

do you warn users about the telemetry? OSS users and developers in particular are pretty hostile to it, especially when it's default

Re: GitHub Star History Graph

#38
post #29

I get many stars on my last project but no issues or PR. It feels quite lonely and, more importantly, I can't know if my work is going in a good direction. I think people mainly use stars as bookmark.

Is there an established way that people advertise their open source projects to developers for help? I know that GitHub has exploration features but when I last used them it felt like looking for a needle in a haystack.

Not that I know of. Especially for C. I resorted to re-post to reddit when I reach a subjective milestone but the returns are slim. Also I hear people may dislike such an auto-promoting endeavour...

First time I posted an early naive version of my string lib, the thread became a deluge of 500+ reactions and constructive advice. Subsequent submissions with a much better work got me depressed.

Re: GitHub Star History Graph

#39

Earlier quoted context omitted.

I recommend adding telemetry to your project for this (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 proc…

do you warn users about the telemetry? OSS users and developers in particular are pretty hostile to it, especially when it's default

Please judge for yourself in this asciinema I've just uploaded whether it's enough of a warning: https://asciinema.org/a/eWQsyXQKi1fmithyTekAD5fWS

Re: GitHub Star History Graph

#40
post #22
post #13

Earlier quoted context omitted.

In my opinion, analytics should be minimal, 100% anonymous, aggregated, and open to the public - otherwise it’s spying. I use a self-hosted Plausible analytics server to implement this[0] across all my websites, so it's all public and you get to see exactly what I see[1][2]. [0] https://hexops.com/privacy/ [1] https://opendata.hexops.com/devlog.hexops.com [2] https://opendata.hexops.com/machengine.org

I’m with you on minimal, 100% anonymous, and aggregated, but why does the data need to be open to the public to not be spying? Genuinely curious, you’ve clearly thought about this a lot.

If the data is public, you're instantly able to be held accountable for the data you're collecting. Others can determine if you are doing something privacy invasive, intentionally or inadvertently.

Public analytics therefore help ensure and demonstrate your analytics are ethical.

Post reply on HN