I actually find that hugely helpful that so many people are actually actively expressing they are hitting this. It's not easy to be able to get an idea what issues people are actually hitting with anything you have made. An issue being bumped with essentially "me too" is a highly valuable signal.
That's why github added emoji reactions many years ago, so you can express "me too" without spamming the notification systems.
https://github.blog/news-insights/product-news/add-reactions...
[flagged]
It is a button that let's people say "me too". It really doesn't matter if it is labeled with a thumbs-up emoji, the text "me too" or Rick Astley dancing. Don't think you are better than others because you are too "proud" to click a button with a thumbs up image on it.
Emoji being associated with infancy is a thing that only exists in your brain and only because young people were early adopters of emoji about 15 years ago. Emoji are just as valid a means of communication as any other.
It's definitey not only in their brain, it's in my brain, too.
On a related note: Emoticon > Emoji.
Bring back B~), get rid of those silly newfangled unicode monstrosities.
Element and discord and the Samsung default keyboard try to :coloncode: any emoticons you type.
This is on desktop and mobile, since the two apps are electron.
\>. <
Good thing I don't use Element as my Matrix preferred client. Discord and all Samsung software are more or less indistinguishable from spyware the way I see it, as most closed-source proprietary software is. That's a major if not primary reason why it's closed source: it's doing naughty stuff against the interests of the user that the developers want to conceal from their victims.
It doesn't matter how many other people prefer to throw their own privacy off a cliff, irrational and self-harming group conformity concerns don't afflict me the way they seem to afflict neurotypical people. One of the blessings of being on the spectrum.
The point is that for the typical older HN denizen, emojis were legitimately a sort of counterculture element associated with trivial conversations in the counterculture of our youth.
That's not what they are anymore. They have a rich meaning - ask a young person what :) means and you'll have your example.
Emojis are, like it or not, part of the lexicon now.
You can use whatever dialect of language that you want. I'll keep using the same as the people commenting above, which doesn't include emojis.
>typical older HN denizen, emojis were legitimately a sort of counterculture element associated with trivial conversations in the counterculture of our youth.
Emojis didn't exist in the youth of the typical older HN denizen. They are the exclusive purview of Gen Alpha, Gen Z, and younger millennials.
I think emojis are easily overused, but I certainly don't mind when they're used to convey simple, universally understood meaning (such as reacting with a "me too" in a bug report).
Stuff like gitmoji, though, drive me nuts. Talk about ambiguous and easily misused. Faster for everyone if you just say what you mean.
Maybe then GitHub should add a text-based expression for people like you.
Like Google does in Gmail, where you can turn off the icons for the "archive", "report spam" actions so that the text is shown instead.
I'm sure this would add a lot of value to GitHub /s
Or you ask your OS vendor (or each website operator) to also ship an optional set of emoticons with less childish images. Start a petition and I'll sign it.
I very rarely use emojiis on github. If I can't add anything to the discussion / issue, I post nothing. So if there's enough people like me, an issue can languish.
However the barrier to entry for a lot of issues reporting is pretty tall - requiring triplicate documentation of everything. It's like an overreaction to the sort of people that need to be told to unplug something for 30 seconds to continue the support call.
And that's if they even "allow" issues.
I was posting in issues note frequently 1-3 years ago. I'm sure I'd be sheepish about some posts.
Do you really think the maintainers don't understand that "doesn't work with Python 3.13" isn't going to affect tons of people?
There's some bozo asking "any news? I cant downgrade because another lib requirement" just two days after the maintainer wrote several paragraphs explaining how difficult it is to make it work with Python 3.13. This adds no value for anyone and is just noise. Anyone interested in actual useful information (workarounds, pointers on how to help) has to wade though a firehose of useless nonsense to get at anything remotely useful. Any seriously discussions of maintainers wanting to discuss things is constantly interrupted by the seagulls from Finding Nemo: "fix? fix? fix? fix? fix?""
Never mind the demanding nature of some people in that thread.
Just upvote. That's why this entire feature was added.
After seeing "Jigar Kumar" cognitive exploits on xz mailing list a maintainer would be excused (and I'd even say, encouraged) to just ignore pressure tactics altogether. It's an open source project - if it works great, if it breaks, you get to keep both pieces.
To the non-technical founder, this is doing something.
They will not move to ~~mocking up~~ sketching a wireframe of something.
>Do you really think the maintainers don't understand that "doesn't work with Python 3.13" isn't going to affect tons of people?
I had trouble parsing this sentence. Claude simplified it for me as follows. AI to the rescue!
"Do you really think the maintainers fail to realize that Python 3.13 compatibility issues will affect many people?"
Reactions, though.
It’s not just that, it’s people commenting “this is unacceptable” and “I hate this library” that add very little value.
Also, you can upvote issues as well / leave reactions without leaving comments. It ensures a better signal:noise ratio in the actual discussion.