the-algorithm icon indicating copy to clipboard operation
the-algorithm copied to clipboard

Lock the issues or rate limit it to people that have been using Github for at least 10+ years.

Open babuloseo opened this issue 1 year ago • 20 comments

As someone that has been using Github since 2010, I am disappointed what is going on with the issue tracker here. Maintainers take notice and do something about it.

babuloseo avatar Mar 31 '23 22:03 babuloseo

actually, "+2 years" is enough ig...

orzklv avatar Mar 31 '23 22:03 orzklv

Just need some way of rating and reporting issues by the community and the garbage will be filtered out

PKWadsy avatar Mar 31 '23 22:03 PKWadsy

I have not been on GitHub for that long (more like 2 years) and I'm not opposed.

PsychNStuff avatar Mar 31 '23 22:03 PsychNStuff

As someone that has been using Github since 2010, I am disappointed what is going on with the issue tracker here. Maintainers take notice and do something about it.

You're no fun :slightly_smiling_face: Remember, this isn't GitHub's fault, but Musk's. He clearly has no experience with open source and fired all the people who could, and it shows.

mathlover2 avatar Mar 31 '23 22:03 mathlover2

I call for at least 50 years Screenshot 2023-03-31 at 6 52 55 PM

PickleNik avatar Mar 31 '23 22:03 PickleNik

At least 5 years cmon!

venkateshamatam avatar Mar 31 '23 22:03 venkateshamatam

As someone that has been using Github since 2010, I am disappointed what is going on with the issue tracker here. Maintainers take notice and do something about it.

You're no fun 🙂 Remember, this isn't GitHub's fault, but Musk's. He clearly has no experience with open source and fired all the people who could, and it shows.

Honestly I think this is most accurate objectively speaking

PsychNStuff avatar Mar 31 '23 22:03 PsychNStuff

9fc

what the hell

mmmpop avatar Mar 31 '23 23:03 mmmpop

As someone that has been using Github since 2010, I am disappointed what is going on with the issue tracker here. Maintainers take notice and do something about it.

You're no fun 🙂 Remember, this isn't GitHub's fault, but Musk's. He clearly has no experience with open source and fired all the people who could, and it shows.

How is shitposting on GitHub instead of Twitter exactly Musk's fault? Or fun while we're at it?

TomasTokaMrazek avatar Mar 31 '23 23:03 TomasTokaMrazek

9fc

    [
      
    
        ![9fc](https://user-images.githubusercontent.com/54904227/229246570-c3844547-fc1f-40c1-89b7-b0d5a4051c39.gif)
      ](https://user-images.githubusercontent.com/54904227/229246570-c3844547-fc1f-40c1-89b7-b0d5a4051c39.gif)
    
    
      
        
          
        
        
          
          
        
      
      [
        
          
        
      ](https://user-images.githubusercontent.com/54904227/229246570-c3844547-fc1f-40c1-89b7-b0d5a4051c39.gif)

what the hell

by replying to it, you're only making it show up twice as often and ofc, i'm gonna reply to you, so that'd be 3x! :)

Lamby777 avatar Mar 31 '23 23:03 Lamby777

As someone that has been using Github since 2010, I am disappointed what is going on with the issue tracker here. Maintainers take notice and do something about it.

Quality over quantity

(As in, you may have been on Github since 2010, but that doesn't make you good quality)

akamicah avatar Mar 31 '23 23:03 akamicah

Why should github give special treatment?

darkwraithcovenant avatar Apr 01 '23 01:04 darkwraithcovenant

divination

Before you bitch at me, I am talking about the issue on the spam, it's so energetic and memey I had to have fun as well.

FREE ALL THE CODE, OPEN SOURCE ALL THE CODE. BE A CHAD DEV.

babuloseo avatar Apr 01 '23 02:04 babuloseo

As someone that has been using Github since 2010, I am disappointed what is going on with the issue tracker here. Maintainers take notice and do something about it.

You're no fun slightly_smiling_face Remember, this isn't GitHub's fault, but Musk's. He clearly has no experience with open source and fired all the people who could, and it shows.

How is shitposting on GitHub instead of Twitter exactly Musk's fault? Or fun while we're at it?

Twitter could have had a proper system in place for managing the issues and pull requests, with an appropriate amount of manpower allotted for that. They could have had someone running this who knew how GitHub worked. Heck, they could have put some restriction on access beforehand.

Instead, they uploaded the code to GitHub and got immediately hit with a huge wave of criticism that they could not handle with their manpower. Furthermore, when they realized that some of the code was embarrassing, they decided to remove that code with another commit, not realizing that a) the commit history exists b) people have already forked the repository and c) you can download GitHub repositories to your computer.

Normally, Twitter would have been able to handle this because of competent open-source experts at the company ... except Musk laid them all off. So instead we have Twitter releasing the recommendation source code in the most bungled manner possible, getting flooded with shitposts, and simultaneously demonstrating that whoever is in charge (Musk and whoever he put at the head of this) doesn't know Git.

mathlover2 avatar Apr 01 '23 03:04 mathlover2

As someone that has been using Github since 2010, I am disappointed what is going on with the issue tracker here. Maintainers take notice and do something about it.

You're no fun slightly_smiling_face Remember, this isn't GitHub's fault, but Musk's. He clearly has no experience with open source and fired all the people who could, and it shows.

How is shitposting on GitHub instead of Twitter exactly Musk's fault? Or fun while we're at it?

Twitter could have had a proper system in place for managing the issues and pull requests, with an appropriate amount of manpower allotted for that. They could have had someone running this who knew how GitHub worked. Heck, they could have put some restriction on access beforehand.

Instead, they uploaded the code to GitHub and got immediately hit with a huge wave of criticism that they could not handle with their manpower. Furthermore, when they realized that some of the code was embarrassing, they decided to remove that code with another commit, not realizing that a) the commit history exists b) people have already forked the repository and c) you can download GitHub repositories to your computer.

Normally, Twitter would have been able to handle this because of competent open-source experts at the company ... except Musk laid them all off. So instead we have Twitter releasing the recommendation source code in the most bungled manner possible, getting flooded with shitposts, and simultaneously demonstrating that whoever is in charge (Musk and whoever he put at the head of this) doesn't know Git.

Sums up this whole repo's situation. Cheers.

Lamby777 avatar Apr 01 '23 04:04 Lamby777

Screenshot 2023-04-01 at 1 04 22 AM this is a certified Twitter moment

PickleNik avatar Apr 01 '23 05:04 PickleNik

Screenshot 2023-04-01 at 1 04 22 AM

this is a certified Twitter moment

You've heard of "this conference call could have been an email." Now, get ready for "this GitHub Issue could have been a Twitter thread."

Lamby777 avatar Apr 01 '23 08:04 Lamby777

ratio

Jerrynicki avatar Apr 04 '23 10:04 Jerrynicki

Gotta add 10 years of GitHub experience to my bio now!

montw-dev avatar Apr 13 '23 05:04 montw-dev

@babuloseo nerd-emoji-nerd

ghost avatar Aug 21 '23 23:08 ghost