[Question] Simple question about package name

[kud]

Hello,

I've got a script which installs and maintains my machine up to date.

I used to do this: $ npm install up -g to install the cloudup cli but now, I've got your project instead. I was a bit 🤔 when I wanted to try my command $ up.

So... I would like to know, how did you get this project name in fact, by overriding the one from cloud up team?

[tj]

Yeah I reached out to Automattic like a year ago but they never got back to me, so I bumped the version, you can still install an older semver of course via @.

Cloudup is basically a dead project, has been for years. This is why I wouldn't trust startups haha, they just get absorbed and discarded by larger companies.

[kud]

Okay! Thank you for your answer and your time. ;)

[kud]

I installed it via npm install -g Automattic/cloudup-cli.

[kud]

In fact my question was mostly like there's no permission on npm? How did you override their package?

[tj]

I wrote the original cli. Honestly I'd just move on to Droplr / Cloudapp etc, they haven't monetized it at all or changed anything, I don't think they have any intention of maintaining cloudup.

[kud]

That's why! Okay I understand now. :)

[oskosk]

Cloudup is basically a dead project, has been for years.

@tj this is not true. We use it extensively. It's not even free to maintain. Developers and Happiness Engineers (support crew) use it daily for different purposes. Even our documentation is packed with images coming from Cloudup. And the feature of having an up cli to get a rapid URL for a screenshot one has just made is essential for daily tasks.

they haven't monetized it at all or changed anything, I don't think they have any intention of maintaining cloudup.

This is not quite an accurate way of inferring how the company has been using the product for years though. But I do understand the concern of course. Came here due to having received a notif for Automattic/cloudup-cli/issues/56

[kud]

Thanks @oskosk , I still use it to be fair. :D