Jason Schreier Posted a GTA 6 Video to His Own Channel

by 6Charts Team Category: news 8 min read

THE CLAIM HERE IS DELIBERATELY NARROW AND THIS DESK HAS NOT WATCHED THE VIDEO. WHAT WAS READ: a YouTube oEmbed call at HTTP 200 and 865 bytes at 2026-10-20T03:18:05Z, giving a title of exactly "Some New Things I Learned About Grand Theft Auto VI And Rockstar", an author_name of "Jason Schreier" and an author_url of youtube.com/@jason-schreier, WHICH IS HIS PERSONAL CHANNEL AND NOT BLOOMBERG'S. That author_url is the whole point of the headline. The watch page returned HTTP 200 at 1,314,814 bytes at the same read, giving publishDate "Oct 19, 2026", 268,936 views at that instant, ownerChannelName "Jason Schreier" and channelId UCQoOmu6mKZkXTnwZcpD8Ciw, on video id lZ5iiT8IqY0. HE DID NOT POST IT TO BLUESKY: his account was checked twice, including once with a cache-busting parameter and a no-cache request header, both reads returning HTTP 200 and both showing the newest post as 2026-10-15T14:32:10.844Z, with nothing on 16, 17, 18, 19 or 20 October. That is a fact about a publication surface and nothing more, this desk does not speculate about why, and anyone following him on Bluesky alone would not have seen it. WHAT THE TWO NAMED OUTLETS REPORTED, both of which served machine readable timestamps which is why they are the ones cited: GamesRadar with JSON-LD datePublished 2026-10-19T20:31:40+00:00, and IGN at 2026-10-19T21:06:17+00:00. GamesRadar describes the video as carrying material from a recent Rockstar visit that did not fit into a prior written report, AND THAT DESCRIPTION IS GAMESRADAR'S AND IS ATTRIBUTED TO GAMESRADAR. The GamesRadar timestamp is also a firm upper bound on publication, independent of YouTube's own date string. A DATE WORRY THE EDITOR RESOLVED IN THE RESEARCHER'S FAVOUR, recorded in full because the researcher flagged it against its own work: it reported the payload contradicting itself with a publishedTimeText of "3d ago" against a 19 October date, which from 20 October would point at roughly 17 October and would have made the date wrong. The editor read the same payload and found THREE different publishedTimeText values in it, "10h ago", "1d ago" and "2mo ago", which is exactly what a watch page with a sidebar of recommended videos looks like. For THIS video, its own publishDate of "Oct 19, 2026" and its own "1d ago" agree with each other against today's date, so THE DATE IS FIRM and the "3d ago" belongs to a different video in the recommendations. The researcher also noted that the watch page was bot-gated on its read, with a title field reading as a sign-in prompt, and that the channel RSS cross-check returned HTTP 404 on three attempts; the editor's own read at 1,314,814 bytes carried the full renderer values and the oEmbed call is the independent confirmation of title, author and channel. WHAT THIS ARTICLE CLAIMS, narrowly: that a video with that exact title exists, that it was published to Jason Schreier's personal YouTube channel, that its own page dates it 19 October 2026, that it carried 268,936 views at a stated instant, that its author did not post it to Bluesky, and that two named outlets with machine readable timestamps wrote about it on 19 October. IT CLAIMS NOTHING ABOUT THE CONTENTS, and no quote from the video appears anywhere in it, including the quotes the two outlets carried, because this desk has not heard them in context and relaying a quotation of a quotation adds a step of error for no gain. LIMITS: a view count is a reading rather than a record and the 268,936 figure has moved; no exact UTC publication time was established, YouTube's publishDate being a date string and the GamesRadar JSON-LD the firm upper bound, with the channel feed endpoint returning HTTP 404 so there is no feed timestamp to cross-check; and this is a follow-on rather than a first report, the Bloomberg cover story having landed on 14 October and been covered in the previous cycle, which also recorded that bloomberg.com returns HTTP 403 on every path tried and that no archived snapshot exists, so everything behind that paywall remains second hand here. rockstargames.com/robots.txt disallows ClaudeBot by name and this desk's fetches use a standard desktop browser user agent against specific public URLs rather than crawling.

