Embedded video players for content hosted on the YouTube video platform (which is owned by Google LLC) may set these third-party cookies and/or use similar technologies to store data in your browser (or other user agent) for purposes such as (without limitation) managing video settings (e.g., tailoring the playback to your connection speed), storing video preferences, providing certain functionality (e.g., allowing you to pause a video at a particular point), showing you advertisements, associating your video viewing and other activity with your Google account (if any), ensuring proper functioning of the service, preventing abuse, and/or compiling user analytics data. Such cookies and/or stored data items may be set by various domains (such as, though not necessarily limited to, youtube.com; youtube-nocookie.com; googlevideo.com; ytimg.com; google.com; accounts.google.com; www.googleadservices.com; and/or doubleclick.net, which is part of the DoubleClick advertising service, also owned by Google LLC). Not all the listed cookies and/or data items are necessarily set in all instances, and there may sometimes be others not listed above, particularly if you are logged into a Google account. Some persist for only a few minutes, or until you close your browser (or other user agent); others may remain in your browser (or other user agent) as long as your individual settings permit. To learn more about what information the YouTube platform and other Google services may collect through and/or in connection with embedded video players and how Google may use that information, see their "How Google uses information from sites or apps that use our services" page and the Google Privacy Policy. For additional information about how Google uses cookies and/or other technologies that may collect and/or process personal information, see the "Technologies" section of their Google Privacy & Terms site and the "Our advertising and measurement cookies" section of their Google Business Data Responsibility site, which includes a detailed list of cookies associated with Google advertising and measurement products. (Those pages do not currently discuss the storage of data in your browser (or other user agent) using technologies other than cookies, e.g., in web storage.) For more information about Google advertising, see the "Advertising" section of their Google Privacy & Terms site. (Google, DoubleClick, YouTube, and other related marks and logos are trademarks of Google LLC.)
VISITOR_INFO1_LIVE, VISITOR_INFO1_LIVE__k, VISITOR_INFO1_LIVE__default, YSC, YEC, _Secure-YEC, PREF, GED_PLAYLIST_ACTIVITY, CGIC, DV, CONSENT, SOCS, AEC, exchange_uid, id, pm_sess, pm_sess_NNN, aboutads_sessNNN, remote_sid, test_cookie, use_hitbox, _gac_gb_, __gads, _gcl_, _gcl_au, _gcl_aw, _gcl_dc, _gcl_gb, _gcl_gf, _gcl_ha, __gpi, __gpi_optout, __gsas, Conversion, 1P_JAR, ACLK_DATA, GPS, NID, ENID, ANID, AID, TAID, IDE, APIS, SAPISID, DSID, HSD, SID, HSID, SSID, SNID, SIDCC, FCCDCF, FCNEC, FLC, FPGCLAW, FPGCLDC, FPAU, GAPS, GLC, N_T, OTZ, PAIDCONTENT, RUL, TAID, UULE, LOGIN_INFO, Permission, yt.innertube::nextId, yt.innertube::requests, yt-html5-player-modules::subtitlesModuleData::display-settings, yt-html5-player-modules::subtitlesModuleData::module-enabled, ytidb::LAST_RESULT_ENTRY_KEY, yt-player-autonavstate, yt-player-bandaid-host, yt-player-bandwidth, yt-player-headers-readable, yt-player-lv, yt-player-quality, yt-player-volume, yt-remote-cast-available, yt-remote-cast-installed, yt-remote-connected-devices, yt-remote-device-id, yt-remote-fast-check-period, yt-remote-session-app, yt-remote-session-name, application_server_key, AuthKey, DeviceId, Endpoint, HighPriorityNotificationShowCount, HomePromptCount, HomePromptTime, IDToken, IndexedDBCheck, LogsDatabaseV2, P256dhKey, Permission, PromptTags, RegistrationTimestamp, shell_identifier_key, TimestampLowerBound, yt-serviceworker-metadata
Jay Leno did a video about the Jetfire last year with it and that has 1M+ views, I think there is definitely interest in the subject.
Very much agree, the F-85 deserves its finished story and the Jetfire was as much a part of that as it was also another technical breakthrough that GM pioneered and then forgot about.
Your site, in my opinion, is the preeminent source of interesting stories on somewhat obscure subjects I’ve ever come across. Some years ago I read Halberstam’s “The Reckoning,” a source you frequently cite, and I find your style very similar. With that said, a story on the Oldsmobile Jetfire would be a wonderful read. I’m very much looking forward to it.
The challenge that I have not infrequently faced is finding what I regard as the “sweet spot” in terms of subject matter, which is something about which a workable (read: large) amount of information is available to me, but where I feel like there’s still something useful I can say about it. There are some subjects that meet the first criterion and not the second, and a fair number that fit the second and not the first. I have taken a certain pride in being able to chronicle some things in a fair amount of detail that don’t get a lot of play otherwise, although whether anyone else is that interested in, for example, the origins of the Ford Fiesta or the history of the JDM Toyota Soarer. Sometimes, the information that’s generally available includes a lot of errors and misconceptions that are worth attempting to clear up, or there’s some technical aspect I have to teach myself in order to explain, or something once familiar is becoming obscure in a way that seems to deserve chronicling. (For instance, given how influential and ubiquitous the original Hydra-Matic used to be, I daresay it’s no longer very well-understood.)
The Jetfire fits into an odd space where it is a relatively small subject (given that I’ve already covered the origins of the Y-body cars at some length) — which is good — but there’s already a fair number of articles about it, and most of them say more or less the same things. So, the question is whether I have anything to add to that discussion and whether people consider it played out or overly familiar.
Personally, I’d love to hear more about it.
Whatever you choose to write about I will read. I was thrilled that you published more articles this year, I thought that with the loss of a lot of your materials a while back and your concern about California’s privacy laws spelled the end for you.
This website has been a treasure trove. I wish that I had the talent for writing and research that you do. And so, I always welcome new articles should you choose to produce them.
I’m still pretty concerned that it does, particularly now that several other states have rolled out their own variation on the often ill-framed California law even as California doubles down. (The latest iteration of the law is more lucid and reasonable in some respects and, uh, definitely not in others.)
The new regulations have been issued, apparently with no opportunity for public comment (at least none I was notified about, and I was on the mailing list for comment on the original regulations), and they are FAR, far worse than I feared. They actually make publishing itself more or less illegal, and devastate the First Sale Doctrine and freedom of expression. They nullify a lot of the statute’s attempts to strike a reasonable balance between privacy and practicality, and they’re also technologically ambitious in a way that isn’t currently feasible except for big companies. It’s horrifying, and since they delayed and delayed, there’s no opportunity to even comment.
Definitely do the article.
Glad to see you’re still writing. As the author of a blog with a lot of automotive content, I think being an information “aggregator” is a useful niche.
I have written about the F-85 Jetfire, but would very much welcome your expert perspective.
I think the “AUWM” contribution is often to bring some light to the individuals involved in engineering, designing, styling, or marketing a car or innovation–and, other than John Beltz, the people involved in Oldsmobile around this time are not exactly household names. And the decision at Oldsmobile to turbocharge that Buick-block engine must have been some sort of compromise–if anybody knew (or claims to know) how it was made, that would be interesting.
Of course, none of this means that Jetfire is the best idea on your mind, just that it can be a good one.
I have spent the past weeks putting together a very sizable mass of research information related to the Jetfire, including various technical papers and the service manual. Some of it is tangential, but probably necessary background at least for me (e.g., regarding the development of aircraft turbo-supercharging, of which I know a little, but not a lot), but it eventually (a) gave me a reasonable grasp of how the Jetfire fluid injection system operates, which is surprisingly involved, and (b) uncovered some interesting details that seem worth relating.
Good! I always learn something – wish I could remember it all! (But I can come here and re-read it.
A later iteration of turbocharging with GM is the ’92-’93 GMC Typhoon SUV and Syclone pickup. Possibly add those to your article. Thanks again for what you do!
I for one will avidly read any new content you might write; I admire your determined persistence, despite California’s well-intentioned legal incompetence. Long live AUWM!
Where it presently stands is that I have a length more or less complete draft. (The conclusion is still a little muddled.) I have rearranged and rewritten big sections of it in trying to decide exactly how much I wanted to get into the history of supercharging, beyond the history of turbocharging, which is more directly pertinent. It includes almost every detail I could dig up on the Jetfire, and more than I had originally intended on the turbocharged Corvair.