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
Glad to hear it, Aaron. If Ate Up With Motor went away it would be a true loss for automotive enthusiasts.
Absolutely!! I only found this site about 3 years ago and it is an internet wonder, an example of the greatness that the rest of the internet can aspire to. It saddens me that there have not been many updates since I first discovered this site, but I continue to hold hope.
My sentiments exactly. I read literally the whole site, end to end, while I was recuperating after a major car crash 3 years ago. It has since become a valuable reference for me, and I still check back periodically for anything new.
So, yes. This is great news for me, and thank you very much for keeping AUWM going, Mr Severson.
In an era where everything is monopolised by social media and wikipedia, it is very nice to have an alternative like you and oldcarmanuals, full of comprehensive information in every way. Keep up the good work!
You made an excellent piece on GMs transmissions, write one about Ford’s and Chrysler’s.
I have, although not as specifically. “Secrets of the Simpson Gearset” (https://ateupwithmotor.com/terms-technology-definitions/simpson-gearset/) talks at length about the mechanical layout of the Ford C4/C6 transmissions and of TorqueFlite, while “Giving Slip the Slip” (https://ateupwithmotor.com/terms-technology-definitions/split-torque-lockup-converters/) talks a great deal about a number of Ford transmissions, including the infamous AOD and the automatic used in the Escort and Tempo, as well as Chrysler’s lockup torque converter.
There’s of course more that could be said about TorqueFlite, which is one of the longest-running and most successful automatics in the U.S., although it’s also more familiar to many readers and other sources like Allpar have a lot of information about it. The aspect that most interested me was the Simpson gearset, which addresses the question of how much TorqueFlite really had in common with Turbo Hydra-Matic or the Ford C6, a frequently contentious point.
One possibility – loan or sell your content to another site like Drivetribe or The Drive. That would keep your work on the Internet at no charge to you. Perhaps they would let you add more articles. You could add in a clause saying that if they took the articles down then you would have the right to put them up yourself, or take them to another site.
That would actually risk creating a different problem: California has decided that if I submit more than a modest number of items for publication a year, the publisher is my legal employer, which could mean they’d own all rights to my work as a work made for hire. (I don’t think the morons in the Legislature who passed this stupid law considered the latter ramification, but it’s a very significant concern. Something being deemed a work made for hire is different than selling or licensing the rights; it says you were never the legal author to begin with!)