Live data from Hacker News

Unable to deal with Chrome Extension Team, Kozmos is shutting down

kodfabrik.com

281–290 of 530 posts

Re: Unable to deal with Chrome Extension Team, Kozmos is shutting down

#281
post #225

Maybe they're still angry with him about leftpad. Yes, it really is the same guy: https://kodfabrik.com/journal/i-ve-just-liberated-my-modules . And, joking aside it would be wise to bear in mind that we're reading only one side of the story here. As with leftpad, there's another side to this. With leftpad he told Kik, "fuck you" ( https://medium.com/@mproberts/a-discussion-about-the-breakin... ), and then wrought gl…

In the links you've shared, I thought the author (Azer) was on the right to behave the way he did. I don't see it as a reason to discount his current experience because of that either.

Actually if anyone behaved poorly, it was npm not Azer.

I'm shocked to see that something like this could happen on npm - where a single threat of getting lawyers involved can get your package transferred away from you. It really wants to make me not publish anything on npm too actually.

Re: Unable to deal with Chrome Extension Team, Kozmos is shutting down

#282

I have to wonder how PayPal are feeling about their $4 billion acquisition of Honey now, which requests permission to read/write on all websites and exists solely as a browser extension. They're on multiple browsers, but I doubt either Mozilla or Apple will be particularly interested to protect what's presumably now a massive PayPal data mining operation.

I would think lawyers at PayPal would have a little more 'pull' than a single developer though.

I doubt it would have to go to the lawyers, I am sure the exec's of both companies are members of the same organizations, country clubs, or other social circles

Re: Unable to deal with Chrome Extension Team, Kozmos is shutting down

#283

Earlier quoted context omitted.

What was the "other side" of leftpad? As far as I remember, the broken system wrought havoc, not the developer who chose to withdraw his modules. I don't think the developer's reasons are much relevant when discussing how reliable their word is.

The broken system allowed him to be a dick. OK, so the is more to it than that and he did have a genuine grievance (I forgot exactly what) bit in dealing with that he caused a pile collateral damage for innocent bystanders. (Innocent bystanders who errantly put too much faith in dependency oriented programming which brings us back to the broken system)

It's his work, and he had every right to pull every module he hosts there in protest. If this was a walk out or some other form of protest, nobody would be calling him a dick, I think that's a little out of order.

That said, the system is definitely broken.

His reaction to the Kik thing is probably where he was at fault, I think it would have been reasonable for him to back down there; companies, in the US at least are obligated to protect their IP in order to retain their rights over it (as far as I have understood from various discussions on HN), but perhaps the forceful lawyering got his back up?

Also I have no idea of jurisdiction of any parties involved, I just assume US.

Re: Unable to deal with Chrome Extension Team, Kozmos is shutting down

#284
post #157

I definitely feel for the author - the Chrome Extension team has been growing increasingly developer-hostile recently. My own open-source extension HabitLab ( https://habitlab.stanford.edu/ ) that I've been maintaining for the past 3 years is going to be removed in 2 days (got a 14-day removal notice for permissions even though all permissions it requests are used and needed, and every update I try to submit is rejec…

This feels like 1994 all over again. In 1994 you had one dominant software monopoly in Microsoft. Today you have several: Microsoft, Google, Apple, Facebook with dominance in individual spheres of influence. Power corrupts. Absolute power corrupts absolutely.

Re: Unable to deal with Chrome Extension Team, Kozmos is shutting down

#285

Earlier quoted context omitted.

What was the "other side" of leftpad? As far as I remember, the broken system wrought havoc, not the developer who chose to withdraw his modules. I don't think the developer's reasons are much relevant when discussing how reliable their word is.

The broken system allowed him to be a dick. OK, so the is more to it than that and he did have a genuine grievance (I forgot exactly what) bit in dealing with that he caused a pile collateral damage for innocent bystanders. (Innocent bystanders who errantly put too much faith in dependency oriented programming which brings us back to the broken system)

> Innocent bystanders who errantly put too much faith in dependency oriented programming

and who need an external package to leftpad a string... the most fascinating part of that story to me...

Re: Unable to deal with Chrome Extension Team, Kozmos is shutting down

#286

Maybe they're still angry with him about leftpad. Yes, it really is the same guy: https://kodfabrik.com/journal/i-ve-just-liberated-my-modules . And, joking aside it would be wise to bear in mind that we're reading only one side of the story here. As with leftpad, there's another side to this. With leftpad he told Kik, "fuck you" ( https://medium.com/@mproberts/a-discussion-about-the-breakin... ), and then wrought gl…

We have a lot more than two data points for Google screwing Chrome extension developers.

Re: Unable to deal with Chrome Extension Team, Kozmos is shutting down

#287
post #221

Earlier quoted context omitted.

That's very sad to hear, I've been an avid user of HabitLab. Thank you so much for developing this tool! I wonder if you've ever considered doing a Chromium fork with the HabitLab interventions integrated deeper into the browser? I think there's a lot of potential and interest for a productivity-oriented browser that helps stay focused and develop good time management skills.

A Chromium fork is going to be a pain to maintain. My contingency plan if it gets removed from the Chrome store is to try to get it accepted into the Edge and Opera stores, and ask users to switch to either Edge or Opera (and provide sideloading instructions for those who want to stick to Chrome).

Why not, might I ask, Firefox?

Edit: no need to reply, I've seen your answer below, thanks.

Re: Unable to deal with Chrome Extension Team, Kozmos is shutting down

#289
post #225

Earlier quoted context omitted.

In the links you've shared, I thought the author (Azer) was on the right to behave the way he did. I don't see it as a reason to discount his current experience because of that either.

Actually if anyone behaved poorly, it was npm not Azer. I'm shocked to see that something like this could happen on npm - where a single threat of getting lawyers involved can get your package transferred away from you. It really wants to make me not publish anything on npm too actually.

Totally agree. I'm shocked to see that people actually think less of Azer because of what he did. Why keep your work on a company that bullies you like that?

Re: Unable to deal with Chrome Extension Team, Kozmos is shutting down

#290
post #284
post #157

I definitely feel for the author - the Chrome Extension team has been growing increasingly developer-hostile recently. My own open-source extension HabitLab ( https://habitlab.stanford.edu/ ) that I've been maintaining for the past 3 years is going to be removed in 2 days (got a 14-day removal notice for permissions even though all permissions it requests are used and needed, and every update I try to submit is rejec…

This feels like 1994 all over again. In 1994 you had one dominant software monopoly in Microsoft. Today you have several: Microsoft, Google, Apple, Facebook with dominance in individual spheres of influence. Power corrupts. Absolute power corrupts absolutely.

In 1994 Microsoft didn't arbitrarily ban applications on their OS.
Post reply on HN