Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

blog.pushbullet.com

Post reply on HN
Print view View original

461–470 of 811 posts

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

#461

Post by freehunter »

ashtonkem wrote: post #428
freehunter wrote: post #233

Earlier quoted context omitted.

If anti-cheat through obscurity worked, there would be no cheaters. The fact that cheaters exist means it does not work.

This is an all or nothing fallacy; the standard is not 100% success. It’s bit like saying “all locks can be picked, therefore they’re useless”.

That’s not what we’re discussing though. We’re discussing if anti-cheat through obscurity works, and I’m saying if it did there would be no cheaters. Instead companies have to build technology solutions that also don’t work 100% but that’s beside the point.

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

#462

Post by rattray »

jtxx wrote: post #64
wlesieutre wrote: post #36

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?

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.

How does ProtonMail compare to FastMail these days?

I see https://news.ycombinator.com/item?id=18008062 from 2018 where the jury seemed to overall favor FastMail.

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

#463

Post by znpy »

dilandau wrote: post #319
seanwilson wrote: post #84

For people focusing their comments on this particular extension + the permissions it asks for, please take a quick look at the numerous recent posts in the official forum for Chrome extension developers to see it's not an isolated issue: https://groups.google.com/a/chromium.org/forum/#!forum/chrom... It's a systematic issue that isn't specific to anything Pushbullet is doing and it's been like this before the pandemi…

>We hear you and are eagerly looking to improve things. Joking aside, isn't this just what people should come to expect from the company that has always tried to normalize the "no support and no service" model? If these antics start causing GOOG to lose share in the browser market then they may review these policies, but I highly doubt it. At the end of the day GOOG is an ad company and publicly-traded at that. They…

> "no support and no service" model?

this is one of the reasons why Google cloud will lose to AWS in the long run.

AWS is customer obsessed, Google is not.

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

#464

Post by freehunter »

StavrosK wrote: post #451
freehunter wrote: post #134

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

Wouldn't the fact that your company's site doesn't work on Firefox need to be filed as a bug on your site's bug tracker?

You’re assuming I have access to my huge mega tech company’s website’s bug tracker. I do not.

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

#465

Post by friedman23 »

geofft wrote: post #403

Uh, yikes: > As I looked at the permissions and what our extension actually needs to operate, I noticed a great opportunity to reduce our permissions requests. We do not need to request access to data on https://*/* and http://*/* . Instead, we can simply request data access for https://*.pushbullet.com/* , http://*.pushbullet.com/* , and http://localhost/* . This is a huge reduction in the private data our extension…

>Uh, yikes

Agreed I wish we could send everyone that thinks this kind of response from a megacorporation is good to a kafkaesque alternate universe.

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

#466

Post by yellowapple »

nikolay wrote: post #133

Google are cutting the branch they are sitting on. I only use Chrome because certain extensions are not available on Firefox. During all these years, they've become impossible to deal with. I open Chrome with 10 tabs and after a couple of hours it's using gigabytes of RAM. From a thin client, it became the thickest client in the visible universe. It's time to consider options... not that there are many.

> I only use Chrome because certain extensions are not available on Firefox.

Which extensions? Especially now that Firefox has moved to WebExtensions, it should (in theory at least) be straightforward for someone to port them over.

Like, if anything it's usually the other way around (Chrome not supporting extensions that Firefox supports).

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

#467

Post by freehunter »

dylz wrote: post #396
maest wrote: post #337

Earlier quoted context omitted.

Youre confused because you're not using Chrome on OSX: on osx there's no "Proceed to " option.

I'm now even more confused: https://i.imgur.com/jl9agwG.png

You’re right to be confused because I’ve never seen a rhyme or reason to it either. I generated a cert using OpenSSL’s command line tools and told Django’s manage.py to use my self-generated cert and it works in Firefox but not Chrome.

It did work in Chrome. And then after an update it didn’t work anymore. I don’t know why and it seems like no one else here does either.

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

#468

Post by Mindwipe »

jaredandrews wrote: post #13

Slightly related, Google is also tightening up Android 11 location permissions (with good reason). In this blog post[0] they outline a process for getting approval that was supposed to be underway by the start of May. So far I have not been able to locate this form nor have I been able to find any Android developers who have. If anyone here knows where it is or what the deal is, please let me know. [0] https://androi…

The SMS access process never worked after it was introduced in a similar way several years ago now. Google even put some minority groups in significant danger to their safety as a result.

Nobody at Google gave a shit and it was never fixed.

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

#469

Post by brigandish »

geza wrote: post #370

I got the same notification yesterday morning for my own open-source extension HabitLab ( https://habitlab.stanford.edu/ ) - same vague request for "you're not using the minimal set of permissions" without mentioning what permissions they want me to stop using (HabitLab is already using the minimal set of permissions for the features it implements - any removal of permissions would have to be done at the expense of r…

Have you considered writing a short blog post (even a tweet) about it and submitting it to HN? Momentum is a good thing.

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

#470

Post by WarOnPrivacy »

sneak wrote: post #432
wlesieutre wrote: post #36

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?

Firefox’s security is a lot less than that of Chrome.

Firefox gives me much more control than Chrome and that makes it much more secure.
Post reply on HN