Live data from Hacker News

How Google obliterated my 4 year old Chrome extension with 24k+ users (2016)

by.graffino.com

71–80 of 131 posts

Re: How Google obliterated my 4 year old Chrome extension with 24k+ users (2016)

#71
post #65

In the final update post[0] the author says There isn’t any option left to circumvent the Chrome Store. Starting with Chrome 53, extensions cannot be side-loaded anymore. Is it possible that Firefox will undergo such a restriction in the future? [0] https://graffino.com/web-development/after-my-post-went-vira...

Firefox already has a similar restriction on Windows, and I think MacOS, but not Linux.

On the normal version of firefox for those platforms you can't permanently sideload an extension, you need to reload it on each restart.

The Developer Edition still lets you sideload addons normally, however.

Re: How Google obliterated my 4 year old Chrome extension with 24k+ users (2016)

#72
post #40

Earlier quoted context omitted.

I am not worried that Amazon would shut down all of AWS any time soon. Can you honestly say it would be a complete surprise, however, if Google announced an EOL for GCP?

Even if they did, for such a big service there would be a long transition period. E.g. 2 years, so you could move somewhere else.

That assumes that you can move off the system and that’s enough notice. Not to mention that it blows up your roadmap.

What’s the point of outsourcing heavy lifting if the vendor is just going to surprise drop it back on your at an in opportune time?

Re: How Google obliterated my 4 year old Chrome extension with 24k+ users (2016)

#73

Earlier quoted context omitted.

Reminds me of how I turned off autoupdate on my mobile browser...

Seriously this Firefox update was a massive bait-and-switch for me. I was on holiday and out of the loop on how big of change this Phoenix upgrade would be, got a notification on Android to update firefox and went through without realizing the massive UX and functionality downgrade this Firefox version is. Apart from the non-starter of missing add-ons, the whole UX overhaul is insane, so many things that use to be fr…

I think it’s usually the latter. Either the feedback wasn’t heard or wasn’t sought.

Re: How Google obliterated my 4 year old Chrome extension with 24k+ users (2016)

#74
post #40

Earlier quoted context omitted.

I am not worried that Amazon would shut down all of AWS any time soon. Can you honestly say it would be a complete surprise, however, if Google announced an EOL for GCP?

Even if they did, for such a big service there would be a long transition period. E.g. 2 years, so you could move somewhere else.

That would be reasonable, yes. But not expected from Google.

Re: How Google obliterated my 4 year old Chrome extension with 24k+ users (2016)

#75
post #68

Earlier quoted context omitted.

Failing that, maybe change some laws and regulations.

>>change some laws and regulations. but then we are in another loop where people who don't understand technology will bring in laws that both fix an issue but creates a whole set of new issues, that might even hinder progress. So I am not a fan of politicians getting involved with things they don't have a good idea about. Personally I choose to believe in the whole decentralized internet idea that's starting to takin…

Yeah the internet being so predominantly web pages with html on them that you have little power to customize ad a user may seem antiquated one day. The internet should simply beam you data on demand, and you can visualize it any way you like client side

Re: How Google obliterated my 4 year old Chrome extension with 24k+ users (2016)

#76
post #57
post #54

The author infringed on Facebook name and possibly the logo too. Facebook sent a notice to Google. Google complied with the law and removed the extension. Yet the author blames Google for all this.

Thank you for this background detail! So actually instead of google, it was FB who with trademark protection legislation took down the app.

An important question is, did Google ever tell the author who made the complaint so he could contact them or countersue? From the mails that are shown they don’t reveal anything apart from ‘a third party acting on behalf of Facebook’.

Re: How Google obliterated my 4 year old Chrome extension with 24k+ users (2016)

#77
post #40

Earlier quoted context omitted.

I am not worried that Amazon would shut down all of AWS any time soon. Can you honestly say it would be a complete surprise, however, if Google announced an EOL for GCP?

Even if they did, for such a big service there would be a long transition period. E.g. 2 years, so you could move somewhere else.

Wow, 2 years, such a long time

Re: How Google obliterated my 4 year old Chrome extension with 24k+ users (2016)

#78
post #57

Earlier quoted context omitted.

Thank you for this background detail! So actually instead of google, it was FB who with trademark protection legislation took down the app.

An important question is, did Google ever tell the author who made the complaint so he could contact them or countersue? From the mails that are shown they don’t reveal anything apart from ‘a third party acting on behalf of Facebook’.

That would be giving legal advice, which Google (or any company) would avoid at all costs.

Re: How Google obliterated my 4 year old Chrome extension with 24k+ users (2016)

#79
post #60

Earlier quoted context omitted.

Was there no way to create a new adwords account?

Pretty sure that's against tos..

And.... Who cares? Given Google's absurdly shitty behavior to so many users, its opacity, frequent mendacity, casual indifference to small organizations and let's not even go into all the gory details of its globe-spanning not-even-disregard-but-outright-hatred for any notion of privacy, I'd say anyone who can subvert its TOS and get away with doing so simply to save their livelihood deserves applause much more than scorn.

Re: How Google obliterated my 4 year old Chrome extension with 24k+ users (2016)

#80

Earlier quoted context omitted.

Money. A new walled garden is a new opportunity for developers to make money, with little competition (at first). Then when it gets big and there’s tons of competition, the company can stop caring about the developers and still make a pile of money. It’s going to keep happening because walled gardens appeal to human nature. Everyone (users, developers) wants the immediate benefits, but only the company reaps long-ter…

Failing that, maybe change some laws and regulations.

Laws and Regulations are themselves a Walled Garden with all the same problems with the added problem of a monopoly on the initiation of violence to enforce the rules
Post reply on HN