Earlier quoted context omitted.
You can bypass the Chrome dialog by typing "thisisunsafe" in the error page.
That's a stupidly hidden way to go about it.
Let's guess what Google requires in 14 days or they kill our extension
161–170 of 811 posts
Re: Let's guess what Google requires in 14 days or they kill our extension
#162Earlier quoted context omitted.
Who do you trust? Certainly not Chromium-Edge. That leaves "only browse the internet on a Mac with Safari" or browsers with such tiny market share that they'll never be tested against, and sites will routinely be broken for you. My company doesn't do any non-Chrome compatibility testing, so all our intranet sites require Chrome.
Why not firefox?
Re: Let's guess what Google requires in 14 days or they kill our extension
#163Earlier quoted context omitted.
I'd stress the "get your own domain" part. This is a _requirement_, or you're going to be going through the same pain again in a few years. Also, make sure you take backups of your old emails every once in a while. Google Checkout should be able to provide those.
What’s the risk of losing your domain from a forgotten renewal?
Re: Let's guess what Google requires in 14 days or they kill our extension
#164Chrome extension developer here. Google ripped my Chrome extension off the app store about a month ago. I got a similar cryptic message, and then I scrambled to fix it, like you're doing now. Somehow my extension reappeared the next day. Email me pat [at] trypigeon [dot] co and I can send you some of the things I did that maybe have helped. Tweeting my support as well: https://twitter.com/thepatwalls/status/126063896…
I have written about this recently on the Android side. https://medium.com/@lazherrera/that-one-time-google-made-it-... If you use any of the words related to the COVID-19 pandemic, they will pull your app, suspend you and ding your account.
Re: Let's guess what Google requires in 14 days or they kill our extension
#165As much as we can criticise Google's handling of this situation, the fact that the developer was able to reduce permissions from accessing data on _all websites_ down to _their website_, as well as tighten up a few other permissions, shows that Google is correct that the extension is asking for more than it needs. I hope the developer finds another load of permissions they can tighten up, resubmits, and is approved.…
You're missing the point here. The developer isn't given any guidance on what needs tightening. This shouldn't be guess and check. These rules impact this developer's livelihood. They should be well defined, documented, and communicated.
Re: Let's guess what Google requires in 14 days or they kill our extension
#166Does your browser extension really need to access localhost/* - as in, port 80 on my local machine? That would make me very uncomfortable about installing the extension. Would it be possible to restrict the extension to accessing a specific port or endpoint that is used by PushBullet?
An example of how we use this communication channel is preventing both our extension and desktop apps from showing notifications on the same computer. Our apps are all about notifications so this would get unacceptable very fast. We ping our local desktop app via localhost to see if it can manage the notification, and show it with our extension if it isn't running.
Maybe if we limit it to just the local port we use? Seems like it can't hurt to try that too.
Re: Let's guess what Google requires in 14 days or they kill our extension
#167Earlier quoted context omitted.
I'd stress the "get your own domain" part. This is a _requirement_, or you're going to be going through the same pain again in a few years. Also, make sure you take backups of your old emails every once in a while. Google Checkout should be able to provide those.
What’s the risk of losing your domain from a forgotten renewal?
Renew your doman for 10 years now, and then every next year do 1 year renewal. If you forget it then you still have 9 years of buffer.
Re: Let's guess what Google requires in 14 days or they kill our extension
#168Another long-term PushBullet customer here. Anyone at Google who is listening- this kind of behavior kills my desire to continue using your products dead. I need functionality, of the type PushBullet has provided for years, to do my work. The recent nerfing of ublock origin has already had me feeling iffy on things. Behavior like this is simply unacceptable. If you want people to use your services, you need to have s…
Re: Let's guess what Google requires in 14 days or they kill our extension
#169> The other opportunity is the tabs permission. This permission lets extensions see what tabs are open. Pushbullet uses this permission to avoid opening new tabs for websites that are already open when mirrored notifications are clicked. This is a small sacrifice to make to let go of a big permission. Let’s let it go! No, that "small sacrifice" sounds super annoying! I don't use Pushbullet, but if I did and this got…
An optional permission seems 100% reasonable.
Re: Let's guess what Google requires in 14 days or they kill our extension
#170Another happy PushBullet user here. Extremely useful for receiving text messages from my phone while on my laptop, especially for web apps that insist on sending security codes that way instead of TOTP. This sort of behavior from Google really is infuriating. How they can just decide to boot an app from the Chrome Store that is installed by over a million users is mind-boggling. It's a pity that Chrome doesn't allow…
> It's a pity that Chrome doesn't allow extensions to be installed from the new Edge store Why would anyone want to do that? What's a real pity is that they make every effort to block users from installing their own extensions. App stores are terrible.