Live data from Hacker News

We lost 54k GitHub stars

httpie.io

641–650 of 697 posts

Re: We lost 54k GitHub stars

#641

Okay. I just went in and double checked. 600+ comments bashing Github for not having prevented this action. Meanwhile, Github: 1) has this action in the "danger zone", literally the only UI element using RED COLOR; 2) has a warning banner on the dialog box that pops up when you click that button; 3) requires you to type in the name of the repository (which everyone copies and pastes anyway because they don’t get the…

Where did you find those §600+ comments bashing Github for not having prevented this action"?

Re: We lost 54k GitHub stars

#642
post #641

Okay. I just went in and double checked. 600+ comments bashing Github for not having prevented this action. Meanwhile, Github: 1) has this action in the "danger zone", literally the only UI element using RED COLOR; 2) has a warning banner on the dialog box that pops up when you click that button; 3) requires you to type in the name of the repository (which everyone copies and pastes anyway because they don’t get the…

Where did you find those §600+ comments bashing Github for not having prevented this action"?

Of the 600+ comments here, the vast vast majority is contemplating how github could improve it’s UI and UX so that nobody loses a star ever again.

Re: We lost 54k GitHub stars

#643
post #422

Earlier quoted context omitted.

It’s also possible that they did consider it, but upon investigation it entailed more work than they could justify. I do think including more context about what will be destroyed by the action would be great, and probably pragmatic, but… If typing out the name of the repository isn’t enough, providing context might not be either. The more I think about it, the more it seems like one of those “Whatever, we’ve got a mi…

They're owned by Microsoft and funded/now led by by Nat Friedman. They can justify a lot.

No doubt, and I’ve never worked on a team with these kind of resources so I can’t be certain either. I’m just advocating for the people at GitHub and casting doubt that it’s trivial to avoid situations like this or resolve them.

Re: We lost 54k GitHub stars

#644
post #551

Earlier quoted context omitted.

“I accidentally made a repo private, which resulted in all of its stars being removed.”

From the post: > Due to an unfortunate sequence of events, I accidentally made the project’s repository private for a moment. And GitHub cascade-deleted our community that took 10 years to build. This reads the same, to me, in terms of cause and effect.

I swear there's something in the water. This entire thread has a ton of nastiness/bitterness in it.

Re: We lost 54k GitHub stars

#646
This hackernews post and other media coverage is getting the job done. Yesterday I saw they were at 3.2K stars, and right now they are 8.7 stars. I suspect this event will get them more users and will turn out better for them in the long run.

Re: We lost 54k GitHub stars

#647

Earlier quoted context omitted.

Stars on GitHub are huge in open source. 54,000 stars is a big deal and puts your project into a super-elite category.

If it’s such a big deal then why is GitHub not intervening to help a “super-elite” tier of project? Devs retconned the concept of a like onto a star. That doesn’t mean they are the same thing.

> If it’s such a big deal then why is GitHub not intervening to help a “super-elite” tier of project?

That's why this is a #1 post.

> Devs retconned the concept of a like onto a star. That doesn’t mean they are the same thing.

Yes, the semantics are ill-defined.

Re: We lost 54k GitHub stars

#648

Okay. I just went in and double checked. 600+ comments bashing Github for not having prevented this action. Meanwhile, Github: 1) has this action in the "danger zone", literally the only UI element using RED COLOR; 2) has a warning banner on the dialog box that pops up when you click that button; 3) requires you to type in the name of the repository (which everyone copies and pastes anyway because they don’t get the…

I'd recommend reading the actual post carefully before claiming to having double checked anything and then going on judging using harsh language. You completely missed the 54k stars question presented and the context in which it was presented to the op.

Re: We lost 54k GitHub stars

#649

Earlier quoted context omitted.

Stars on GitHub are huge in open source. 54,000 stars is a big deal and puts your project into a super-elite category.

What concrete benefits does a project get from having lots of stars? I'm not disagreeing with you, I'm just wondering what the stakes are, since I don't have a lot of open source background myself.

I'm not sure if there is a fixed universal set of concrete benefits. It probably varies from project to project and the people involved.

Re: We lost 54k GitHub stars

#650

>"The same goes for stars. If you’re one of those 54K people who’ve starred the repo any time in the past decade, the repo is no longer among your starred projects." // This seems like bad design from a UX perspective. Projects I star are a characteristic of my account. If a project is made private, I still want to have the star in my account list; it feels almost like gaslighting to just remove a star.

>Projects I star are a characteristic of my account. What about deleted repos? Should those be maintained as well?

I wasn't thinking the repo would be maintained beyond the title (and short description, maybe whole readme?) being in a list of starred repos, and maybe having something like "[now private]" or "[removed]" added.

If I know I starred a repo and then go back to it and it's no longer accessible, I want to see that I'm not going mad and have some information about why the repo is no longer accessible.

Post reply on HN