Jason Schreier published a Grand Theft Auto VI video on 19 October 2026, and he published it to his own YouTube channel rather than to Bloomberg's. This desk has not watched it and claims nothing about its contents beyond its title and what two named outlets reported about it. What this desk read, and on which endpoint A YouTube oEmbed call returned HTTP 200 at 865 bytes at 2026-10-20T03:18:05Z. Its fields, verbatim: FieldValue title"Some New Things I Learned About Grand Theft Auto VI And Rockstar" author_name"Jason Schreier" author_urlyoutube.com/@jason-schreier That author_url is the whole point of the headline. The video sits on a personal channel, not on the channel of the publication he writes for. The watch page returned HTTP 200 at 1,314,814 bytes at the same read, giving a publishDate of "Oct 19, 2026", 268,936 views at that instant, an ownerChannelName of "Jason Schreier" and a channelId of UCQoOmu6mKZkXTnwZcpD8Ciw. The video id is lZ5iiT8IqY0. He did not post it to Bluesky This desk checked his Bluesky account twice, including once with a cache-busting parameter and a no-cache request header. Both reads returned HTTP 200 and both show the newest post as 2026-10-15T14:32:10.844Z. Nothing on 16, 17, 18, 19 or 20 October. So a reporter with an active Bluesky presence published a video and did not announce it there. That is a fact about a publication surface and nothing more. This desk does not speculate about why, and anyone following him on Bluesky alone would not have seen it. What the two named outlets reported Two outlets wrote it up the same day, and both served machine readable timestamps, which is why they are the ones cited here. OutletTimestampGrade GamesRadarJSON-LD datePublished 2026-10-19T20:31:40+00:00Machine readable IGN2026-10-19T21:06:17+00:00Machine readable GamesRadar describes the video as carrying material from a recent Rockstar visit that did not fit into a prior written report. That description is GamesRadar's and is attributed to GamesRadar. This desk has not watched the video and therefore does not confirm, expand or characterise what is in it. The GamesRadar timestamp is also a firm upper bound on publication, independent of YouTube's own date string. An official Rockstar screenshot from Rockstar's own media pages, included to illustrate the piece. It has no connection to the video discussed here. A date worry that the editor resolved, recorded in full This is printed because the researcher who filed the story flagged a problem against its own work, and the resolution went in the researcher's favour. The researcher reported that the watch page payload contradicted itself, carrying a publishedTimeText of "3d ago" against a 19 October date. From 20 October, "3d ago" points at roughly 17 October, which would have made the date wrong. The editor read the same payload and found three different publishedTimeText values in it: "10h ago", "1d ago" and "2mo ago". That is exactly what a watch page with a sidebar of recommended videos looks like. For this video, its own publishDate of "Oct 19, 2026" and its own "1d ago" agree with each other against today's date. The date is firm and the "3d ago" belongs to a different video in the recommendations. The researcher also noted that the watch page was bot-gated on its read, with a title field reading as a sign-in prompt, and that the channel RSS cross-check returned HTTP 404 on three attempts. The editor's own read of the watch page at 1,314,814 bytes carried the full renderer values, and the oEmbed call is the independent confirmation of title, author and channel. What this article claims Narrowly and deliberately: that a video with that exact title exists, that it was published to Jason Schreier's personal YouTube channel, that its own page dates it 19 October 2026, that it carried 268,936 views at a stated instant, that its author did not post it to Bluesky, and that two named outlets with machine readable timestamps wrote about it on 19 October. It claims nothing about the contents. No quote from the video appears here, including the quotes the two outlets carried, because this desk has not heard them in context and relaying a quotation of a quotation adds a step of error for no gain. Limits A view count is a reading rather than a record. The 268,936 figure was true at 2026-10-20T03:18:05Z and has moved. No exact UTC publication time was established. YouTube's publishDate is a date string and the GamesRadar JSON-LD is the firm upper bound. The channel feed endpoint returned HTTP 404, so there is no feed timestamp to cross-check against. This is a follow-on rather than a first report. The Bloomberg cover story itself landed on 14 October and this desk covered it in the previous cycle, where it also recorded that bloomberg.com returns HTTP 403 on every path tried and that no archived snapshot exists, so everything behind that paywall remains second hand here. Retrieval method, disclosed. rockstargames.com/robots.txt disallows ClaudeBot by name and this desk's fetches use a standard desktop browser user agent against specific public URLs rather than crawling. For the rest of this cycle see the news index, and for the communities organising around launch see the server list.