When devs give a link to their twitter account, their chat, etc. they certainly wouldn't mind reading a kind personal comment from time to time.

I'd be happy to use a first-party system designed for simply saying why I like something. However I'm not willing to create a Twitter account just so I can thank someone when we've never met (and likely never will), and are likely never to speak to each other again. Same deal with signing into other services through GitHub (like gitter), that might start sending me emails (when signing in via GitHub, the service gets your email address; so far as I know, gitter doesn't use it for anything, but other services might).

I’ve seen and used issues as “thank yous”. As a developer, I don’t mind this misuse of the issues :-)

I've done that a few times, and always felt anxiety before hitting "submit". So far I've had mostly good reactions to it, but I've also had it ignored and the ticket silently closed.

Devs could allow a "this software is too good for us" issue, keep it unresolved and see how many would pile on ...

(A really cheeky issue tracker could have this built in as issue 0.)

Ignored and silent closed is not the same as negatively commented on and closed.

Thank you issues while clutter would be my favourite off topic issue to close.

Probably depends on the person. I would kinda mind that.

Isn’t that what stars are for? Not a note, but I wouldn’t Star a repository I didn’t appreciate.

Unclear, I think. I tend to use GitHub stars as bookmarks, which implies interest but not necessarily hearty approval.

I don't think you can generalize here; it's like Twitter, where some people use Likes to remember all-time favourites and some people use them as an "I've read this" checkbox.

I also use stars as bookmarks. A dedicated "appreciate" button would be nice.

F

Besides the thing sibling commenters mentioned about GitHub Stars acting like bookmarks, I also feel that GitHub Stars are more intended to be used to indicate interest in the source code itself—which is a bit different from indicating interest in the product you get by compiling said source code.

I might Star e.g. Postgres (yeah, I know, not their official repo) because someone told me that it's an example of good, elegant code, and I would like to study it. But that doesn't mean that I'm a Postgres user, let alone an adoring fan. I'm starring the code.

What a great idea! I submitted it to Github's feedback form.

The new GitHub Sponsors program is great for donating to an open source author but it requires the author to sign up.

I could have sworn that GitHub's "emoji reactions" thing applied to a repo's Releases, but I guess I was mistaken. It'd be a nice addition.

Stars?

Doesn't feel personal enough. It would be helpful to be able to express what you like about a piece of software.

That's what I use stars for anyway.

Let me pile on btw: great tool!