The Most Terrifying Cults to Ever Exist | Good Enough | History Teacher Reacts



Cults are as old as religion. Some cults are bizarre. Some cults are dangerous. Some cults are TERRIFYING. Good Enough shares the most terrifying cults in history. Mr. Terry talks about the history of religion, the psychology behind cults, and compares and contrasts them.

Original Video: https://youtu.be/ccnvYegunQ0?si=qtQzrW53Fc6e0WUq

Join my channel to get early-access to new videos!
https://www.youtube.com/channel/UCCbJSm-pLHjna1JW9X31N8g/join

Links:
Gaming channel: https://www.youtube.com/c/MrTerryGaming
Discord – https://discord.gg/AbktyXv38a
Twitter: https://twitter.com/mrterryhistory
Twitch: https://www.twitch.tv/mrterryhistory
Tik Tok: https://www.tiktok.com/@mrterryhistory
Instagram: https://www.instagram.com/mrterryhistory
Facebook – https://www.facebook.com/Mr-Terry-History-109138461571454/
TeeSpring – https://mr-terry-history.creator-spring.com
Patreon – https://www.patreon.com/MrTerry
Streamlabs – https://streamlabs.com/mrterry2
PayPal – https://paypal.me/mrterryhistory

For all business inquiries: [email protected]

source

