5 ms·

I believe Pushbullet needed it's permissions for the features it offered, they even tried removing features and permissions just to appease Google. Regardless

I believe Pushbullet needed it's permissions for the features it offered, they even tried removing features and permissions just to appease Google. Regardless of that, just tell people what they've done wrong, developers are surely jaded by being told absolutely nothing about what or why some faceless mega corp is trampling all over their day. Is it any wonder people like OP lash out in frustration and just pull all of their work when one has no means to obtain a straight answer? The man has a young child, and that is work enough, but it also puts things into perspective, and honestly, as a father of a months old child, I'd probably respond to this in the same way and think "fuck it, one less frustration" and just pull it too.

pvg 6y ago
I believe Pushbullet needed it's permissions for the features it offered The PB post describes them removing permissions they realized they didn't need, you can check their writeup. Google's handling of this was poor but PB had real problems. In this extension's case, we haven't even seen what notices Google sent.
- alias_neo 6y ago
  I'm all for enforcing strong privacy rules, in fact, I stopped using PB very quickly after trying it for the first time, because of the _feeling_ of a lack of privacy/security it gave me (based on no actual evidence), so I'm not defending PB. That said, calling Google heavy handed is an understatement, and there have been several cases which have made it clear that kicking up a fuss online and being big enough to get some attention is the only means for recourse.
  - pvg 6y ago
    I didn't call it 'heavy handed'. I'm just correcting your assertion that PB didn't have unnecessary and overly-broad permissions. This is in their writeup.
    - znpy 6y ago
      This might be okay as long as you give clear and specific points to correct. But Google just said "you're asking too much permissions". After the first fixes the extension got rejected again, without explanation.
      - pvg 6y ago
        I'm not really trying to re-litigate the whole PB thing. It's just not the case that they got dinged for nothing which is what the comment I replied to was suggesting. And the other (I think more important) point was that we know even less about whatever happened to Kozmos.
    - alias_neo 6y ago
      Oh, I understand your point. I was calling Google heavy handed.

pvg 6y ago

I believe Pushbullet needed it's permissions for the features it offered The PB post describes them removing permissions they realized they didn't need, you can check their writeup. Google's handling of this was poor but PB had real problems. In this extension's case, we haven't even seen what notices Google sent.

alias_neo 6y ago
I'm all for enforcing strong privacy rules, in fact, I stopped using PB very quickly after trying it for the first time, because of the _feeling_ of a lack of privacy/security it gave me (based on no actual evidence), so I'm not defending PB. That said, calling Google heavy handed is an understatement, and there have been several cases which have made it clear that kicking up a fuss online and being big enough to get some attention is the only means for recourse.
- pvg 6y ago
  I didn't call it 'heavy handed'. I'm just correcting your assertion that PB didn't have unnecessary and overly-broad permissions. This is in their writeup.
  - znpy 6y ago
    This might be okay as long as you give clear and specific points to correct. But Google just said "you're asking too much permissions". After the first fixes the extension got rejected again, without explanation.
    - pvg 6y ago
      I'm not really trying to re-litigate the whole PB thing. It's just not the case that they got dinged for nothing which is what the comment I replied to was suggesting. And the other (I think more important) point was that we know even less about whatever happened to Kozmos.
  - alias_neo 6y ago
    Oh, I understand your point. I was calling Google heavy handed.