Just to touch up on http://support.trakt.tv/forums/188762-general/suggestions/11258295-schedule-movie-refreshes and other things regarding the data refresh. Tbh I have seen little improvement regarding data quality on the site. Really sucks hard that any upcoming movie or newly airing show has a big chance of being "incomplete" or running with subpar artwork. There really needs an additional update job besides the update time on their respective source for the refresh.

(from the "new show calendar")
https://trakt.tv/shows/the-virtues only had a backdrop but posters uploaded over two weeks as well as two days ago
https://trakt.tv/shows/funniest-ever-tv-cock-ups also blank
https://trakt.tv/shows/love-beyond-frontier-2019 has had a non-English "English" poster since Nov 2018...
https://www.thetvdb.com/series/terrace-house-tokyo-2019 same

(stale artwork - at least the image there is gets grabbed at least the one time)
https://trakt.tv/movies/brightburn-2019
https://trakt.tv/movies/the-informer-2019

Also there is still no language fallback for artwork that isn't "English"... there are enough instances where the original language is sufficient for "English" too... and everything is better than blank images. I have been uploading images to the wrong language on TVDB for well over two years now just so that trakt grabs them (or whenever I last requested this)... really would love to stop doing this.

Trakt relies a lot on TVDB for shows. Sometimes TVDB has duplicates which eventually get fixed. But when that happens, these dupes are still available on Trakt.

I suggest coming up with a notification system that warns when a show has a TVDB entry disappear. Who would get notified? Well, mostly you guys, since you're the ones with the ability to remove dupes. Maybe you could also add a warning on the show page that the TVDB entry is gone and that Trakt admins are investigating.

This might cut down on dupes and the constant reports about them.

Note: this implies that shows on Trakt auto-refresh periodically, otherwise the disappearance of a TVDB entry will never be noticed. I assume that is the case.

For a while now different developers or even individual users have been creating ginormous lists with thousands of items but with only three featured on each entry these tend to block everything out since they are also more likely to reach someone else that might throw them a like. Are there any plans to deal with this? Can we hide, re-categorize (non-personal) or downvote lists against this? Some of these serve no purpose other than actually bypassing advanced filters I'd argue or being pinned on kodi dashboards on dubious box setups I'd say...

Here are some examples of this:
https://trakt.tv/users/theultimatec0der/lists (one of his "all shows" has 50K items...)
https://trakt.tv/users/dborg/lists (I think his biggest is gone which was the thousands of "MOVIES NOT INTERESTED IN WATCHING)
https://trakt.tv/users/enormoz/lists
https://trakt.tv/users/zapras/lists/rarbg
https://trakt.tv/users/chas3down/lists/drunk
https://trakt.tv/users/fexi/lists/all-movies-with-german-audio
https://trakt.tv/users/opposite_lock/lists/15-18

Didn't find anything specific in the search but I was certain I saw mentions of this in the past too.

There have been many times when I wonder whether to wait through the credits in the cinema to see if there is an after credits scene, or, when watching a film at home and then leaving the rolling credits on for the music whilst I rate the movie and SURPRISE! Post credits scene that I had no idea about, and I don't like thinking about how many people missed this scene because no one had an idea it existed.

I believe some feedback system where (authenticated) users can vote to say whether the movie has an after credits scene or not. I understand there is some exceptions when films have multiple after credits scenes with more credits in between them but I think maybe just a Yes or No should suffice enough to help people justify whether to wait through the credits or not.

My technical idea for this is something along the lines of.

To allow voting:
a POST request that needs to include a bearer token so that we are sure that only users with accounts can vote. Sent along with the info needed to record a vote, such as movie id and their vote (maybe YES/NO (Boolean?) What about future proofing for other voting options?)

My idea for the storage of a vote is (this is based on assumed knowledge of the current DB structure given the current API responses) a table with columns to store the userid, movieid and their vote. Which could hopefully make changing a users vote easy and avoiding double voting etc.

Fetching the votes will simply be a count of the votes for a given movie for each vote choice.

This is a very loose idea and without knowledge of the current system I can't say my suggestions/ideas are accurate.

Would love to hear reasons for/against this idea.

Thanks

I have reported this issue before, and came across it again with movie:
https://trakt.tv/movies/the-mountain-between-us-2017

This movie on the Trakt web site did not show watched or collected. I know this to be wrong. I checked my local media data (in tinyMediaManager) and sure enough, it is both collected and watched. It also shows that it has already synced to Trakt with this data. This is proven in 2 ways. First, I do not manually mark anything watched in tMM. I mark when watched on Trakt and sync that to tMM. Second, it has the Trakt ID logged, which means that it has synced as that is how the Trakt ID gets populated. As a third method of verification, I have prior data backups from Trakt indicating that it was in fact collected and watched in Trakt in the past.

What steps are taken for data control and integrity? I have personally experienced two conditions where this issue could be happening. First is when there is a merge/deletion of a duplicate. I assume there is a merge process, or at least I hope so vs simply a removal of the duplicate. In this process, is there a pointer of sorts left in the system to where the former Trakt ID will point to the new ID? Second, Trakt has connection problems somewhat often. This happens usually around 06:00 UTC, typically +/- 2 hours. During this time, the site and service are up and down and not stable for a relatively short period of time, maybe 30 minutes if I had to guess. During this time, changes made tend to disappear and cause corrupt data. Corrupt data example is that a movie might appear on an list and it cannot be removed from it (this example has happened to me a few times). IF this is possibly due to maintenance on the site, server(s) or database, is anything done to prevent data writes during such times? Are there any checks to confirm data writes? For example, a write is sent to populate A, the database writes A and sends a reply that A was in fact written with success. Is there a transaction history that a user can review for changes under their account?

I do not know anything about Trakt on the backend, its database or programming. Due to this, I cannot really point to a problem and report it to be fixed. I can only identify that there is an issue and use my data management experience combined with my user experience on Trakt to identify possible problem areas. All I can be sure of is that there is with certainty an issue with data on the server side somewhere and it appears to be rare yet does happen. As a user, there is only so much I can do as access is limited and there is no way to know when data corrections happen exactly what code is used to execute the DB transactions. I hope I have provided enough where someone can review appropriately.