How Google obliterated my 4 year old Chrome extension featuring 24k+ users

Re:How Google obliterated my 4 year old Chrome extension fea... by zenopopovici on Wednesday September 07, 2016 @09:44AM (#12443285)

You got it wrong. I was never told what to do or how to change it so that my users would still recognize it. Also changing its name in this way was suggested (and accepted) for the Safari extension by the Safari Gallery Team.

If I don't know what I'm doing wrong, I can't fix it. This is not about TM infringement, but the total lack of communication by Google.

[ Parent | on HN ]

Re:How Google obliterated my 4 year old Chrome extension fea... by kowdermeister on Wednesday September 07, 2016 @10:18AM (#12443569)

> If I don't know what I'm doing wrong, I can't fix it

Most of programming btw is like that. Google throw an exception with a better error than "undefined is not an object". Maybe it's easy for me from the outside to pinpoint the problem, but it's usually about reading between the lines.

Their support is indeed poor, but you are not entitled anything and probably the lesson here is not to build anything serious on 3rd party platforms where you are unsure about licensing, legal questions. I've been burned once by SoundCloud legal team for using their public API.

[ Parent | on HN ]

Re:How Google obliterated my 4 year old Chrome extension fea... by zenopopovici on Wednesday September 07, 2016 @11:31AM (#12444207)

I'm not entitled for support when I'm developing for their platform ... and I'm supposed to be a sightseer 4 years in the future.. I'm gonna stop right there...

[ Parent | on HN ]

Re:How Google obliterated my 4 year old Chrome extension fea... by atombath on Wednesday September 07, 2016 @10:14AM (#12443529)

Devil's advocate: it isn't in Google's interest to give you legal advice.

[ Parent | on HN ]