[mythtv-users] xmltv and atlas grabber
Thomas Boehm
mythtv-users at lists.boehmi.net
Tue May 17 21:23:02 UTC 2016
Hi list,
if you use xmltv with the atlas grabber you might have gotten the
following email from Metabroadcast
-----
We are writing to you because you have registered an API key for Atlas
using this email address.
Today we are announcing some important changes to the way we make data
available for smaller users of Atlas. You can read more about these
changes here: https://metabroadcast.com/blog/changes-to-atlas-access
As part of these changes, it is necessary for all holders of Atlas API
keys to log in to the Atlas website before 16 June 2016, and confirm
compliance with our updated terms and conditions. Details of how to do
this are available here:
https://metabroadcast.com/blog/confirming-atlas-terms-and-details
You can contact MetaBroadcast via the contact form here:
https://atlas.metabroadcast.com/admin#/contact. Unfortunately we cannot
commit to answering all messages individually, or messages sent via
other channels.
Thanks for reading,
Chris
-----
and the summary of the first link is as following
-----
1. The former RadioTimes XMLTV feed will stop on 16 June 2016.
2. We have updated our terms for the first time in two years, including
clarifying when free access to Atlas is provided.
3. All users of Atlas APIs must log in and reconfirm compliance with
terms and conditions by 16 June 2016, following the instructions
here. Applications that do not confirm by 16 June 2016 will have
their API keys revoked.
4. In addition, we will advise some applications of changes in their
API calls that are required.
5. One specific change required is that no call to the Atlas schedule
endpoint should request more than 24 hours of data. Applications not
following this rule will be revoked without further notice.
6. Those making personal use of Atlas may well want to consider another
source of data, such as Schedules Direct.
7. You can contact MetaBroadcast via the contact form here, although we
cannot commit to answering all messages individually.
-----
Can someone explain in plain english what this means for the future use
of Metabroadcast's guide data?
It looks like they want to get rid of all the users with a free API key
because of some users who (unwillingly?) abused the service.
What would be the alternative? I read that Schedulesdirect provides data
for UK now. Does MythTV support the SD-JSON service or only the "old"
SD-DD service?
More information about the mythtv-users
mailing list