26 thoughts on “The Most Terrifying Cults to Ever Exist | Good Enough | History Teacher Reacts”

  1. Hi Mr Terry and greetings from the UK.

    I am a Data Engineer and Analyst so if helpful I will explain Y2K.

    The Y2K problem stemmed from the common practice of representing years with only the last two digits. For example, the year 1998 was stored as "98." As the year 2000 approached, systems that were not Y2K compliant could misinterpret "00" as 1900 instead of 2000. This occurred because the system might assume that "00" represents the year 1900 since it follows the pattern of two-digit years.

    For instance, if a system calculated the difference between two dates and encountered "00," it might incorrectly deduce that the date is in the 1900s instead of the 2000s, leading to potential errors in calculations, data processing, and other system functions. To avoid these issues, organizations had to update and modify their systems to handle four-digit year representations, ensuring accurate date processing.

    The transition from using two-digit representations for the year (e.g., "98" for 1998) to a four-digit format (e.g., "1998"). This shift allowed systems to distinguish between the years in the 1900s and 2000s.

    It was overblown and ideas of nukes going was speculative at best but computer development was already working to counter the issue. It was just a pain for most as people had to update their code, backlogged their old data when transitioning to new etc.

    Reply
  2. I have no idea how good the NYE 2000 party was, because I was at work until 3AM, as I was in charge of our company's Y2K compliance process. We'd re-written all of our accounting, payroll, scheduling, and data security programs, plus a few other things I can't recall at the moment, and I had to go through everything and make sure it was functioning properly.
    No idea what they thought I'd do if anything was broken, because I can't write COBOL or FORTRAN.

    Reply
  3. In the defense of the Y2K thing, computers used to be programmed as 19xx for the year. That means that as soon as the year changed to 2000 the computers would think that it was 1900. Can you imagine having all banks have their accounts revert to the amount of money recorded on those computers for a year that existed before modern computers were invented? The Y2K problem was fixed before it became an actual problem.

    Reply
  4. RE: Y2K …. I mean, yeah. There were plenty of "doomsdayers," to be sure. But it was a legit issue that A LOT of effort was put in to fix it. People who could program in COBOL where in very VERY high demand, as well as programmers who could deal with embedded systems. COBOL = COmmon Business Oriented Language. One of the very early languages that became obsolete. But a whomp-ton of businesses all over the world still had systems running software that was made using COBOL.
    The thing is, COBOL (and plenty of other non-COBOL software, mind you) wasn't able to go from 1999 to 2000. They would roll back to 1900. Or simply totally crash.
    Now consider when, for instance, bank transactions are attempted a century before the actual current date, in dispute with banking records as, of course, such a transaction is impossible. And that's simply banking. Embedded systems involved in infrastructure could well shut down when the date rolls back. If not rolling back to 1900, then totally crashing because it's attempting to exceed its "counting limit," which has to do with how much memory was allocated to handling that.
    Like with old video games where the high score rolls over. Except THEY were often smart enuf to include an indicator of how many times the score had rolled over.
    But no one thought of that with the business systems and such. So it HAD TO be fixed. And they did. Which is WHY nothing happened. Nothing happened because people talked about it and were like, "Oops! We need to deal with this." and then they did. It wasn't simply, "People said something was going to happen but nothing did, so they were wrong."
    To be honest, the "doomsday" scenario was totally possible. No one really knew. I wasn't a doomsdayer, and tried to talk people down from it. But I knew some "preppers" who were convinced it would be alpaca lip tic.

    Reply
  5. Yes, the Y2K problem was a serious issue that cost many industries and government a lot of money to resolve. It was because when most programs were originally developed, they used a two-digits value to represent the year to save space because memory was very limited and costly. The base problem would be that 1999 would be presented by 99 and 2000 would be represented by 00. Also depending how the number is represented in code, this could turn the year into a negative value. It is a similar problem when video games like Donkey Kong roll over their score or level count. It was a true historic event.

    Reply
  6. Their artwork is giving hardcore David Firth vibes and I am here for it 😂

    That being said, I understand why but there's some pretty (I think) noteworthy context missing from some of these descriptions. Like how, say, Jonestown was ridic underdeveloped prior to Jones' and the other members' arrival, which is why they were essentially put to slave work. Also, Jones held consistent mock s*****e's so that is why a LOT of the people who passed that day were unsuspecting. Jones also recorded audio of the whole thing, including taking his own life.

    Also, I guess I get why it's left out but I think it's an important missed opportunity to talk about the history of Number 3, whose name I always forget, that began essentially by ploy of a "minor attracted person" to gain ritualistic "right" to… children, after convincing people they were the "true descendants of the Knights Templar," which is WILD.

    Reply
  7. The people of Jonestown knew there was poison in the grape juice. Another person already commented about it. A lady tried to stop it. Many people tried to avoid it. Many people were forced to drink it or were injected. This included kids. Not many, but some escaped.

    Reply
  8. Y2K could have been very problematic if it wasn't detected early enough for everyone to adapt. Humanity getting together to solve a potential problem is one of the "up with human" feathers in humanity's cap.

    Reply
  9. The cult from Miami,
    “Yahweh Ben Yahweh”. Hulon Mitchell, legally changed his name.
    There were many believers in prison, long after he was arrested.
    Murders, and lots of crazy stuff happened in and because of this cult.

    Reply
  10. So you were right about one of these groups having to do with Haileys Comet… that was Heavens Gate…they believed that by dying on that day they could ascend to the UFO that tailed the comet…

    Reply
  11. Some more perspective on the Y2K bug fear: I was an older teen at the time, but my dad is a computer programmer so he was able to help me a good understanding of what it actually meant – and I felt like a lot of the people who were freaking out were doing so more out of ignorance. Starting years before the 1/1/2000 deadline people saw the potential problem and updated computer systems to handle it, with actually a lot of focus on checking, fixing, and double checking the most problematic computer systems – make sure the nukes would be fine, for instance. I remember very shortly before New Years there was a computer scientist on the news being interviewed about whether or not he was worried – and I remember I felt that he seemed reasonably level-headed and trustworthy in his response so it really helped me go from a little bit worried to more relaxed. He said that he wasn't worried, except that there was a slight chance of a short power-outage happening somewhere – the electrical grid was deeply embedded with all sorts of controllers so it was impossible to check them all but he figured if there was a problem it would be easily solved. Other than that he said that the elevators in really old buildings might reset at midnight – automatically going down to the bottom floor before resuming normal operations. So yeah, I wasn't really worried – and I didn't hear anything about even those two things happening.

    Reply

Leave a Comment