Chrome killed my extension and won’t tell me why
71–73 of 73 posts
Re: Chrome killed my extension and won’t tell me why
#72Earlier quoted context omitted.
Publishers need authors to make money, google doesn’t need extension developers.
In theory, Chrome works fine without extensions. In practice, if Chrome was "banned by the Extension developers' guild" so that every other browser got to participate in the WebExtension ecosystem except for Chrome, people would leave Chrome quickly. (Sadly, probably for some "exactly Chrome, but not by Google" browser, rather than for Firefox.)
Better brand recognition - more people switched off IE to Chrome than from FF to chrome (hence why I’m not putting the terrible performance and reliability issues that FF used to have like crash and lose all tabs as a factor but it took a decade for FF to sort their shit together and by then it was too late).
Better integration with Google services right when a Google account became quite important.
Being the default browser for the Android eco system.
So I don’t know who would exactly leave Chrome because of extensions but I have a feeling that even you wouldn’t.
Re: Chrome killed my extension and won’t tell me why
#73Earlier quoted context omitted.
This seems like more a solution to open, transparent platforms. It’s a shame that we are going backwards: you used to be able to download software from the internet, direct from publishers with no limitations. Now everything’s all stupid requiring developers to beg the “powers that be” for access to distribute their work.
But that isn't sustainable anymore now that everyone and their mother does all sorts of sensitive thing on the internet. App Stores may not catch any and all malware, but they'll catch some, or even a lot, and they give Google (or whoever runs one) tools to deal with what slips through. They make getting new extensions transparent and they're trustworthy. What's missing is legislation to level the playing field; eith…