Live data from Hacker News

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

blog.pushbullet.com

201–210 of 811 posts

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

#201

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 have all my domains on autorenew, probably many I should have let lapse now, and some of which I have regretted letting go of.

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

#202
I'm also an extension developer, and Google has done this to me a few times too. We request permissions specifically for what we need, and our extension is unlisted and can only be installed from our website.

Google is a bully, and they use their size and the threat of permanently removing access to your Google Account (and family photos) to terrorize small players without cause.

How many people would Google need to hire to provide email support for extension review for extensions above a certain size? It can't be a huge dent in their budget.

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

#203

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…

So many people claim for change, but so few migrate to Firefox, DuckDuckGo, or another alternative.

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

#204

Earlier quoted context omitted.

Usual answer is that this would make it easier for malicious actors to bypass the limitations. Likely there is some automated system running these checks.

Security through obscurity is no security at all. Edit - this is a basic principle of security: https://en.wikipedia.org/wiki/Security_through_obscurity

Anti-cheat through obscurity on the other hand is absolutely a thing.

As a metaphor, there’s a damn good reason you can’t just pay an Olympic anti-doping facility to test your urine; it would be trivial to develop protocols that evade the tests if you could do that.

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

#205

Earlier quoted context omitted.

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 @ .

Yes, but there's still an increase in the attack surface - it's a lot harder to convince a registrar to turn over gmail.com than , for most values of . It's not a deal breaker, of course, but it's something to consider when looking at the risk factor.

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

#206

Earlier quoted context omitted.

Redirects shouldn't compromise the CORS / XSRF security model, which is the key item of concern from a Chrome Extension standpoint. Like if pushbullet.com redirects to foo.com, the crex is now looking at the foo.com page and its permissions will apply accordingly.

Maybe I'm naive but what if pushbullet.com was just running a server-side fetch and returning the result? That would bypass CORS, essentially acting as a proxy server.

Pushbullet doesn’t need a Chrome extension to tell their server to make a web request. But, their server doesn’t have your cookies, so there’s no security concern.

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

#208

Different extension developer here. The Chrome Extension store ecosystem has become a nightmare for developers over the past year. Some items: - Extension review times have gone from 1 hour to a variable amount of time ranging from 1 minute to 3 weeks or longer (try to plan a release or spot fix an issue when you have no idea how long it will take for a deploy to reach users) - User reviews of extensions have been di…

Fellow extension developer here as well. I've been trying to get an update approved since February or March.

Submitted an update in late February and decided to update my screnshots. Remove the screenshots and add new ones only for Google to tell me "you can't add screenshots while you app is in review", fine, add them later after the review.

3-4 weeks go by and I check the approval status. Status has been rejected because....no screenshots provided. I've since updated the screenshots and resubmitted for review. Currently still waiting on approval.

I've been planning on doing a Product Hunt Launch but that's been put on hold until I can get an updated version in the chrome web store (the current version is very old and buggy). I've even looked into distribution outside the store but turns out chrome will no longer let you do that.

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

#209
post #99

We went through the same problem at Superhuman (and as I write our latest extension update has been pending review for 2 weeks, so maybe we're about to hit it again). Simeon on the mailing list was quite re-assuring, and I would recommend reaching out to him, though there are limits to what he can help with. That said we found that the review process is quite arbitrary, resubmitting may work simply because you get a…

Damn that sounds like crazymaking :(

Dunno why they can't be more explicit which part of the code is the issue

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

#210

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

So, which ones are the good registrars?
Post reply on HN