Live data from Hacker News

Let's guess what Google requires in 14 days or they kill our extension

blog.pushbullet.com

791–800 of 811 posts

Re: Let's guess what Google requires in 14 days or they kill our extension

#791
post #561

Earlier quoted context omitted.

After 2nd to 3rd rejection if it will require a human to intervene Google will have to hire half the earthlings to deal with crappy spammers that will simply spam google store with their extensions. The answer is not human interaction, the answer is automation tool to give more details as what was detected and didn't pass.

> the answer is automation tool to give more details as what was detected and didn't pass And then Google will have to hire half the earthlings to write all the special-case code into the automation tool...

why? current automation tool is a boolean exit. You either pass or not. Just expose *current tool logic.

No other hiring required for this

Re: Let's guess what Google requires in 14 days or they kill our extension

#792
post #226

Earlier quoted context omitted.

Had the same problem when I made a fairly successful app in university. Whole account got deleted for a “3rd strike” meaning “3rd resubmission.” I’ve made a new account and their AI black box still doesn’t realize it’s me...

By whole account deleted do you mean your Chrome dev "account" or your Google account including Gmail, Gcal, and YouTube? The latter is my greatest fear.

My play store dev account was deleted, but my gmail and everything was fine. Good thing because I had a lot on there.

To get back to the store I created a new account with a different name. But then google took down my apps because their bots said I was impersonating “Joe Hinkle” (which is me). So then I made this blog post to “verify” that Joe Hinkle gave permission for Impact Studios (my new account name) to host my content, and it worked...somehow...

The blog post that somehow convinced them is here. https://blog.joehinkle.io/2017/04/proving-impact-studios-is-...

Re: Let's guess what Google requires in 14 days or they kill our extension

#793
post #96

Earlier quoted context omitted.

Because they are attempting to automate all of it. This message is generic and based on some analysis of the "manifest.json". They have also turned off all reviews in the Chrome Web Store: https://news.ycombinator.com/item?id=22935092

Huh? They turned off reviews because a worldwide pandemic eliminated their ability to maintain staff to moderate reviews. That's the opposite of "automating it".

Huh? Moderation is one of the easiest tasks to transition to a work-from-home model.

Re: Let's guess what Google requires in 14 days or they kill our extension

#794
post #403

Uh, yikes: > As I looked at the permissions and what our extension actually needs to operate, I noticed a great opportunity to reduce our permissions requests. We do not need to request access to data on https://*/* and http://*/* . Instead, we can simply request data access for https://*.pushbullet.com/* , http://*.pushbullet.com/* , and http://localhost/* . This is a huge reduction in the private data our extension…

paid Google shill.

We've banned this account for breaking the site guidelines. Could you please stop creating accounts to do that with?

https://news.ycombinator.com/newsguidelines.html

Re: Let's guess what Google requires in 14 days or they kill our extension

#795
post #518

Earlier quoted context omitted.

I can only assume that this isn't the result of a human flagging Pushbullet like this; I expect it's an automated system. And if that automated system can make a decision to flag the extension, it could also include in the email specifically what caused that flagging to happen. At this point I'm really starting to become unsympathetic to the idea that they can't tell you what you're doing wrong because it'll enable p…

Getting kicked off the platform happens on HN itself a lot/ I get flagged on HN on almost regular basis (and my ability to reply/talk back is taken away) for speaking my mind (no curse words, just opinions that are others strongly disagree with) about Google, HN itself, Amazon et al. If I ascribe a n ulterior motive to someone in power, I get kicked off. Worse, sometimes I get attacked personally. So I think it's pre…

Who is referring to getting kicked off HN? I believe the post you're responding to, which said "If you're going to run a platform like this and capriciously threaten to kick people off of it," -- the "it" referred to Google.

Re: Let's guess what Google requires in 14 days or they kill our extension

#796
post #403

Uh, yikes: > As I looked at the permissions and what our extension actually needs to operate, I noticed a great opportunity to reduce our permissions requests. We do not need to request access to data on https://*/* and http://*/* . Instead, we can simply request data access for https://*.pushbullet.com/* , http://*.pushbullet.com/* , and http://localhost/* . This is a huge reduction in the private data our extension…

The toughest thing in Google is getting in touch with a Human there. Its virtually impossible unless you know people working there. And this isn't just about scale. Take cloud services. Getting in touch with GCP customer service is a lot more difficult than other providers.

Re: Let's guess what Google requires in 14 days or they kill our extension

#798
post #590

Earlier quoted context omitted.

> Google has apparently paid Mitchell Baker personally multiple millions of dollars too. What are you talking about?

Google fund Mozilla, it's not a secret, you can use a search engine and find such information. Or did you mean to contradict me rather than ask a question?

I know that Mozilla has historically been paid by Google to make Google search the default search provider in Firefox. But you just claimed "Google has apparently paid Mitchell Baker personally multiple millions of dollars too" which is something different that I have heard nothing about. So, what is that claim about?

Re: Let's guess what Google requires in 14 days or they kill our extension

#799
These folks also do the same thing for Adsense on sites. For a site, I am running for a long time. 10+ years. And earned multiples of 100ks worth of revenue from it.

They sent a vague email, regarding violation and suspended Ad serving. Never ever had any issue before.

I can only suspect that their policies have changed because of the current pandemic. But isn't it disingenuous, in that case. Similar to laying off an employee, and cooking up a shady reason for it.

They will only make me kill the business, which in turn will stop payments (reduce significantly) to AWS. Thereby enabling more slow down.

Very very unhappy with them.

Re: Let's guess what Google requires in 14 days or they kill our extension

#800

Earlier quoted context omitted.

Is that really true?

Only years later, as in the case of a certain Vietnamese hacking group that did exactly this starting at the end of 2015 and didn't have their apps yanked until Nov & Dec of 2019 and another batch located & yanked only last month, well after any and all damage was already done to those who used the apps.

Well, I meant for devs who are doing it innocently ;)

The fact that it took four years in your example implies that permission shaving isn't hugely risky for devs.

Post reply on HN