https://api.typings.org is down

[ckvckv]

https://api.typings.org is down.
Unhandled promise rejection (rejection id: 1): PopsicleError: Unable to connect to "https://api.typings.org/entries/dt/moment/tags/2.11.1%2B20161010105546"

[bagadim]

Same here(

[mesajin]

@ckvckv @bagadim Do you know any alternatives for this domain? Any private registries?

[blakeembrey]

The server has been deprecated for over two years, I opted not to renew the domain again. Is there any reason people haven't migrated to @types?

[bagadim]

@blakeembrey We were not tracking it specifically. Once installed and use it.
Thanks for the info, we will migrate to @types!

[blakeembrey]

Ok, please let me know if there's a major problem with migration.

[mesajin]

We have a legacy application running on Typescript 1.8.10. Could you please suggest how to migrate to @types.
We tried these steps from https://stackoverflow.com/a/44170004/985176. But didn't worked.

[tommywo]

we added this to /etc/hosts as a quickfix

104.24.112.177 api.typings.org

[richardlawley]

While I appreciate that @types is the preferred way forward, choosing not to renew the domain with no notice has caused anyone who still used it (old projects, in-progress migrations etc) problems.

The deprecation notice on the typings page gives no indication that it would stop working - quite the opposite:

This project will remain operational for the foreseeable future, but is effectively deprecated. New projects should use @types from NPM.

I was aware of the deprecation, and had in-progress tasks to gradually move off typings, but these have not been easy due to a mix of globals and imports in my project.

[woolfel]

since amazon-login-sdk uses api.typings.org. Builds that the module stop building. if you use CircleCI to build, you're kind of screwed. how much is it to renew the domain?

[blakeembrey]

I’ve hosted this project in deprecation for two years past that notice. I can renew the domain today, but hopefully this project will be sunset by 2020 if I do that. It’s an unnecessary personal expense to keep it available.

[blakeembrey]

I was aware of the deprecation, and had in-progress tasks to gradually move off typings

Just to check on this, if it's been in-progress for two years what's the expected timeframe you'll be able to stop using Typings? Is 2020 (2 months) a reasonable timeframe?

[woolfel]

@blakeembrey it's totally reasonable, except for the fact that Amazon Web Services ignores the deprecation. I think Amazon should pay for the domain on your behalf. We are looking into alternate solutions for amazon-login-sdk. I also sent amazon an angry feedback letting them know they've screwed aws users and ignore the fact you deprecated the api. You didn't do anything wrong at all and I don't blame you. It's 1000% amazon's fault.

[blakeembrey]

The domain is live again FWIW, would love to put a reasonable timeline to shut it down with everyone here. Feel free to direct someone from Amazon here to comment too, I’ll make sure to publish this publicly in the next week or so.

[woolfel]

In my "feedback" to amazon, I did include details about the api being deprecated and that they were responsible. I got a response from AWS, so I know they are aware of it. I included a link to this issue, so they have seen it AFAIK. 2 years is totally reasonable, what's not reasonable is Amazon ignoring the deprecation warning and telling developers to use their library. They make billions and can't put 1 person on it to update their sdk. If I worked at amazon and had enough influence, I'd have amazon pay for the domain, send you a fat check for a few thousand dollars and fire the aws employee for ignoring the deprecation. Sadly I have zero influence at aws and don't work there. In the mean time, you're super cool for covering AWS butt.