Live data from Hacker News

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

blog.pushbullet.com

191–200 of 811 posts

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

#191
post #50

It is a common theme with Google, what they do makes sense, but communication is impossible. I don't know if it is an artifact of overusing machine learning "our neural network trained on a variety of malware gives your app a score of 4.3, you have 15 days to get it down to 4.0". How is that calculated? No one knows, maybe you shouldn't use the location permission if your icon is red and your domain is not in .org, o…

> It is a common theme with Google, what they do makes sense, but communication is impossible.

You could say the same about some machine learning algorithms.

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

#192
post #119

i guess removing plaintext http and localhost should fix this.

We never use plaintext http so that is a reasonable thing to remove for our first-part domain (pushbullet.com). We use localhost to communicate with our desktop application. An example 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). Maybe if we limit it to just the local port we use? Seem…

You could try that. Long term, it should also be possible to route this communication through the internet, or use the Chrome/Firefox/WebExtension NativeMessaging API [0][1].

0. https://developer.chrome.com/apps/nativeMessaging.

1. https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...

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

#193

lol. We have the same problem, but on the Google Play Store. We have an brand name app used by millions of people. We uploaded an update where the only change was a new Firebase library. Google rejected the update for vague reasons (“violation of Google Play policies” but not telling us which one). Appealing the rejection, the CSR just pasted the vague policy thing back at us. We asked for more information and they j…

> No idea what’s going on at Google.

It's like trying to troubleshoot a machine learning algorithm.

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

#194

Earlier 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?

If a domain is important to you, you should have it set to autorenew.

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

#195
post #161

Earlier quoted context omitted.

IIRC, the intent is that no one should be doing this and anyone doing it should be at least technical enough to figure out what they're doing and be reminded that it's a bad idea.

On the other hand these stupid dialog tricks are why I stopped using Chrome. I'm not an idiot and I know what I'm doing. It's pretty arrogant to assume that I shouldn't be visiting my router's configuration page just because it uses a self-signed certificate. I don't care to set up an X.509 infrastructure at my house, thank you. Please stop mollycoddling me. Firefox continues to do a good job of just letting me visit…

I'm confused - Firefox and Chrome act completely identically to a self signed cert for me. Both let me click through after looking at the cert or expanding a section. I have never been "blocked" by some hidden modal unless the site chooses to be HSTS-enforcing, and in that case Firefox does not allow a clickthrough either.

Both examples on latest current, taken right now:

Firefox: https://i.imgur.com/4VMjDZ4.png

Chrome: https://i.imgur.com/YosvXEu.png

For HSTS, both Firefox and Chrome act identically and do not allow clickthrough: https://i.imgur.com/WPCTep1.png

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

#196
post #64

Earlier quoted context omitted.

ProtonMail has come a long way as a replacement for Gmail as well. Suuuper happy with them, they're really responsive to feature requests and support inquiries. I requested for an iOS feature to choose browsers so I could open all links from PM in Firefox. They had it implemented in a month or something... it a quick fix but that impressed me. hence me shilling here They recently added ProtonCalendar too.

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.

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

#198

Earlier quoted context omitted.

The most important change you can make for your email is to own your own domain. Once you own your own domain, changing providers is much easier since it is transparent to the people that email you. Even if you decide to keep Gmail, you should switch your email to your own domain.

One worry about tying your identity to your own domain, is the security of your identity (aka your domain) hinges on the security of your registrar. If a bad actor can socially engineer their way into controlling your domain, your entire identity is compromised. Here's a blog post about this nightmare happening to someone: https://medium.com/@N/how-i-lost-my-50-000-twitter-username-...

I agree that that would be catastrophic, but I’m not convinced that using custom DNS changes my risk factor. If someone took over @gmail.com, they could do as much damage as they could by taking over @.

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

#199

Another 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…

I whole-heartedly agree and this is why I give money to AWS and Azure will not give any to GCP until the lack of transparency and random product killings stop.

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

#200

Earlier quoted context omitted.

Chrome is a trivially easy product to switch off of compared to other Google properties like Gmail and YouTube. Have you tried Firefox recently?

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…

Try sending your company's internal sites a Chrome User-Agent from Firefox. There are extensions that let you do this.
Post reply on HN