God’s Ultimate UNO Reverse Goes Wrong  🔗 **Source:** [God’s Ultimate UNO Reverse Goes Wrong](https://youtube.com/watch?v=DQfXZijoAA0&is=KP9wli3G9UOINWKn) > [!note]+ Document Notes > --- > tags: [titulus-crucis, acrostic-apologetics, tetragrammaton, hebrew-aramaic-debate, greek-epigraphy, viral-apologetics] > author: Dan McClellan > source: Dan McClellan (YouTube) > reference: https://www.youtube.com/watch?v=DQfXZijoAA0 > date created: 2026-09-26 16:23 > --- > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > # 🏷️ Title: God's ultimate UNO reverse goes wrong > ## 🧭 Table of contents > - [📝 Summary](#-summary) > - [📖 Main content](#-main-content) > - [🗒️ Notes](#️-notes) > - [📚 References](#-references) > - [🗣️ Paraphrase](#️-paraphrase) > - [📰 Newsletter](#-newsletter) > - [✅ Action items](#-action-items) > - [🧪 Hypotheses](#-hypotheses) > - [📊 Methodology](#-methodology) > - [❓ Questions](#-questions) > - [🔮 Future research](#-future-research) > - [💡 Implications](#-implications) > - [🧠 Learning styles assessment](#-learning-styles-assessment) > - [📊 Accessibility assessment](#-accessibility-assessment) > - [🌍 DEIB assessment](#-deib-assessment) > - [✅ Logical validity](#-logical-validity) > - [🛡️ DARVO analysis](#️-darvo-analysis) > - [🎯 Conclusion](#-conclusion) > - [🔄 Refactor appendix](#-refactor-appendix--gods-ultimate-uno-reverse-goes-wrong) > ## 📝 Summary > - **What happened.** Dan McClellan (biblical scholar, "data over dogma" educator) posted an 8-minute stitch-format response on 2026-09-26 to a viral apologetics clip. The clip claims the sign Pilate placed over Jesus (the titulus, John 19:19-20) read "Jesus Christ of Nazareth, King of the Jews," that in Hebrew the first letter of each of its four words spells the divine name YHWH, and that a sign meant to mock Jesus therefore ended up praising him: God's "ultimate UNO reverse." > - **The claim under rebuttal.** The Hebrew acrostic works only if the phrase contains four words starting yod-he-vav-he. The clip's reconstruction supplies the vav by inserting a conjunction ("and") that no gospel account of the sign contains. > - **McClellan's reading.** Three problems, ranked. (1) The graphic's Greek uses capitalized initials, lowercase, breathing marks and accents, a manuscript convention for literary copies, not public signage; it was pasted from a website carrying the Greek of John 19. (2) The Hebrew adds a word. Without the added vav the initials do not spell YHWH; the added "and" also breaks the apposition of the Greek ("Jesus the Nazarene, king of the Judeans"). (3) A lesser, contested point: most translations render John's "Hebrew" as Aramaic, and he declines to take a side. > - **Why it matters.** The video is a compact demonstration of a checkable original-language claim failing a check any reader can run: count the words in John 19:19 and compare. It is also a case study in how a fabricated detail travels through creators who cannot read the language they are quoting. > - **Key stakeholders.** The unnamed clip creator (never identified in the transcript); McClellan; the audience the clip targets; scholars in the Hebrew-vs-Aramaic titulus debate McClellan mentions without naming. > - **Risks and tradeoffs.** McClellan's textual case is strong and verifiable. His motive claims are not: he calls the creator a liar and a grifter at 00:02:09 and 00:04:20, then at 00:08:00 says the creator "didn't know any better and was deceived." The generalization that social-media Christians are "deeply, deeply, deeply gullible" (00:04:20) carries no evidence. Keep the philology and quarantine the psychology. > - **Bottom line.** The acrostic requires editing the text it claims to decode. That single fact settles the case; the rest of the video is commentary on why the claim spreads anyway. > ## 📖 Main content > **The clip being answered.** The rebutted video (voiced by an unnamed male creator, interleaved with McClellan's responses and marked by ">>" in the auto-transcript) runs a familiar apologetic. It shows a graphic of the crucifixion placard in Hebrew, Greek and Latin, asserts that Hebrew Bible scholars encoded hidden messages in first letters, reconstructs the Hebrew line, reads the initials as Yahweh, and lands the punchline at 00:06:29: "Oh yes, it does. But not a code, a name. Yahweh. Boom." It closes at 00:07:14 with the theological payoff: evil put Jesus on the cross and was defeated by doing so. The opening frames all of this as God pulling "the ultimate uno reverse card" (00:00:00). > **Problem one: the Greek is typeset like a medieval manuscript.** McClellan's first and, by his ranking, most serious objection is orthographic. The graphic's Greek has each word beginning with a capital followed by lowercase, plus rough and smooth breathing marks and accents (00:00:00). He says that convention belongs to "more sophisticated literary texts that were being copied out" and would not appear on "a placard being created to place over the head of an executed person" (00:00:44). His inference about method: the creator "copied and pasted off of some website that had the Greek of John 19 on it" (00:00:44). The mechanism behind the objection, which he states rather than documents, is that first-century public inscriptions used undivided capitals without diacritics; polytonic minuscule is a later scribal system. That is the standard account in Greek paleography and is checkable against any inscription corpus. > **Problem two: the Hebrew has an extra word, and the extra word is the whole trick.** This is the load-bearing section, 00:02:09 to 00:03:37. The acrostic needs four Hebrew words whose initials are yod, he, vav, he. McClellan says the creator "has added an entire word to the Hebrew that simply doesn't exist in any of the New Testament's descriptions of what was written on this sign" (00:01:26 into 00:02:09). The added word is a vav, the conjunction "and" or "but." Without it, he says, the initials spell out something the auto-captions render as "yode mem" (00:02:09); given the standard reconstruction of the meme, he most likely said yod-he-mem-he, the initials of Yeshua ha-Notzri Melekh ha-Yehudim. Treat the exact letter sequence as unverified from this transcript. > He then adds a grammatical point that is independent of the acrostic: John's Greek puts "king of the Judeans" in apposition to "Jesus the Nazarene," that is, "Jesus of Nazareth, who is king of the Judeans" (00:02:55). The auto-captions render "apposition" as "opposition" throughout. Inserting "and" turns the title into two coordinated predicates, "Jesus the Nazarene and King of the Judeans," which he says matches no gospel (00:02:55). His conclusion: "Someone has just made that up" (00:02:55), by someone who knows "a tiny little bit about Hebrew," and it has been repeated by people who know none. > **A third small error in the clip.** The creator quotes the sign as "Jesus Christ of Nazareth." McClellan notes "Christ" appears in none of the gospel descriptions of the sign (00:03:37). This is checkable in one minute against Matthew 27:37, Mark 15:26, Luke 23:38 and John 19:19; none includes Christos in the titulus. > **The hedged point: Hebrew or Aramaic.** McClellan flags one "potential issue" and explicitly refuses to rule on it. John 19:20 says the sign was written in Hebraisti, and most translations across Christian history have rendered that as Aramaic; some current scholars argue it means Hebrew. "That's a debate that's ongoing... So I'm not taking sides on that debate" (00:01:26). If Aramaic, the reconstruction would look different and the acrostic argument changes shape again. The separation of his certain claims from his uncertain one is a feature of the video worth copying. > **The anachronism claim.** The clip asserts that "in the original Hebrew Bible, scholars would take the first letter from each word in Hebrew and combine them to make a hidden code" (00:05:03 into 00:05:46). McClellan's reply: "No, they wouldn't. That's something that took place sporadically in the centuries long after the Bible was written" (00:05:46). Nuance he doesn't add and this analysis should: alphabetic acrostics do exist in the Hebrew Bible (Psalm 119, Lamentations 1-4, Proverbs 31:10-31) I think you're going to like this.>> All right, let's see it.>> Because have you ever seen God pull theultimate uno reverse card? >> No, but I saw Tyson beat Spinx on TV.>> The sign above Jesus's head on the crossprobably would have looked somethinglike this. And it said Jesus Christ ofNazareth, King of the Jews. >> So, that's not what it would have lookedlike. There are two glaring problems andthen one potential issue. Probably themost significant glaring problem is theway the Greek is represented where eachword begins with a capital letter andthen has lowercase following it and hasrough and smooth breathing marks and hasaccents. That’s simply not how Greek waswritten for public-facing texts. That ishow Greek would have been used forcertain kinds of more sophisticatedliterary texts that were being copiedout. Certainly wouldn't have been usedfor a placard being created to placeover the head of an executed person. So,The most glaring problem is that whoevercreated this didn't bother to go look uphow they would have used Greek forpublic-facing signs. They just copiedand pasted off of some website that hadthe Greek of John 19 on it. They didn'teven bother to look anything up. Now,the potential issue is with the notionthat the sign had Hebrew on it because throughout the overwhelming majority ofChristianity,most translations of the Bible haverendered that Aramaic, not Hebrew. Now,there are scholars who argue today thatit was Hebrew, that was being referredto by the language of the Hebrews ratherthan Aramaic. That's a debate that'songoing. I think there are significantproponents of the view that it shouldrefer to Hebrew. So I'm not taking sideson that debate. Potentially it wouldhave been in Aramaic, and if it was, itwould have looked much different, butthis is Hebrew and not Aramaic. Theother glaring issue is precisely withThe Hebrew. And it's with the fact thatwhoever created this has added an entireword to the Hebrew that simply doesn'texist in any of the New Testament'sdescriptions of what was written on thissign. And they added that word entirelyarbitrarily just toengage in deception, just to lie to you. So that apologists on the internet couldsuggest that if you take the firstletter of each of the four words of theHebrew, it spells out the divine name,the tetragrammaton, yode, vave, adoni,and it simply does not. It spells outyode mem. Unless you just arbitrarilythrow in this extra word, a vav, whichis a conjunction and or but and it kindof messes up the opposition of thestatement because in Greek it says Jesusthe Nazarene, king of the Judans. That'sopposition. That is saying Jesus ofNazareth. That is to say, or who is kingof the Judeans. But when you add thevav, the extra conjunction that is notthere into the Hebrew, you get Jesus theNazaren and King of the Judans, which is simplynot how any part of the New Testamentdescribes what was written over Jesus'shead. Someone has just made that up. Someone who knows a tiny little bitabout Hebrew, but not enough to knowmuch better, and they just passed it onto other people who don't know the firstthing about Hebrew, and so just ape thisclaim all over the internet withoutknowing they're lying to people. Andthat's the problem with this contentcreator. They don't have the first cluewhat they're talking about. Anytime theytalk about what's in the Bible, theycouldn't even get it right. He saidJesus Christ. Christ Christ is not therein the specific description of what waswritten on the sign that is being repeated here. They couldn't even getthat right because they don't thinkcritically about this. They're notcareful about this. They're certainlynot insightful about this. They sawSomebody else claim this on the internet,and they decided they were going to burpit up for their audience as well, so theycould get the little digital pats on thebutt from all the likes, from all thecomments, from all the shares, and sothey could make money off of it. This ispure and simple a grift. And this person is not even good at it.The problem is that to grift Christians,you really don't have to be good at it.Because a lot of Christians today,particularly on social media, aredeeply, deeply, deeply gullible. Andthey don't bother to think criticallyabout any of this. And I'm going to geta lot of comments on my video gettingmad at me for exposing the fact thatthis person is lying to them. They'regoing to come to the defense of theperson who is lying to them for theirown benefit, and they're going to getupset or annoyed at the person who istrying to help them understand thetruth. Why? Because this is not aboutData. It's not about truth for them. It's about vibes. It's about ticklingthe little tuning fork in the loins oftheir dogmatism. And because theperformance of garbage apologetics doesthat for so many people out there,they're going to get upset at the personwho's saying the little tickling of thetuning fork in the loins of yourdogmatism is not true. It’s based on alie. They’re going to get upset with meabout that. >> But here’s the thing. This sign wasoriginally meant to mock Jesus. But letme get a little deeper. In the originalHebrew Bible, scholars would take thefirst letter from each word in Hebrewand combine them to make a hidden code.No, they wouldn’t. That’s something thattook place sporadicallyin the centuries long after the Biblewas written.>> So in Hebrew, that sign above Jesus'shead would have looked something likethis. See,>> I see someone who doesn't know how totransliterate Hebrew, lying to thepublic in order to make them feel likethere's a secret code in that statement. And there simply is not. They didn'teven translate it correctly after theymisinterpreted it. This is laughablegarbage apologetics.And unfortunately, people just eat it upbecause they just want to be made tofeel good about their dogmas. >> So then what happens if you take thefirst letter with each of these words?Does it reveal a hidden code? Oh yes, itdoes. But not a code, a name. Yahweh.Boom.This is completely hilarious to me. >> Here's where I would insert a joke aboutit being far more hilarious how blindly andbrainlessly this content creator isrepeating just outright falsehoods anddeception just to make other people feelgood about their dogmas. But I don'tfind it hilarious. I find it tragic. Ifind it deeply concerning that so manyPeople out there are being misledbecause there are so many other peopleout there who do not have the foggiestidea what they're talking about, who aremaking a living by deceiving people whowant to be deceived. >> Because what was first meant to mockJesus ended up praising him. Do you knowwhat's even funnier? Again, the jokeswrite themselves regarding how ignorantthis content creator is, but how muchmore ignorant they are, relying on theiraudience being so, that this garbageapologetic can land and can get them thedigital pats on the butt and the revenuethat they're after. >> Evil is the one who put Jesus on thatcross, and by doing so, was defeatedbecause of it. Remember,the claim in this video is not true. Itis a lie. Somebody made it up to deceiveothers so that they could benefit fromit. And this content creator didn't knowany better and was deceived by it, andthen turned around and spread it. Amplified that deception to an audiencethat just wants to be made to feelbetter about their dogmas and doesn'teven seem to care if it's true or not.That's a problem.And the fit for this video has been thelast Ronin., God’s Ultimate UNO Reverse Goes Wrong, Dan McClellan, 01m3f7ecyherrzvdzr79k7s8cv.