Live data from Hacker News

We lost 54k GitHub stars

httpie.io

361–370 of 697 posts

Re: We lost 54k GitHub stars

#361
post #208

Earlier quoted context omitted.

And another that it was made public again. Or neither, and just not delete shit that there was no need to delete.

The user said "delete this stuff". GitHub asked, "Are your sure?" User: "Yes". Seems like a good reason to delete it.

No. The user said, "make it private". That has nothing to do with deleting anything.

Re: We lost 54k GitHub stars

#362

>There’s a confirmation box. It’s designed to stop users in a situation like mine from doing something stupid. It tells you that “You will permanently lose all stars and watchers of this repository.” That’s pretty scary. >The problem is that the box looks exactly the same for repos with no commits and stars and for repos with a decade-long history and 55k stargazers and watchers. And it says “Warning: this is a poten…

They admitted exactly what they did. This experience is still really bad UX IMO.

Re: We lost 54k GitHub stars

#363
post #181

Earlier quoted context omitted.

I mean "refused to". There was absolutely no value to Microsoft in refusing to restore the deleted information, and there was no practical reason to have deleted it at all. Ultimately, it just amounts to contempt.

"I screwed up. By the way, it's your fault. I hope you realize how many people think more highly of your service because my project is there. Why wont you accept some money for a service you don't provide?" What's the value in capitulating to that? Also, a user saying "delete this stuff" is a pretty practical reason to do so. Indifference != contempt.

Define the difference.

Re: We lost 54k GitHub stars

#364
post #339

This is horrible -_-!!! But I wonder what would happen to GitHub Discussions in this situation? I now 100% feel necessary to build a Discord channel for OSS projects.

Please don't use discord, use gitter or something else which itself is open source

Re: We lost 54k GitHub stars

#365
I find it ironic that some people are blaming the author so bad given that Github has made the same mistake in the past and had to restore it from the backup, making it clear that the UX could be better.

I get it, we should all be very cautious when doing destructive actions, but it's also specially easy to be confused by github's repository naming conventions and you're not seeing the actual repository you're making private, just it's name.

Re: We lost 54k GitHub stars

#366

Earlier quoted context omitted.

I specifically dislike the "Lessons" section, as it throws all the blame on github and doesn't mention the seemingly obvious advice: "make sure you're not on autopilot when taking potentially dangerous actions, on github or any website". Yes, GitHub probably should show the stars in the warning UI, and hopefully that will prevent some of these mistakes. But GitHub makes it pretty hard to make this mistake already - t…

I suggest you read "The Field Guide to Understanding 'Human Error'". You'd learn a lot. https://www.amazon.com/Field-Guide-Understanding-Human-Error... My view is that expecting humans to stop making mistakes is much less effective than fixing the systems that amplify those mistakes into large, irreversible impacts.

Is that book still worth to spend time reading if I do understand what you are saying and I hold the same views? I'm always hungry to learn something useful from books, but more often than not I find these hyped books ("The Checklist Manifesto" comes to mind) really annoying in that they make me spend a significant amount of time reading stupid "curious life stories" to bring across a point that can be expressed in a 3 word sentence, like "checklists are good". And it's even worse when these are trivial truths most sane people would agree on, which doesn't make the "advice" more actionable, because it's just much easier said than done.

I mean, it would be disappointing to read it to find it summarizes exactly to what you just said.

Re: We lost 54k GitHub stars

#367
post #310

Earlier quoted context omitted.

What could the author have done with this post that would take it from being “blaming” into “giving feedback in an earnest intent to save others future pain”?

Acknowledge their own agency and responsibility. Literally stop blaming with language like “GitHub deleted…”

How would you word that sentence and remain factual about the deletion?

Re: We lost 54k GitHub stars

#368

Earlier quoted context omitted.

What could the author have done with this post that would take it from being “blaming” into “giving feedback in an earnest intent to save others future pain”?

Drop passive aggressive comments like the one about how they're going to stop wearing their GitHub T-Shirt because of how GitHub subjected them to the same treatment that lesser and more unworthy projects would have received. Even using words like "future pain" is pretty crazy. "We lost 54k GitHub stars"? They're imaginary internet points! Cope.

It sounds like you are ok with the post, except for the one sentence before the epilogue?

Re: We lost 54k GitHub stars

#369
> We even offered GitHub financial compensation for any resources required

What? Can anyone explain this? Are people so desperate about github stars these days that they’re willing to pay Microsoft for them?

Re: We lost 54k GitHub stars

#370

Earlier quoted context omitted.

I’m curious which statements from the article carried that tone?

I think in the "But theres a confirmation box, right?" and if I had to quote a portion I'd quote >>"To paraphrase, the box tells you “You’re about to demolish a house. If there are any people inside, they will all die”. But it doesn’t include anything specific to break you out of your auto-pilot mode if you’ve confused the address and think you’re looking at an empty house." >>"The dialog should be more contextual an…

Thank you for quoting. I see where you’re coming from - the comparison to killing people is pretty hyperbolic.

Do you agree that, hyperbolic metaphors aside, the UI improvement suggestion is a good one?

Post reply on HN