GitHub has not removed malicious imitation software after 3 weeks(successfulsoftware.net) |
GitHub has not removed malicious imitation software after 3 weeks(successfulsoftware.net) |
Moral of the story. If you want even the most basic level of support from Github, you need to get on the front page of HN first.
And it seems they are able to do things very quickly, when they want to. Bastards.
This also works for Google support.
> And it seems they are able to do things very quickly, when they want to. Bastards.
I wouldn’t chalk any of this up to malicious intent. I’m sure they are swamped with such requests.
It was already a problem before agents could automatically perform these actions.
And it’s not something you can really automate on their end either. At least not the judgement call on the removal. Imagine if there was a fully automated process and it inadvertently took down a legit project.
Stalling in the hope that reporters won't escalate, instead of allocating a tiny bit of their billions in profit to hiring for this, is malicious in my book.
They just don't want to. Not malicious, just ignorant and disrespectful of their users.
Then maybe they should be growing their customer support capacity along with their business. It drives me crazy how big companies have normalized cutting those departments down to anemic proportions. Especially those where you're a paying customer.
It's malice from whoever is responsible for under-staffing. It's also malice to prioritize the squeaky wheel for optics; it's intentional to reduce the spread of the knowledge of how unresponsive they are.
Just seems like a silly rational response to the same problem.
I think the likelihood GitHub did something within 10 minutes of a post appearing on HN's front page is approximately zero.
Nobody in GitHub Trust & Safety is sat there watching HN.
An executive or communications professional who might have heard it got on HN, or seen it appear in a tool monitoring Microsoft and GitHub's mentions across the internet, and who then flagged the post, Trust & Safety would probably spend *more than 10 minutes* noticing the email or Teams message, then trying to find the right ticket internally. Then after locating the ticket you still have to investigate the facts, discuss, and click buttons to ban/delete the user.
It's (much) more likely this sat in a queue until someone got to it and the timing of it being on HN is a complete coincidence.
https://lowendbox.com/blog/will-github-ever-remove-this-null...
Not the worst thing in the world, they're easy to spot, but I'd like to see GitHub invest more time in protecting their users from falling victim to these bad actors.
There's an impersonation profile of me on Github (username happyhannob). I've reported it a while ago, received the same automated message, and no reaction otherwise. It's still online.
I guess you can't expect basic fraud prevention from a company currently building the future with AI...
Open source code is still copyrighted. What the license defines is rights that people have in distributing that code. If an unofficial repository is using open source code to ship malware, and the license that software had didn’t allow that, then the unofficial repository is still breaking copyright law despite the code being open source.
EDIT: e.g. https://www.mozilla.org/en-US/foundation/trademarks/policy/
"Show me the incentive and I'll show you the outcome."
It's not illegal to send an incorrect one by mistake but GitHub probably won't process it. It's illegal to send an incorrect one intentionally. Now that it's been pointed out to you that making malware isn't a copyright violation, it's intentional if you send a DMCA anyway.
There’s no need for benefit of the doubt when it comes to the level of support provided by tech companies.
Bad support by tech companies is a conscious profit-preserving choice.