Robots are in control here, follow their rules and get your accounts permanently deleted if you don't understand the robots rules and mindset...
Let's guess what Google requires in 14 days or they kill our extension
241–250 of 811 posts
Re: Let's guess what Google requires in 14 days or they kill our extension
#242Earlier quoted context omitted.
What’s the risk of losing your domain from a forgotten renewal?
I have all my domains on autorenew, probably many I should have let lapse now, and some of which I have regretted letting go of.
I feel your pain.. I accidentally let my main blog domain go a long while ago when I decided to drop most of the domains I was holding.
Beyond this, I've had a few pretty good ones over the years... right now, I've got about 30 of them, and just keep thinking I should let most of them go.
Re: Let's guess what Google requires in 14 days or they kill our extension
#243I had a friend who went through a similar, onerous process with Google which ended up killing his entire chrome extension (which had 400,000+ MAU). This iron-fisted control of the extension marketplace is not becoming to Google.
Re: Let's guess what Google requires in 14 days or they kill our extension
#244Earlier quoted context omitted.
I've found the exact opposite to be true in my very specific experience. Five years ago I used every Google product under the sun, today the only Google product I use at all (even search) is Chrome because it's the only one I haven't been able to replace. I try Firefox with a fresh install on nearly every major release and I keep it installed as a secondary browser, but I can never manage to use it as my daily browse…
You can bypass the Chrome dialog by typing "thisisunsafe" in the error page.
Reminds me of the default admin password for an app I've worked on... "You should change me."
Re: Let's guess what Google requires in 14 days or they kill our extension
#245Earlier quoted context omitted.
Switching email isn't nearly as friction-free as switching your browser. Not only do you have to change your email in every service you've registered for, you also need to convince your friends and other contacts to use the new email.
I recall seeing this recently on another HN post, where they had set up a blanket forwarding rule from their Gmail to another email account. Their Gmail later got dinged but the forwarding rule continued to work.
I did that years ago. The only downside is that every 2-3 years some email gets stuck in gmail’s spam folder.
Re: Let's guess what Google requires in 14 days or they kill our extension
#246I think that reading all of a users' cookies from all websites is pretty privacy invading...
Re: Let's guess what Google requires in 14 days or they kill our extension
#247Earlier quoted context omitted.
What’s the risk of losing your domain from a forgotten renewal?
I've used auto-renew ... but it turned out my biggest risk was actually the expiration data on my credit cards
I loaded up credits at my registrar to last a couple years because of this.
Re: Let's guess what Google requires in 14 days or they kill our extension
#248As 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.…
Extension developers monetizing their extensions by selling the data that they get from users is a big problem. It's the reason that I don't freely install useful extensions that I find today. I have no way to distinguish those who sell my data from those who dont. I love that Google is starting to solve this problem, and from my perspective an extension that is sending and receiving SMS messages should not be reques…
They aren't solving this problem, they're killing off extensions. And I say this having received many unsolicited attempts to "purchase" Chrome extensions.
Re: Let's guess what Google requires in 14 days or they kill our extension
#249Earlier quoted context omitted.
I believe you're supposed to use Native Messaging for that: https://developer.chrome.com/extensions/nativeMessaging
This may be well what needs to change, but in any case the message from Google should have been explicit about it instead of the dev involved having to create a blog post, hope it gets traction on HN and that someone here knows what the problem is.
the docs are pretty explicit about it
Re: Let's guess what Google requires in 14 days or they kill our extension
#250Earlier quoted context omitted.
I'm not the previous commenter, but on Android Mozilla is removing the ability to install extensions from third parties (think GitHub, etc.) and will trim the only left official extension store down to a few extensions. (I think it's below 20 right now.) An ecosystem where all extensions need to be channelled through one central power broker is pretty much the main requirement to allow them to do what Google is doing…
This is temporary while the Android team builds out and stabilizes the add-on APIs supported in the new Firefox for Android. Otherwise it'd be a total crapshoot whether an add-on you tried to install worked or broke randomly (potentially in gnarly ways).
If locking down on the extension ecosystem were only temporary they could just defer the nearing downgrade of their main line browser until their replacement is fully functional.
But that's not what they do. Instead we do have a clear announcement on a feature removal and a vague hint that they might add it again in the future.
It's absolutely not sure that disabling non-store extensions is only a temporary defect.
If you have evidence that suggests otherwise, feel free to add it.
It does not help that their marketing language feels designed to consistently avoid any meaning whatsoever.