Hey, would you mind sending some screenshots of where are you seeing January 1st, 1970 date being displayed after marking? Might be just a UI thing.
Thanks we’ll take a look.
Hi, it’s been months and choosing “unknown date” still sets the date by default to January 1st, 1970.
When a movie is set to unknown, I’m guessing the backend assigns a Unix epoch of 0. Instead of intercepting this, the frontend simply translates it to “watched on January 1, 1970.” This should not be the case and media with an unknown watched date should not display a watched date and should be excluded from analytics (except what’s independent from the watched date, such as number of movies watched).
Please take a look @mike.d.
Setting the watched date as “Unknown” is great if you don’t know when you watched it, and for it to have a default date of 1st January 1970 id fine with me.
At least this way you know that anything listed as watched on 1st January 1970 means that you marked it watched but was not sure when you watched it.
When you do the export you can then see all those listed as watched on 1st January 1970 means it was watched at an unknown date.
Don’t mess with it and cock it up.
Of course it’s “fine” as it is. But it messes up and skews the data (such as number of movies watched by date/year). Let’s not settle for the bare minimum.
Just discussing 
OK, but what is the difference between 1st January 1970 and Unknown Date when it comes to stats.
Unknown Date will skew the data for that (date) just as 1st January 1970 will, but at least we would know that 1st January 1970 IS the date that you marked something watched but didn’t know when you watched it.
Unknown Date has to be something doesn’t it? (not techy so no idea how it works in the bowels of computer speak) Unless they can literally make a Calendar entry that says Unknown Date.
Or should the Unknown date just be 1st January 1900, there would be no one alive using Trakt that would have watched anything back then and OK that date would have masses of watched items but we would know the reason why.
We use the 1970 internally as a “marker” for Unknown Date. Basically if you see this date in any of our UIs platform it should be considered a bug.
If possible just pinpoint exact spots where you see it to fix this quickly 
If analytics are also skewed let me know where exactly and well take a look
Not sure if this counts but I see the 1970 date on every item I have marked as “unknown date” and also it appears in the export files.
Not sure if this counts but I see the 1970 date on every item I have marked as “unknown date” and also it appears in the export files.
Which platform and where in UI - screenshot would be the best to solve this 
For exports I’d say its expected - export file needs to encode “Unknown” somehow so during import its recreated.
Statistics used to have a start date and end date option. Now, only All Stats is available and I believe the Unknown Date entries are included. Since some people might want the unknown date entries in their stats, the date range is a preferred option.
The unknown date entries show up in my Year In Review for 1969 (date is Dec 31, 1969 7:00pm… US Eastern Time).
Is this screenshot from phone Trakt mobile app or from mobile Chrome?
Could you also screenshot us “chrome on the web” where you see it? Thanks
Thanks, for web I will pass it on.
For Android App the screenshot tells me its still the “old” app. I can just say here that we do not support or update it anymore so things like that might not be handled properly.
Old app ! Oh OK no idea I’m just using what I had, it still updates the info on to Trakt though doesn’t it?
Is there a new app?
Or is it just mobile using the web now?
Old app ! Oh OK no idea I’m just using what I had, it still updates the info on to Trakt though doesn’t it?
Yeah I guess if you are fine with this you can keep using it.
Yes - the new app is available via Google Play Store, its a normal native app - not web.