Live data from Hacker News

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

blog.pushbullet.com

211–220 of 811 posts

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

#211
Nah, dude. Fuck that localhost access. Sorry, but I wouldn't install something that's running listeners on localhost:80 (or any other port) just because they want to route data from a browser extension to an installed program.

That's a pretty bootleg hack, to be quite honest.

Would you dare touch my /etc/hosts mappings too?

Guess again, Mark Shuttleworth! You wouldn't ever even get installed in the first place. You DON'T have root. Not anymore. [0]

Google is correct to reject you. Localhost belongs to the individual.

[0] http://security.stackexchange.com/questions/44512

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

#212
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.

Yeah, I actually think these sorts of strategies are clever. They're a way to protect normal users without outright barring power users from doing as they wish. macOS operates in a similar way. I really like how the difficulty increases depending on the task: • Want to allow one app through Gatekeeper? Instead of double-clicking the app icon directly, right click it and select "open". • Want to turn off Gatekeeper fo…

Except for those of us who are finding out about it only via a Hacker News comment. As happened with this user, who seems, you know, sufficiently a power user to need that info. Even a "if you know this site to be safe, please read this knowledge base article (link)" and buried in that, amidst all the reasons you shouldn't use untrusted certs, are the instructions.

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

#213

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?

I've used auto-renew ... but it turned out my biggest risk was actually the expiration data on my credit cards

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

#215

We spend a quite a bit on Google Ads yet they seem to refuse devoting even a few minutes of a knowledgable support staff’s time to our account—even when we’re trying to figure out how to give them more money. For 1-2 years our product shopping ads never displayed and we couldn’t get anyone to tell us why. One day, it just started working by itself (perhaps some engineer pushed a fix). Contrast this with their sales s…

I was using Google Ads for a pet project of mine. I lost the password to one account, and then decided to set up another. Using the same CC (which is also my personal CC) on both accounts triggered something and they killed my account. I explained what happened, and told them to check the first account access patterns as they had abruptly stopped due to the loss of the password. They didn't care in the least.

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

#216

I am the proud recipient of many Apple rejection notices from the App Store (I have been releasing iOS apps since 2012). I have not had an app pulled, but I have had many rejections to submitted apps (the latest were received yesterday). In all of the notices, Apple is usually quite explicit in what the problem is, including attaching screengrabs, and they will respond, if I ask them for further clarification.

This is why I'm often amused when people gripe about the $99/year membership fee for the Apple Developer Program.

Xcode is free, Interface Builder is free, all the documentation for everything is free. I'm trying to get into Windows development and don't use Apple devices, but I agree $99 a year for everything Apple gives developers is not expensive considering the value and the cost of these tools on similar platforms.

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

#217

Does chrome already offer features like PushBullet? Firefox somewhat does with Pocket, so I assume chrome has something similar. If they do offer something of the sort, or start to shortly, this seems like a perfect antitrust case.

yes they offer https://messages.google.com/

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

#218

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 been using Fastmail for more than a decade and I don't know why someone would trust something as important as email to a company like Google.

I am not sure why would one trust something as important as email to any company. Register and use your own domain. Then you are totally free in your choice and switching is no problem

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

#219
I just want to mention this is why I believe Google will never be able to compete with AWS, or otherwise be credible in the B2B space. You're relying on automated systems which can take down your business on a whim, with no recourse.

Where I work uses Office 365, which is a horrible, horrible technology compared to Google Suite, but I can't, in good faith, argue for switching to Google. It's not a company I'd ever rely on in a business setting.

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

#220
post #166

Earlier quoted context omitted.

We use localhost to communicate with our desktop application which is commonly installed alongside our extension by users. 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…

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.
Post reply on HN