Should still be changed to June 3rd since every other source (IMDB, TVDB, RottenTomatoes etc.) has it listed as June 3rd release date. The incorrect date creates issues with other services that use TMDB like Trakt (every episodes release date will technically be a day wrong on the calendar).
All our dates here are based on the local date in the original country of the series.
Amazon Prime advertize its releases in GMT time, so we need to convert the date in local US date for the US series.
Oh so this is the source of the error. Actually indeed they released it June 3rd 00:00 GMT, but if they advertise the date in GMT you should NOT be converting. The show might be US produced but it's an international release, advertising the date as US centric in this instance is wrong, and generates calendar errors on services that rely on your API.
Furthermore what US Time zone are you taking as the point of reference ? Hawaii ? Alaska ? West ? Mountain, Central, East ?. If the release date was for example June 3 08:00 GMT (and there are a few in this case), it would still be June 2 In Hawaii (9PM), Anchorage (10PM) Los Angeles (11PM), but June 3 In Santa Fe (12AM), Kansas City (1AM), and Washinton DC (2AM). You can see how absurd it is ? Please stick to the stated the service release date, this conversion policy only introduces confusion for everybody.
Or, and this might be too radical and rational an idea, an idea, evolve the API, add a field 'GMT Release date' and 'Country of origin release date' and let the services that deal with the API sort it out then, not guess what your intention was.
All evidence pointing to the contrary, not to mention the numerous reports about this problem would tell you it's not, but we'll just learn to compensate for your ways and each petition the various services using you API to compensate for your way to change the release dates.
Again, reasonable solutions would exists to address the issue in a satisfactory manner for all involved parties, but I can see there is no point in discussing further when the staff attitude is "we are right and the rest of the world is all wrong so there".
All our dates here are based on the local date in the original country of the series.
Amazon Prime advertize its releases in GMT time, so we need to convert the date in local US date for the US series.
The time it was released doesn't matter. The important thing is to use the date that Amazon Prime Video used: June 3rd. If you are going to use it by release time then you can start changing the date of all Prime Video series.
Reply by superboy97
on March 14, 2022 at 1:57 PM
Amazon Prime release new content at 0h GMT on their advertised date, which mean the evening of the previous day in the US (this is a US series).
Reply by UndefinedxJoker
on March 14, 2022 at 6:24 PM
Ah ok I didn’t know that. Thanks!
Reply by Joshua
on June 2, 2022 at 2:03 PM
Should still be changed to June 3rd since every other source (IMDB, TVDB, RottenTomatoes etc.) has it listed as June 3rd release date. The incorrect date creates issues with other services that use TMDB like Trakt (every episodes release date will technically be a day wrong on the calendar).
Reply by superboy97
on June 2, 2022 at 2:11 PM
You need to ask this services to correct their software.
As explained, our data here are correct.
Reply by Joshua
on June 2, 2022 at 2:53 PM
The official trailer for Season 3 also say June 3rd, look at all the other posts from users to have the date corrected.
Reply by superboy97
on June 2, 2022 at 2:58 PM
All our dates here are based on the local date in the original country of the series.
Amazon Prime advertize its releases in GMT time, so we need to convert the date in local US date for the US series.
Reply by RxB
on June 3, 2022 at 2:36 AM
Oh so this is the source of the error. Actually indeed they released it June 3rd 00:00 GMT, but if they advertise the date in GMT you should NOT be converting. The show might be US produced but it's an international release, advertising the date as US centric in this instance is wrong, and generates calendar errors on services that rely on your API.
Furthermore what US Time zone are you taking as the point of reference ? Hawaii ? Alaska ? West ? Mountain, Central, East ?. If the release date was for example June 3 08:00 GMT (and there are a few in this case), it would still be June 2 In Hawaii (9PM), Anchorage (10PM) Los Angeles (11PM), but June 3 In Santa Fe (12AM), Kansas City (1AM), and Washinton DC (2AM). You can see how absurd it is ? Please stick to the stated the service release date, this conversion policy only introduces confusion for everybody.
Or, and this might be too radical and rational an idea, an idea, evolve the API, add a field 'GMT Release date' and 'Country of origin release date' and let the services that deal with the API sort it out then, not guess what your intention was.
Reply by superboy97
on June 3, 2022 at 4:01 AM
This is not the "source of the error", but just the explanation.
Our data are correct.
Reply by RxB
on June 3, 2022 at 4:31 AM
All evidence pointing to the contrary, not to mention the numerous reports about this problem would tell you it's not, but we'll just learn to compensate for your ways and each petition the various services using you API to compensate for your way to change the release dates.
Again, reasonable solutions would exists to address the issue in a satisfactory manner for all involved parties, but I can see there is no point in discussing further when the staff attitude is "we are right and the rest of the world is all wrong so there".
Reply by Uzui
on June 3, 2022 at 6:09 AM
The time it was released doesn't matter. The important thing is to use the date that Amazon Prime Video used: June 3rd. If you are going to use it by release time then you can start changing the date of all Prime Video series.
Reply by superboy97
on June 3, 2022 at 10:50 AM
The important thing is to use the local date of the originj country at the time of the release to be consistent with all the other series.
All the Amazon Prime series are based on this model.
Reply by UndefinedxJoker
on June 3, 2022 at 10:54 AM
This site is a joke. Just put the release date that Amazon advertises!
Reply by ljransom1
on June 9, 2022 at 1:42 PM
Everyone made valid points here. Superboy, nobody likes you.