News for hackers. Stuff that matters.

A comment on A uBlock Origin update was rejected from the Chrome Web Store. Parent comment

Re:A uBlock Origin update was rejected from the Chrome Web S... by tomxor on Saturday October 12, 2019 @12:35PM (#21234391)
> I wonder if it's been on purpose or just, as always, their automatic algorithms being imposible to contest when they're wrong.

Further down the github issue, another person attempts to submit the same build recieving the same response. But then asks for clarification on the applicability to uBlock only to receive an excerpt from ToC bundling advice...

Pretty sure this is not algorithmic. As the dev said they are being stone walled.

[ Parent | on HN ]
Re:A uBlock Origin update was rejected from the Chrome Web S... by unicornfinder on Saturday October 12, 2019 @12:58PM (#21234542)
Indeed. A friend of mine used to work on YouTube's moderation team. Turns out a lot of the "algorithm" is actually humans, hiding behind the shield of automation.
[ Parent | on HN ]
Re:A uBlock Origin update was rejected from the Chrome Web S... by behnamoh on Saturday October 12, 2019 @03:32PM (#21235633)
This scares me a little as "it was algorithm's fault" seems to be a good excuse for tech companies to get away with their monopolistic behavior. A few years down the road and they'll blame "AI" for the misconduct.
[ Parent | on HN ]
Re:A uBlock Origin update was rejected from the Chrome Web S... by YeGoblynQueenne on Saturday October 12, 2019 @01:22PM (#21234694)
Do you mean this post?

https://github.com/uBlockOrigin/uBlock-issues/issues/745#iss...

That's the developer relenting and trying to resubmit, after fuming at one of their users suggesting to do so. The reply they get is the same as the original reply, including the ToS (right? Not "ToC") but excluding the bit about risking being banned if the same vilation occurs multiple times. It still looks like an automated reply though.

[ Parent | on HN ]