Gregory's Server"Like and subscribe!" has come to GitHub https://github.com/daeuniverse/dae/issues/368#issuecomment-1859984256
|
bert hubert 🇺🇦🇪🇺
30 comments
Franziska Köppe | madiko
@bert_hubert interesting approach to involve the community into further development(s). 🤔 
Rihards Olups
@madiko @bert_hubert It’s not involvement, it’s gaming the GitHub “starring” feature. Basically makes the repo stars useless.
Franziska Köppe | madiko
@richlv // cc @bert_hubert 
Bodhipaksa
@hnapel Thank you. The post you're replying to is the most perfect piece of sealioning I've ever seen.
Franziska Köppe | madiko
I love the fediverse. Just learned a new terminology: "sea lioning" (didn't got it from the link to the wikipedia article of sea lions though): Thank you!
Pēteris Caune
@madiko @richlv @bert_hubert from a HN comment thread: """This cheats the other users (like me or you) -- if we are looking at the project's star count, you are likely trying to judge project's popularity and get a measure of how many people like it. And dae's star count is basically a lie - it does not represent how many people liked it, but rather how many people had found annoying bugs in it. [...] And as you said, other projects who don't have this practice are in disadvantage."""
Rihards Olups
@cuu508 @madiko @bert_hubert And to be pedantic, it's gaming the system, not gamification - the latter is more often associated with something positive, like StreetComplete introducing small gamification elements in mapping. Gaming the system harms other users and makes the metric useless, so Github could as well drop "starring" now.
Franziska Köppe | madiko
Thank you very much for sharing your thoughts. I had a "feeling" grumbling in my stomach (that is why I wrote "intresting" with the thought-face behind it 🤔) But I could not put a finger to name my grumbling. It makes sense to me, what you are writing. From my experience in moderating and supporting an engaged open source community I share your experiences. Recently we wondered how to "know what peeps need". It's not easy to know. The blind spot is huge.
Gytis Repečka
@bert_hubert Oh wow, that is so toxic 🤯 Refusing issues because reporter did not like-comment-subscribe (in this case ⭐️) could be turning point for users to realize - GitHub is just like proprietary social media 🧐
Lauma Pret 🕸️
@bert_hubert @richlv
Rihards Olups
@laumapret @bert_hubert 
weilawei
@bert_hubert EWONTFIX is supposed to be a gibe at maintainers who ignore their users, not a manual...
JRSofty
@bert_hubert that's really sad. Of course if it's open source, you can maybe find a fork and see if they have fixed your issue. Or if you know the programming language then you could always make your own fork, and correct it.
RMcNeely
@FlagrantError @bert_hubert just in case there's any confusion about them farming engagement for the stat aggregators out there they made it very clear. 
🔗 David Sommerseth
@bert_hubert They seem to have dropped that. It even looks like a GH ToS violation 
Sir David Nielsen
@bert_hubert @cstross if you like this code, then smash that star button and watch as GitHub turns your email into useless goo.  
Fish Id Wardrobe
@SenseException @bert_hubert They already got something – a report of a possible bug in their software, for free
RMcNeely
@bert_hubert well that's gross. Thanks for helping to call behavior like this out. Short of GH changing its terms for things like this, the community strongly rejecting this behavior as socially acceptable might be the best we can do. 
Benjamin
@bert_hubert Someone make a bot that stars that crappy project and auto-reposts every thusly closed report under its own name. Who the F*CK looked at this and thought: This is good! |
@bert_hubert How wonderful.