Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes to forecast.io (now darksky.net) will require code updates and rebranding. #3470

Closed
rpitera opened this issue Sep 21, 2016 · 5 comments · Fixed by #3698
Closed

Changes to forecast.io (now darksky.net) will require code updates and rebranding. #3470

rpitera opened this issue Sep 21, 2016 · 5 comments · Fixed by #3698

Comments

@rpitera
Copy link

rpitera commented Sep 21, 2016

Received via email; forecast.io is rebranding as darksky. The API link as well as branding and use requirements will change as a result.

Hi there,
You’re receiving this email since you have an account registered with us at https://developer.forecast.io/.
Sorry for the long radio silence: we’ve been working very hard on a lot of new things, and we're finally starting to roll them out! As API developers, we wanted to let you know about them.
First, we’re consolidating our branding under the Dark Sky name, getting rid of Forecast.io entirely. We’ve found that people often don’t realize the two are related, and this causes a lot of confusion.
Also, a lot of people seem to pronounce it “forecasteoh” and not “forecast dot eye oh”, and that drives us bonkers!
This means a few things for you as a developer:
The developer portal is now https://darksky.net/dev/. The attribution requirement of the Terms of Service have changed. Attribution should: Display “Powered by Dark Sky” Link to https://darksky.net/poweredby/. Please make this change at your earliest convenience! The API endpoint has changed from https://api.forecast.io/ to https://api.darksky.net/. The previous endpoint will continue to work, but please change your software as soon as possible.
Secondly, we’ve rewritten our developer site from the ground-up. It should now be much easier to use, and will allow us to add new developer features much more quickly and easily than we were able to before.
Expect further updates in the near future, and please let us know if you run into any bugs!
Thirdly, we hate bothering you with emails, so we’ve created a Dark Sky Status Blog that you can use to keep on top of any updates or outages with the API. You can find it at http://status.darksky.net/.
Finally, we wanted to let you know that we’re getting very close to finishing up work on a brand-new weather forecasting model, which should drastically improve our global accuracy.
We’ll let you know when it’s ready, so stay tuned.
Thanks for your continued support!
Adam, Jay, and the Dark Sky Team <3

@chennin
Copy link
Contributor

chennin commented Sep 21, 2016

python-forecastio issue: ZeevG/python-forecast.io#46

@rpitera
Copy link
Author

rpitera commented Sep 21, 2016

Thanks for the xref, @AlucardZero !

@fabaff
Copy link
Member

fabaff commented Oct 3, 2016

Doc update: home-assistant/home-assistant.io#992

@fabaff
Copy link
Member

fabaff commented Oct 3, 2016

Request for new release: ZeevG/python-forecast.io#49

@Landrash
Copy link
Contributor

Landrash commented Oct 3, 2016

@fabaff New release has been done but ZeevG/python-forecast.io#41 was not included. May be nice to have the change over to Darksky anyway in this release.

@home-assistant home-assistant locked and limited conversation to collaborators Mar 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants