Author: Zebulan

  • Book Review: “The Seventy-Two Servants of the Word of God”

    Book Review: “The Seventy-Two Servants of the Word of God”

    Summary

    Mikkel “Michael Potamopotos” Søtbæk (a Danish Confessional Lutheran) provides an easily-digestible case for favoring the Septuagint (LXX) as the authoritative text type of the Old Testament. Despite some unfortunate formatting and typographical errors in this first printed edition of Mikkel’s monograph, the substance of his arguments are rock solid, and though one may be able to nitpick a few of his points, their cumulative force prove unassailable.

    This is not a comprehensive case for the Septuagint, but it is certainly a sufficient case, and it the strongest case yet compiled in written form. For those unfamiliar with the LXX, it serves as an excellent starting point; even for those with existing knowledge (such as myself), it is an excellent overview and summary to refer back to, covering much ground in little space. I highly recommend this book to everyone interested in studying Scripture.

    Background and presentation

    This book has been a long time coming, and I’ve been waiting for it since I was first recommended the recordings of a two-part discussion on The Other Paul’s YouTube channel, in which Mr. Søtbæk discussed some of the content of the book. These streams serve as a decent, albeit long and less organized preview of the book, if you’re curious:

    Since the release of these streams in 2022, it has taken an additional three-and-a-half years for the book to reach publication. In mid-2025, he gave a briefer, audio-only overview on The Gottesdienst Crowd podcast. But this December, the book was finally released, and I am pleased to report it was worth the wait.

    Printed in its first edition as a paperback, this book is rendered with a comfortable text size, reasonable margins (large enough to scribble some short notes), and a generally well-organized structure with chapters, sub-sections, a list of tables and figures, and plenty of footnotes throughout.

    Like the Septuagint, this book is a translation: Mr. Søtbæk had originally written his monograph as his master’s thesis and in his native language of Danish1, and he has now translated it both in language and in form into an English book. Unlike the Septuagint, however, this book is an imperfect translation.

    Though the English is overall well-written, there are nevertheless a few instances of awkward and confusing phrasing that seem to betray that certain statements were not originally composed in English. The text could do with some more em dashes, semicolons, and parentheses to more clearly delineate clauses. I spotted a few spelling typos, accidental grammatical inversions, and missing words throughout, which I expected.

    Less expected, however, were the formatting errors. Unfortunately, it seems the book has also suffered somewhat in its translation from digital thesis to monochrome paperback.

    Starting off with something harmless and subtle: the title page inside the book and every page heading gives the title as “Seventy-Two Servants of the Word”, whereas the external cover and the copyright page render the slightly more verbose “The Seventy-Two Servants of the Word of God”, which is an understandable change for marketing purposes. One might even suppose that the inclusion of the alternative title is intended.

    Less subtle and certainly not intended, however, are certain places where the text of the book references a figure “above”, which is actually on the next page, or mentions comparing something on the left to something on the right, when the actual order is reversed. Evidently certain illustrations were shuffled around during the editing process, and the text was not updated accordingly.

    The most egregious example is on pages 65–66, where the text directs the reader to notice certain phrases in a chart that are supposedly highlighted in yellow and turquoise. This useful and colorful formatting may be glimpsed in the digital form of the document referenced in one of the 2022 livestreams hosted by The Other Paul, but the book’s current format makes such highlighting impossible, and no substitute has been provided.

    These mistakes are distracting and far more common than I would like, but thankfully, they are all merely surface level. The actual meat of the content is unaffected, and though I have some minor complaints about that as well, they are (despite the length of words I am about to dedicate to them) mere nitpicks in comparison. Perhaps some small good will even come of these slight errors, in that they may serve as traps at which midwit critics of the book will attempt to tear down the impenetrable castle2 which Mr. Søtbæk has constructed, and thereby demonstrate their own folly. (But I’d rather that such people just not be stupid.)

    The content

    My favorite parts

    The section on Church father support for the Septuagint is more extensive than I had expected, and this is one of the most useful aspects of the book; for although comparisons of Old Testament quotations in the New are relatively easy to compile in this digital age, Church father quotations are much harder to find and sort through. Though I walked into this book already convinced that the Church fathers held the Septuagint as authoritative, the witness provided in this book was even stronger than I knew, for there are many references here I was not yet aware of.

    I was pleasantly surprised to discover that Part IV (especially, but also indeed the entire book) not only addresses but utterly annihilates one of the most annoying “arguments” (to give too much credit to its proponents) I’ve ever encountered against the Septuagint—namely the claim that there is no single translation to which the title “Septuagint” can be applied.

    Multiple volumes could be filled with books listing the differences between the Septuagint and Masoretic Text and the resulting implications that flow from each difference. I myself have spent a great deal of time investigating such differences of varying significance, and I am thus well aware of how bountiful the harvest is. It is therefore quite important for a summary work such as this to carefully pick which examples it spends its pages on. I am therefore pleased to report that this book has generally chosen a very strong set of examples, such that one could construct a strong case for the Septuagint on these alone, even without the rest of the arguments made within and without.

    To speak much more on what the book gets right might risk simply repeating what is already stated therein, so I shall now move onto my critiques of the content, which although long, may be addressed with very short alterations.

    My nitpicks

    Languages of the Babatha letters

    On page 17, it would’ve been nice if the languages of the remaining Babatha Letters were briefly mentioned. On first read, one might assume the remainder are written in Hebrew, but a quick search online suggests their language to instead be Nabatean-Aramaic and Jewish-Aramaic3. Briefly mentioning this would strengthen the argument being made.

    Ezra 4:18 and the translated letter to Artaxerxes

    In the section titled “From King Josiah to Ezra”, on page 18, a claim is made that a particular word (H6567) in Nehemiah 8:8 can and should be understood as meaning “translated” in the given context, by demonstrating that a closely-related word (H6568) is used in such a way in Ezra 4:18. I find this argument a bit weak—perhaps the weakest argument in the entire book.

    Now, certainly, both Masoretic Ezra and Greek Esdras B say the letter was translated in an earlier verse, though Esdras A entirely omits this detail:

    Masoretic Ezra 4:7 (ESV)In the days of Artaxerxes, Bishlam and Mithredath and Tabeel and the rest of their associates wrote to Artaxerxes king of Persia. The letter was written in Aramaic and translated.
    Esdras B 4:7 (NETS)And in the days of Arthasastha, they wrote in peace—Mithridates, Tabeel with also the rest of his fellow-slaves—to Arthasastha, king of the Persians; the tribute collector wrote in Syrian a document, also having been translated.
    Esdras A 2:15 (NETS)Now in the times under Artaxerxes, the king of the Persians, Beslemos and Mithridates and Tabellios and Raoumos and Beelteemos and Samsaios the scribe and the rest of those associated with them but living in Samaria and the other places wrote out the following letter to him against those who were living in Judea and Ierousalem,

    Note that the Masoretic Hebrew word rendered as “translated” here is H8638, from which we get the word “targum”. The Greek word here in Esdras B is ἡρμηνευμένην (G2059), from which we get “hermeneutics”. Both can quite clearly be understood as meaning “translated” here.

    I would interpret this passage as saying that two versions of the letter were prepared: one in Syrian (Aramaic), and another in (presumably) Persian.

    Note, however, that the word used in the Masoretic Text here is not the one found in Masoretic Ezra 4:18, and in fact the Greek versions of the latter passage make no mention whatsoever of the letter being translated in the king’s presence:

    Masoretic Ezra 4:18the letter that you sent to us has been translated/made-clear before me…
    Esdras B 4:18 (NETS)the tribute collector whom you sent to us was summoned before me…
    Esdras A 2:22 (NETS)I read the letter that you have sent to me…

    The level of divergence between Masoretic Ezra and Esdras A is somewhat expected, but the level of divergence between Masoretic Ezra and Esdras B is surprising, and (certainly if one takes a Septuagint primacy view) suggests that the Masoretic Text is corrupt and perhaps even incoherent here, which would hamper its utility in determining the meaning of H6567 & H6568.

    Furthermore, the preceding passage in 4:7 (of both Masoretic Ezra and Esdras B) already seems to imply that the letter was translated before being delivered to the king, which would make it odd for the king to then reply as if the letter had been translated after reception. Thus, a reading of “made clear” (with the resulting sense that the king was simply confirming that the already-translated version of the letter had been understood clearly by him) would seem to be a more coherent reading of the Masoretic Ezra.

    On the other hand, if the word used in the Masoretic Ezra 4:18 is indeed best understood as “translated”, then any resulting incoherence would favor the accuracy of the LXX in this passage against the Masoretic Text. But while that would serve the goals of the book, it is not the argument made on the page.

    Ultimately, I think the other evidence presented in the book for the increasing loss of Hebrew and adoption of Aramaic is sufficient for the overall points being conveyed, and that the appeal to Ezra 4:18 is perhaps a bit too shaky to be worth inclusion.

    Note on scholarly notation

    On page 28 I noticed “(Acts 10:24f)” and “(verse 44f)”, which confused me at first since the “f”s looked to me like either verse-subdivision indicators or indicators of additional verses not present in all manuscripts (and thus outside the common verse numbering scheme); but after looking it up, I now understand that this is merely a standard shorthand for saying “and the next verse”. I wonder if perhaps this use of scholarly notation (unexplained in the book itself) is unsuited to its intended audience. But it is a very minor thing.

    The name of the translator of the Wisdom of Jesus the son of Sirach

    I was initially rather confused by the wording on page 43, since it gave the name of the man who translated the Book of Sirach into Greek as “Jeshua ben Sirach” and “Joshua, the son of Sirach”. First of all, there’s a bit of inconsistency between the section heading and the text under it, but far more confusing is that this name is applied to the translator.

    Now, Jesus (Joshua) is the name of the guy who first wrote the book, and 50:27 says Jesus’ father was named Sirach, but the grandson translator never names himself.

    Another prologue (historically attributed to Athanasius but now deemed of later origin) gives the translator’s name as Jesus and his father’s name as Sirach, thus making the translator’s name identical to the original author, and producing a lineage that looks like Sirach → Jesus → Sirach → Jesus (unless 50:27 is instead viewed as the signature of the translator, which seems unlikely to me). Even if this prologue is correct, I think it would be much clearer if the book simply called the translator “the grandson of Jesus son of Sirach”.

    Philo and his audience’s native tongue

    In section “The Jewish Reception of the Septuagint”, on page 45, my initial read led me to think that the author was claiming that many Hebrews contemporaneous to Philo had Greek as their native tongue, on the basis of these words of his:

    but in our own [language] it means “turning oneself away from God”

    I had assumed that “our” referred to the Hebrews in general. However, upon closer inspection, a fuller version of the quote suggests something slightly different—namely that the Hebrews said “Phanuel” (notably the same transliteration of the name used in LXX Judges 8), whereas Philo and his audience natively spoke Greek.

    Ἔστι δὲ ὡς μὲν ᾿Εβραῖοι λέγουσι “Φανουὴλ”, ὡς δὲ ἡμεῖς, ἀποστροφὴ θεοῦ.

    “On the Confusion of Tongues” by Philo of Alexandria, chapter 26

    It is, as the Hebrews say, “Phanuel”, but as we [say], “turning away of God.”

    Literal English translation of Philo quote

    On second read, I now realize that this section of the book was simply making a point that Greek had made inroads into the elite levels of the Hebrew society. Still, I suspect my initial confusion could be repeated by others, so I think including the full quote might clarify the point being made.

    The opening of eyes in Isaiah

    In section “The Use of the Septuagint by Christ”, on pages 65–67, one of the most powerful arguments in favor of the Septuagint is put forth: Christ’s reading of the Book of Isaiah in the Nazareth synaogogue. To reiterate the comparison given between the Greek of Isaiah and the Greek of Luke (now in living color):

    πνεῦμα κυρίου ἐπ’ ἐμέ οὗ εἵνεκεν ἔχρισέν με εὐαγγελίσασθαι πτωχοῖς ἀπέσταλκέν με ἰάσασθαι τοὺς συντετριμμένους τῇ καρδίᾳ κηρύξαι αἰχμαλώτοις ἄφεσιν καὶ τυφλοῖς ἀνάβλεψιν καλέσαι ἐνιαυτὸν κυρίου δεκτὸν […]

    Isaiah 61:1–2 (Rahlfs’ LXX)

    […] ἀπόστελλε* τεθραυσμένους ἐν ἀφέσει […]

    *imperative form

    Isaiah 58:6 (Rahlfs’ LXX)

    πνεῦμα κυρίου ἐπ’ ἐμέ, οὗ εἵνεκεν ἔχρισέν με εὐαγγελίσασθαι πτωχοῖς ἀπέσταλκέν με [ἰάσασθαι τοὺς συντετριμμένους τὴν* καρδίαν*] κηρῦξαι αἰχμαλώτοις ἄφεσιν καὶ τυφλοῖς ἀνάβλεψιν ἀποστεῖλαι** τεθραυσμένους ἐν ἀφέσει κηρῦξαι ἐνιαυτὸν κυρίου δεκτόν

    *these two words are in accusative case (as opposed to the dative case used in Isaiah), but this has no effect on the meaning
    **infinitive form

    Luke 4:18–19 (Greek; bracketed section is absent in Alexandrian & Western Texts, but present in Byzantine Text and Irenaeus’ Against Heresies)

    And now in English, with the Masoretic Isaiah added to the comparison, and certain rendering choices adjusted (relative to Mr. Søtbæk’s book) to provide a more precise comparison…

    the Spirit of the Lord is upon me, because he has anointed me to bring good news to the poor, he has sent me to heal the brokenhearted, to proclaim to the captives liberty* and to the blind a recovery of sight**, to call the acceptable year of the Lord […]

    *can also mean “pardon/forgiveness
    **etymologically “a looking up

    Isaiah 61:1–2 (Rahlfs’ LXX → English)

    […] send out the oppressed in release […]

    Isaiah 58:6 (Rahlfs’ LXX → English)

    the Spirit of the Lord is upon me, because he has anointed me to bring good news to the poor, he has sent me [to heal the brokenhearted,] to proclaim to the captives liberty* and to the blind a recovery of sight**, to send out the oppressed in release, to proclaim the acceptable year of the Lord

    *can also mean “pardon/forgiveness
    **etymologically “a looking up

    Luke 4:18–19 (English; bracketed section is absent in Alexandrian & Western Texts, but present in Byzantine Text and Irenaeus’ Against Heresies)

    the Spirit of the Lord LORD is upon me, because the LORD has anointed me to bring good news to the poor, he has sent me to bind* the brokenhearted, to proclaim to the captives liberty and to the imprisoned an opening, to proclaim** the acceptable year of the Lord […]

    *i.e. “bandage”
    **can also mean “to call

    Isaiah 61:1–2 (Masoretic Text → English)

    […] send out the oppressed free […]

    Isaiah 58:6 (Masoretic Text → English)

    This is an exceptionally powerful argument, but there is one unspoken detail that, although not ultimately harmful to the argument, I nevertheless wish had at least been mentioned for the sake of preempting and shutting up the ignorant who might otherwise claim it as a “gotcha”: there is technically another passage in Isaiah which speaks of God’s Servant giving sight to the blind, which also bears some resemblance to the passage in Luke.

    ἀνοῖξαι ὀφθαλμοὺς τυφλῶν ἐξαγαγεῖν ἐκ δεσμῶν δεδεμένους καὶ ἐξ οἴκου φυλακῆς καθημένους ἐν σκότει

    Isaiah 42:7 (Rahlfs’ LXX)

    To open eyes of the blind, to lead out of bonds the bound, and out of the house of prison those sitting in darkness.

    Isaiah 42:7 (Rahlfs’ LXX → English)

    To open blind eyes, to bring out of dungeon the bound, from the house of prison those sitting in darkness.

    Isaiah 42:7 (Masoretic Text → English)

    Some might contend that Christ is referencing Isaiah 42:7 and synthesizing it with Isaiah 61:1–2, in a similar way to how Isaiah 58:6 has been incorporated, and that therefore, it cannot be certainly claimed that Christ is referencing anything specific to the Septuagint. This objection, however, does not hold up well under scrutiny.

    Although there is obviously an overlap in meaning (contextually, the passage speaks of God’s Servant making blind men see and leading men out of prison), the actual words are quite different. For example, the Greek term used in LXX Isaiah 61:1 and Luke 4:18 rendered as “recovery of sight” is ἀνάβλεψιν; etymologically, this term could woodenly be rendered as “a looking up“. This is different from the phrasing of “to open eyes” (ἀνοῖξαι ὀφθαλμοὺς) that is used in Isaiah 42:7 as well as in the New Testament (e.g. John 10:21 & Acts 26:18).

    Now, the “looking up” terminology does appear in LXX Isaiah 42:18, but the context and tone are rather different (God is chastising the Israelites for their idolatry, calling them spiritually blind and deaf), and the form of the words are still not as close to Luke 4:18 as LXX Isaiah 61:1 is. Somewhat ironically, the Masoretic Hebrew of this verse is less similar than the Greek, since only the Greek specifically conveys the sense of looking up.

    οἱ κωφοί ἀκούσατε καὶ οἱ τυφλοί ἀναβλέψατε ἰδεῖν

    Isaiah 42:18 (Rahlfs’ LXX)

    O deaf, hear, and O blind, recover sight* to perceive!

    *etymologically “look up

    Isaiah 42:18 (Rahlfs’ LXX → English)

    O deaf, hear, and O blind, look to see!

    Isaiah 42:18 (Masoretic Text → English)

    Had Christ intended to specifically reference Isaiah 42:7 (the most similar passage in terms of meaning that appears in the Masoretic Text), He could have used the same terminology of opening eyes (ἀνοῖξαι ὀφθαλμοὺς) that already occurs both in the Greek of Isaiah 42:7 as well as in the New Testament (e.g. John 10:21 & Acts 26:18). That the exact words of LXX Isaiah 61:1 are used instead is clearly an endorsement of its particular reading over that of the Masoretic Text.

    Furthermore, I must reiterate that Luke describes Christ as reading from a written copy of the Book of Isaiah, so such a loose paraphrase would be quite inappropriate (and entirely unnecessary, since Isaiah has no shortage of relevant passages that could’ve been quoted here). I’d further posit that the slight deviations from our now-common LXX that occur in Christ’s reading may have been actual variants in the manuscript Christ was reading from, and that He (knowing they made no real difference to the meaning of the prophecy) simply read the text exactly as written.

    Finally, to “answer a fool according to his folly” (Proverbs 26:5): consider that Luke specifically says “the scroll of the prophet Isaiah was given to him. He unrolled the scroll and found the place [singular] where it was written”. The words of Isaiah 58:6 and Isaiah 61:1–2 are not incredibly distant from each other, but Isaiah 42:7 is quite far indeed from both. Are we to assume that “place” in the scroll covered the entirety of 42:7 to 61:2?

    The simple, reasonable conclusion is that Christ was indeed reading and quoting from the Septuagint.

    (Blind ones seeing is also mentioned in Isaiah 29:18, Isaiah 35:5, and Isaiah 42:16, but those are all even more dissimilar to the passage in Luke, and most of the previously-given points still apply.)

    Thoughts on Theodotion

    Throughout the book, the name “Theodotian” is used, but the standard form derived from the Greek and appearing in most places online is “Theodotion”. I don’t know why a non-standard spelling is being used here. Is this how they spell it in Denmark?

    Relatedly, I think it might’ve been worth mentioning in the “Theodotian and Daniel” section (pages 147–149) that Irenaeus, who in Against Heresies Book III Chapter XXI attacks Theodotion and the other Jewish translators, also seemingly quotes the so-called Theodotion Daniel thrice in Book IV Chapter XXVI of the same work.4 This seems to be much stronger evidence for the “Theodotion” text predating Theodotion than the supposed (and very tenuous) New Testament references to it that were given. Perhaps Mikkel was not aware of this detail?

    Digression on the origin of the two Greek versions of Daniel

    I have a hypothesis that the version of Daniel attributed to Theodotion may not only predate Theodotion, but might even be the official LXX version, while the “Old Greek” version is descended from the partial, unofficial translations Aristobulos was aware of (as mentioned on page 43), perhaps being later expanded to include sections first translated by the LXX project (possibly explaining why some sections of the two versions resemble each other more than others).

    Speculating a bit further, I’d posit that Origen was unaware that such a pre-LXX text was circulating, and that he may thus have mistakenly assumed that the version more closely resembling the proto-Masoretic Text was the work of Theodotion, while the other was the Septuagint. It could also be the case that Theodotion never produced a revision of Daniel at all and simply “reposted” a preexisting version that was later attributed to him as a result; or perhaps he did produce a revision based on this preexisting version, but his changes were so minor that the two were easily confused for each other.

    Notably, the so-called Theodotion version, although generally closer to the Masoretic Text than the so-called Old Greek, nevertheless sometimes diverges from the Masoretic—even in a few places where the Old Greek does not:

    chapter/verse“Old Greek”Masoretic“Theodotion”
    9:24decreeddecreedcut short
    9:24to anointto anointto gladden
    9:25build Jerusalem a city for the Lordbuild Jerusalem until an anointed leaderbuild Jerusalem until an anointed leader
    9:26shall be torn away and will not beshall be cut off and have noughtshall be destroyed, and there is no judgement in him/it

    Although it is not entirely clear on this point, the wording of Origen’s Letter to Africanus seems to suggest that the so-called Theodotion version was already circulating within the churches:

    For in Daniel itself I found the word “bound” followed in our versions by very many verses which are not in the Hebrew at all, beginning (according to one of the copies which circulate in the Churches) thus:  “Ananias, and Azarias, and Misael prayed and sang unto God,” down to “O, all ye that worship the Lord, bless ye the God of gods. Praise Him, and say that His mercy endureth for ever and ever. And it came to pass, when the king heard them singing, and saw them that they were alive.” Or, as in another copy, from “And they walked in the midst of the fire, praising God and blessing the Lord,” down to “O, all ye that worship the Lord, bless ye the God of gods. Praise Him, and say that His mercy endureth to all generations.” […] Of the copies in my possession whose readings I gave, one follows the Seventy, and the other Theodotion […]

    Origen’s Letter to Africanus (c. 203-240 AD)

    It would be quite surprising for a Theodotion-produced version to be circulating in the churches at this time (and to then become so popular that the supposed Septuagint version nearly vanished), considering the contemporary attitudes toward the Septuagint; but it would be much less surprising if the version in fact predated Theodotion and perhaps even is the true Septuagint version.

    There may be something I’m missing. Still, as the book says, this is a “fruitful field for further research”, and the matter awaits an answer from the mouths of faithful men.

    Where is the Peshitta?

    Something left entirely unmentioned in the book (and never even alluded to except indirectly through a brief mention of “Syriac-speaking Christians” on page 109) is the Peshitta: a translation of the Bible commonly believed to have had its Old Testament completed during or before the 2nd century AD, which bears much resemblance to a proto-Masoretic Text5.

    This version would seem to be the sole exception to the Septuagint rule over the realm of early translations that circulated in the Church. Apparently it was held in high regard in the Syriac Christian tradition, and it is still used to this day in the Syriac churches—somewhat similar to how the Septuagint is still used by the Greek-speaking churches.

    A cursory search online brought up “The Syriac Versions of the Old Testament” by Bas ter Haar Romeny, and a quick read through that led me to this relevant paragraph:

    The earliest reference to the origins of the Peshitta is found in Theodore of Mopsuestia’s commentary on the Twelve Prophets. This Greek-speaking exegete (d. 428) says that the Syriac Bible was composed by some unknown man who often made mistakes, and even made up stories. Therefore, he argues, this Syriac Bible could by no means compete with the Septuagint6. Theodore was reacting against Eusebius of Emesa (see § 3 above), an earlier representative of the Antiochene School of exegesis, to which Theodore also belonged. Eusebius had defended the importance of the Hebrew text as the original version of the Old Testament, and had used informants and the Peshitta to get access to it. Eusebius knew that Syriac (his mother tongue) and Hebrew were ‘neighbours’. For this reason, he had accorded the Peshitta a special status. For Theodore, however, the most reliable way to access the Hebrew was via the Septuagint. He endorsed the view that the Septuagint was a translation made by seventy very learned persons who had independently come to the same renderings, and that it was, furthermore, adopted by the Apostles, who handed it down to the Gentiles. Theodore was anxious not to add anything to the biblical text. He was afraid of speculation. The fact that it was unknown to him who had translated the Peshitta, made him shun the latter version.

    “The Syriac Versions of the Old Testament” by Bas ter Haar Romeny (2005)

    The article then proceeds to discuss various later accounts and modern hypotheses attempting to explain the origin of the Peshitta, leaning towards a Hebrew origin, though whether these hypothetical Hebrews were Jews or Christians is unclear. It also discusses three (ultimately failed) attempts to replace the Peshitta with a version more closely aligned with the Septuagint: the Syro-Lucianic/Philoxenian version, the Syro-Hexapla, and Jacob of Edessa’s version.

    It is certain that although the Syriac world held it in high regard, such a view was never held in the West; in fact, the Peshitta was essentially irrelevant to the Western Church (which I gladly admit to holding in higher regard than the East). No truly ancient legend has been passed down to ground its origin. No ancient translations ever used the Peshitta as an authoritative basis. And obviously the difference in language precludes any possibility of drawing close connections between it and the authoritative Greek of the New Testament.

    As such, I do not think the Peshitta (and its omission from the book) does any real harm to the case for the Septuagint, but I do wish it had at least been briefly addressed, lest any should assume it was omitted out of dishonesty.

    A Deuteronomy 32:43 variant

    On page 172, Deuteronomy 32:43 is used as an example of a Christological prophecy preserved in the Septuagint. The LXX text used on the page appears to be Rahlfs’ critical text, which matches Codices Vaticanus and Alexandrinus. (The Sinaiticus page for this passage has been lost.) Notably, the Aldine Text, Complutensian Text, and even the Sixtine Text7 of Deuteronomy 32:43 have “angels” and “sons” swapped compared to Rahlfs’ critical text, such that the version in these printed editions aligns even more closely with Hebrews 1:6. I think this might be worth mentioning in a footnote, although the combined witness of Vaticanus and Alexandrinus in favor of the critical reading is strong.

    The misleading use of “Gentiles”

    This is perhaps the most nitpicky of nitpicks, but I’m bugged by the use of the (originally Latin) term “Gentile” throughout the book. Its usage in quotations of (and references to) Scripture is misleading, since its modern meaning of “non-Jews” is too far removed from the intent of the original Greek ἔθνος (ethnos), which simply means “nations”/”races”.

    The Greek word only ever means “other nations/races besides the Jews” by contextual implication—the same way that one uses the term “the world” in a phrase like “me against the world”; indeed, Scripture itself sometimes speaks of “the world” (Greek κόσμος; “cosmos”) in this otherly way, e.g. John 14:17. In contrast, just as the default meaning of world/cosmos should be the general sense (e.g. “God created the world” obviously means God created the entire world, and not just the parts of the world that oppose Him), the vast majority of passages and prophecies speaking of ἔθνος should be seen as speaking of all nations generally, rather than speaking of non-Jews specifically.

    This situation is made even worse by some translations also sometimes rendering even the word for “Greek” itself (Ἕλλην) as “Gentile”, thus confounding the aforementioned cases with cases where a specific group actually is intended to be referenced. See, for example, the ESV mistranslation of Mark 7:26 and NIV mistranslation of Galatians 3:28.

    The continued use of the word “Gentile”, both here and in various English translations, thus functions as a form of judaizing due to its modern sense. Many errors can (and do) flow from such a misunderstanding, such as the heresy of Dispensationalism. Since English already has words to more clearly translate the Greek here, I would greatly prefer that those words be used instead. The Word ought to be conveyed clearly, and “Gentile” is at best an insufficient translation of the Greek, and at worst an incorrect translation.

    Editorial issues and suggested fixes

    For the purpose of improving a future second edition, I shall now list every editorial mistake or awkwardness that I noticed, along with a suggested fix for each.

    pageissuesuggested fix
    15“But it must also be added that spoken Hebrew never disappeared completely, but it was kept in use”

    The repeated use of “but” reads awkwardly.
    “However, it must also […] completely: rather, it was kept in use”
    17“26 out of 36”

    This page (and the article8 referenced in its footnotes) claims the existence of 36 Babatha Letters, but other sources9 only mention 35. I assume 36 is a typo which has been inherited by the book.
    “26 out of 35”
    19“from the comparison between the two inscriptions above”

    The referenced figure is actually on page 20, and calling both the original inscription and the modernized transcription “inscriptions” seems a bit confusing.
    Move the illustrations to before the relevant text, and/or revise the text to “from the comparison between the inscription and the transcription in Figure 1”
    19“the original Paleo-Hebrew inscription is on the left while the text on the right is the now common Aramaic script”

    This is reversed from what is actually displayed in Figure 1 on page 20.
    Reverse the order of illustrations or revise the text to match the actual order.
    19“(Talmud Bavli, Sanhedrin 21b-22a)” has an extraneous underline below the comma.Remove the underline.
    20the printed illustration has suffered a loss in detail on its lower fifth, compared to the equivalent that can be seen here. Note also that the original illustration has the Aramaic script on the right, matching the text on page 19.Adjust the illustration to be be better rendered in the monochrome format of the book.
    21“where these new letters are seen”

    This has a typo; the letters being referenced are the old ones.
    “where these old letters are seen”
    25“Phila-delphia” and “Scytho-polis” have seemingly unnecessary hyphens—perhaps an artifact of the page’s layout and text flow being altered at some point.Remove the extraneous hyphens.
    26“to-gether” and “Deca-polis” are two more examples of unnecessarily hyphenated words.Remove the extraneous hyphens.
    26“a large, open city squares”“a large, open city square”
    26“looking at the map above”

    The map is on page 25, so this is slightly awkward.
    “looking at the map in Figure 3”
    37“Apart from the tribes of Benjamin and Judah surviving in Judah itself, the tribe of Levi, Luke 1:5, and northern tribe of Asher is also mentioned as having survived in the southern Judah, Luke 22:30.”

    The punctuation is confusing here.
    “[…] itself, the tribe of Levi (Luke 1:5) and the northern tribe of Asher (Luke 22:30)” are also mentioned as having survived in southern Judah.”
    46“Esther and 1 Esdras, in the Masoretic Text known as Ezra and Nehemiah”

    This is confusingly worded for two reasons. Firstly, the unfamiliar reader may think that what is being said is that the Greek Esther corresponds to the Masoretic Ezra; secondly, the name “1 Esdras” is somewhat ambiguous, as although some use it to refer to “Esdras A”/”Greek Ezra” (the book containing the story of the “Darius contest”), others simply use it to refer to the Ezra portion of Esdras B (as is the case in the Anglican 39 Articles of Religion). Generally, I’d recommend using the A/B naming scheme as it avoid ambiguity and corresponds more directly to the titles used in old Greek manuscripts.

    Additionally, it is unclear whether 1 Esdras (Esdras A) is even the book intended to be referenced here versus 2 Esdras (Esdras B) which corresponds more closely to the Masoretic Ezra–Nehemiah.
    Depending on intention:

    “Esther and Esdras A (the latter of which resembles and yet differs greatly from the books called Ezra and Nehemiah in the Masoretic Text)”

    …or…

    “Esther and Esdras B (the latter of which corresponds to the books called Ezra and Nehemiah in the Masoretic Text)”
    55“Ezra and Nehemiah (In the Septuagint, 2 Esdras)”

    “In” probably shouldn’t be capitalized. Also, I again find the use of “2 Esdras” a bit confusing due to its ambiguity: the name can refer to Esdras B, or to Nehemiah alone, or even to the obscure apocryphal Latin Esdras.
    “Ezra and Nehemiah (which form a single book in the Septuagint known as Esdras B)”
    65–66“shown in turquoise beneath”

    In actuality, Table 2 on page 66 has no coloring whatsoever, nor any alternative form of highlighting (e.g. underlining)
    Place a solid underline below the relevant words in Table 2 and revise the text on page 65:

    “marked in Table 2 with a solid underline”
    65–66“The passage in brackets in yellow”

    Again, there is no coloring in Table 2.
    Place a dotted underline below the relevant words in Table 2 and revise the text on page 65:

    “The passage marked in Table 2 with a dotted underline”
    66In the English translations of both Greek passages: “to preach the gospel”

    This is a correct translation, but a more etymological translation would make for a clearer and fairer comparison to how the Masoretic Text has been translated in the same table.
    “to bring good tidings”

    And add a footnote pointing out that this is the Greek word for evangelizing.
    66In the “English From LXX” row of Table 2: “[to set at liberty those who are oppressed]”

    This is ever so slightly inaccurate; the form of the Greek verb used in Isaiah 58:6 is imperative, which I think would be better rendered without the “to”.
    “[set at liberty those who are oppressed]”
    66In the “English From MT” row of Table 2: “The Spirit of the Lord is upon me, for”

    The Masoretic Text renders “the lord Lord” (“adonai” followed by “yhwh”) here, but this is lacking in the comparison, ironically making the text appear slightly closer to the quote in Luke than it actually is. Also, for consistency, “for” ought to be replaced with the equivalent “because” to match the other translations in the table.
    “The Spirit of the lord Lord is upon me, because”
    66In the “English From MT” row of Table 2: “to proclaim liberty to prisoners”

    The word used here can just as easily be rendered “captives” (as the Greek is rendered), so for consistency I think it
    should be rendered to match.
    “to proclaim liberty to captives”
    66In the “English From MT” row of Table 2: “to proclaim the acceptable”

    A footnote should probably be adding to point out that the Hebrew word rendered “proclaim” could also be rendered “call”.
    “to proclaim* the acceptable”

    And add footnote saying “*Can also mean “call”.
    67“he counted 37 such quotations, he found that 33 were”“he counted 37 such quotations and found that 33 were”
    70“it is not only with the Book of Isaiah that Jesus uses the Septuagint, he also uses it at places where its wording differs from the Masoretic Text”

    This is missing an “other” before “places”, and the punctuation could be improved.
    “[…] that Jesus uses the Septuagint: he also uses it at other places […]”
    72“prima farcie”“prima facie”
    74In English Matthew 1:23 translation: “will receive in her womb*”

    I think the asterisk is somewhat misplaced here, given the comment attached to the asterisk.
    “will receive* in her womb”
    74In English LXX Isaiah 7:14 translation: “will receive* in her womb*”

    I see no purpose to the 2nd asterisk here.
    “will receive* in her womb”
    74In the English LXX Isaiah 7:14 translation: “call his name called Emmanuel”“call his name Emmanuel”
    75“Here, a difference is seen between the wording of the New Testament and of the Septuagint […]”

    This entire paragraph appears to have been misplaced, as it speaks of Table 5 on page 74 (which has more than enough room to place the paragraph), yet it has been placed below Figure 5 on page 75, which only becomes relevant to the next paragraph (presently located on page 76).
    Transpose the paragraph to page 74.
    75In Figure 5, “Romans” is misspelled as “Romas” twice. The chart on the left is cut off after 1 Peter. There is also no explanation given for what the “P&O” abbreviation means; one must reference the PDF version of R. Grant Jones’ “Notes on the Septuagnt” to see it explained.Add explanation for “P&O” header below charts, and fix the spelling and visual cut-off.
    76“The book of Roman’s”“The Book of Romans”
    76“the transmission of the Septuagint in the centuries following A.D. 1 underwent revisions—though the textual instability of the Septuagint has been vastly overstated by many including Theodotian, Kaige, and the Lucian recension, among others”“[…] underwent revisions—though the textual instability of the Septuagint has been vastly overstated by many—including Theodotion, […]”
    87In Table 7 (the Genesis 1:1 table), the English translations of the LXX and Masoretic Text are swapped.Move the translations to the correct rows.
    87“lex orandi lex, which is what is or ought to be prayed and ought to be believed, or less literally, the rule of prayer is the rule of faith”

    This portion appears to have been quite mangled; this also makes me wonder whether the section title “Lex Credendi Lex Orandi” is intentionally reversed from the standard form.
    “lex orandi lex credendi, which means ‘the rule of prayer is the rule of faith’, or less literally: what is or ought to be prayed ought to also be believed”
    88“Juxta Hebreos,” (typo, and it also has an extraneous underline below the comma)“Juxta Hebraeos,”
    97“things [Rom. 8:32].”“things [Rom. 8:32]?”
    97The Proverbs 22:28 reference at the end of the Origen quote is missing a citation. (All the other citations in the quote are marked.)“‘Thou shalt not remove the ancient landmarks which thy fathers have set [Prov. 22:28].’”
    97“This motif also seen […] is also plainly asserted” reads awkwardly.“Thus, the motif of the Jews altering Scripture, seen with Justin Martyr and Irenaeus, is also plainly asserted”
    99“How long it survived is unknown, Jerome himself saw the work […] in the end of the fourth century, but it most likely” could do with clearer punctuation than commas.Use em dashes or parentheses instead.
    100“all nations under sun”“all nations under the sun”
    101“De mensuris et ponderibus,” has an extraneous underline below its comma.Remove the underline.
    104“where he had also acquired his skills in Hebrew that ‘under the inspiration of Barabbas.’” could be more clearly worded.“where he had also acquired his skills in Hebrew—and thus ‘under the inspiration of Barabbas.’”
    104“found the Septuagint wanting? As Jerome had accused it of being.” could be more clearly worded.“found the Septuagint wanting (as Jerome had accused it of being)?”
    109“He believes”“He believed”
    115“The debate did not end there and continued, however the chance”“[…] and continued; however, the chance”
    116“Lex credenda lex orandi”“lex orandi lex credendi”
    119“the vague Hebrew consonantal text”“the vague Hebrew consonantal text.”
    126“of the Aristeas’ letter.”“of Aristeas’ letter.”
    127“A decade after Cardinal Fisher’s death, he was executed by the English crown for his refusal to recant his loyalty to the Pope. the Roman Catholic Church summoned”“A decade after Cardinal Fisher’s death (he was executed by the English crown for his refusal to recant his loyalty to the Pope), the Roman Catholic Church summoned”
    134“deconstructive criticism would not effect”“deconstructive criticism would not affect”
    138“his own translation of the Latin, the Gallican Psalter,”“his own translation into Latin (the Gallican Psalter)”
    139“first by letting it direct his translation when he thought the Greek did not capture what he understood by the Hebrew, and later by adding in what was found under these text-critical signs”

    The chronology appears to be reversed from what was intended to be said.
    “first by adding in what was found under these text-critical signs, and later by letting it direct his translation when he thought the Greek did not capture what he understood by the Hebrew”
    139“Thus, Origin’s”“Thus, Origen’s”
    140“Though at this point […] Hebrew was a language understood only by a tiny minority”“At this point […] Hebrew was a language understood only by a tiny minority”
    142“scribes that did failed”“scribes that failed”
    142“the term Hexaplaric readings is still used”“the term ‘Hexaplaric readings’ is still used”
    145“Grammatical alterations have zero impact on the meaning of the text.”

    It seems to me that this was intended to be worded less generally.
    “These grammatical alterations […]”
    159“the dominant socio-dialect used by the New Testament’s authors as well as the Septuagint, the amount of literature truly is an embarrassment of riches.”“the dominant socio-dialect used by […], for which the amount of literature truly is […]”
    161(in the Masoretic translation) “give Thummin”“give Thummim”
    161(in the LXX translation) “give Thummim”“give manifestations” (The LXX does not use a transliteration of the Hebrew term.)
    161“The mistaken was”“The mistake was”
    167“Messiah, which in the Greek Septuagint simply was Christ, the Greek term for Messiah.”

    This would be clearer if it actually explained the underlying meaning of both words.
    “Messiah, which in the Greek Septuagint simply was Christ, a Greek word having the same meaning of ‘anointed one’.”
    167“According the fathers”“According to the fathers”
    172Twice, the Dead Sea Scroll fragment “4QDeutq” is mentioned; this is not exactly the name of the fragment.Use the actual fragment name: “4QDeut44q
    172In Table 9, the English translation of the Masoretic Deuteronomy 32:43 includes “For he will revenge his servants’ blood”, but this seems to be an error, since the corresponding text in the other two sources are omitted.Remove “For he will revenge his servants’ blood” from the chart since it is irrelevant.
    175“this ‘root of Jesse’ who will rise up and rule the nations applies to Christ, and that the nations”“applying to Christ this prophecy of the ‘root of Jesse’ who will rise up and rule the nations; that the nations”
    176“to catch the pray”“to catch the prey”
    179“handed on to current generation”“handed on to the current generation”
    182“fully extend copies of the Septuagint”“fully extant copies […]”
    182“fully extend copy of the Masoretic Text”“fully extant copy […]”

    Conclusion

    Aforementioned issues aside, this book is an excellent introduction to the Septuagint for newcomers and an indispensable handbook for Septuagint apologists. The book is well worth its price, and I would gladly purchase a second edition that addresses its minor deficiencies. And even as-is, I would highly recommend this book to everyone who even slightly cares about the textual traditions of Scripture.

    The book is available to purchase now in paperback form on Amazon (this is an affiliate link that gives me a commission), with a Kindle version forthcoming.

    Footnotes

    1. “The Protestant Case for the Septuagint – Another interview with Michael Potamopotos” by The Other Paul ↩︎
    2. A house built on the Rock, some might say. ↩︎
    3. “The Complete Babatha: More Questions than Answers” by Naphtali Lewis
      “Babatha: The Ancient Jewish Woman About Whom We Know Most” by Philip F. Esler ↩︎
    4. I am aware that this section of “Against Heresies” survives only in its Latin translation, which raises the question of whether the translator supplied quotes from the “Theodotion” version where Irenaeus may have originally quoted the “Old Greek”. However, the way in which Irenaeus uses Daniel 12:4 appears to align better with the Theodotion version. Also, the Latin translation is said (by W. Wigan Harvey, apparently) to be quite woodenly literal. Furthermore, it was probably published quite a while before Jerome came on the scene, since Tertullian is thought to have quoted it; so even if it was substituting “Theodotion” quotes, it would still at least be evidence of the “Theodotion” version already being common in Latin (and favored by some) at an early point. ↩︎
    5. Although according to Romeny, the current commonly available translations of it are based on manuscripts that have been further “revised” in the direction of the Masoretic Text compared to the more reliable manuscripts. ↩︎
    6. Theodori Mopsuesteni Commentarius in Xll prophetas, ed. H.N. Sprenger (GOF V.l; Wiesbaden, 1977), pp. 283-84, ad Zeph. I :4-6. [This footnote has been copied from the quoted article.] ↩︎
    7. This is why the Thomson and Brenton translations of this verse match Hebrews 1:6 so closely, while the LES2 (which is more directly based on Codex Vaticanus) matches the critical text here. ↩︎
    8. “Multilingualism and rebellion in 2nd-Century Judaea” by Letizia Rivera ↩︎
    9. Papyri.info HGV SERIES: P.Yadin
      “The Complete Babatha: More Questions than Answers” by Naphtali Lewis
      “Babatha: The Ancient Jewish Woman About Whom We Know Most” by Philip F. Esler ↩︎
  • Word History

    For the Seventy-Two Servants.

    The Word of God did clearly speak.
    The Word was once to Hebrew given.
    The Word went into Egypt's land.
    The Word returned by God's own hand.
    And when far from the Hebrew driven,
    the Word was received by the Greek.
  • Questions for Future Me

    I thought it would be somewhat interesting and maybe fun to write a series of questions for myself to answer in 10 years. (Yeah, over half of them are Minecraft questions. Silly, I know.) I’ll come back to answer the questions in this article on March 22, 2031.

    Minecraft

    Vanilla

    Has MC-4 been fixed yet? How about MC-100000?

    Surely, Java Edition data packs have the ability to add custom blocks and items now, right?

    Vanilla better have lavalogging by now, and Java Edition in particular must have had snowlogging ported over from Bedrock, right? Java Edition also has waterlogging for flowing water now, right?

    Mojang has continued to say no to vertical slabs, right? But what about windowlogging?

    Does vanilla have buildable vehicles similar to Plato’s Transporters? What about rotating/spinning platforms like Create?

    Glow squids give off actual light now, right? And surely iceologers have been added by now.

    Are polar bears useful yet? Are pigs still redundant?

    The second combat update was generally well-received, right?

    Ray-tracing came to Java Edition, right? Is it the modern equivalent of “fancy” or “fabulous” graphics?

    Quasi-connectivity was eventually removed, wasn’t it? How did Mojang soften the blow? Pushable block entities?

    What did the fletching table’s functionality end up being?

    Netherite and the smithing table was the start of a new branching upgrade tree for end game armor, right? I’m guessing one of the netherite alternatives involves materials from The End?

    I’m guessing that The End has green-colored biomes now?

    There’s a firework workstation now, right?

    Mods

    Did you start using behavioral mods on your singleplayer world? If so, how did that turn out?

    I think Fabric might get really big after the release of 1.17. Did it ever come to equal Forge in popularity? Does Forge even still exist?

    Did Modrinth overtake CurseForge as the primary mod repository?

    Has OptiFine died yet? If it did, was it the CaffeineMC mods (Sodium, Lithium, Phosphor, etc.) that replaced it, or something else?

    Does Quark still exist? What about the Team Abnormals mods? I don’t like their “visible source” licenses. Did that ever change? Have true open source mods taken their place?

    What’s the current successor to the Too Many Items legacy called? At the moment it seems like Roughly Enough Items could be the next primary one if Fabric takes off.

    Youtubers

    Is your singleplayer series still going? If so, why?

    Did Dream ever admit to cheating in those 1.16 speedruns?

    Is Etho’s singleplayer series still going? Whatever happened to that museum/lab project?

    Is Stampy still making the occasional Lovely World video?

    Other

    MinecraftOnline still exists right? You did finish the landscaping around the house, right? The lag is fixed now, right? Did they stack the old nether above/below the new one when updating to 1.16+? What did they do for 1.17+?

    What about Crazy Fools UK? 2b2t? Hypixel?

    How big was Hytale?

    Does Minetest feel like a legitimate game instead of a bootleg now? Did you ever contribute to Minetest, or did you end up creating your own MC clone?

    WordPress

    Gutenberg Full Site Editing became popular, right?

    Does Gutenberg still use a sidebar for the block inspector and/or document settings, or did it switch to popovers/modals?

    Is Divi still around? Did it ever switch to using blocks? How about Oxygen, Elementor, and Beaver Builder?

    Coding

    Did Crank take off?

    How big is Rust these days?

    Does PHP have generic types yet?

    Does vanilla JS have any form of typing similar to TypeScript yet?

    Did the year of the Linux desktop finally happen?

    How many people still use Arch, btw?

    Has Audacity become better to use, or has something replaced Audacity?

    LEGO

    How left-wing did LEGO go? Did they start introducing LGBTXYZ characters into their themes/shows?

    Did Bionicle ever come back again?

    Does TTV still exist?

    Is Ninjago still going? Was Seabound good? Are they still doing those 2D animated episodes, and did they ever stop looking kinda janky? Did Way of the Departed ever become canon or at least referenced in-show?

    Did Monkie Kid get better with each season? Did it ever reach Ninjago-level quality?

    Music

    Are The Beach Boys still your favorite band?

    What’s your opinion on SMiLE these days?

    Did the Bicycle Rider chorus ever get a better official stereo mix? What about Child Is Father of the Man?

    Did your interest in writing music ever go anywhere?

    Did you learn to play the piano?

    Miscellaneous

    I bet Trump’s social network never took off. Did I guess correctly?

    How big is Gab these days?

    Did Texas secede? I have no clue whether that will happen.

    Louis finally released that AGI demo, didn’t he?

    How did “the project” go? You’ll know what I’m talking about.

    Do you have a VR kit yet? Does it have foot-tracking so you can actually kick the rats? Do you even remember what I’m referencing? (It was on the 21st, by the way.)

    Are you married yet?

    Do you think writing this article was a good idea in hindsight?

  • LMB Tales: Rise of the Ask Topics

    LMB Tales: Rise of the Ask Topics

    Introduction

    If you were a member of the (now-closed) official LEGO Message Boards (LMBs), you may recall there being a lot of “Ask (insert character name here)” topics, where the topic author would roleplay as a certain character from a LEGO theme and answer questions from fellow users. But what you may not know is that I’m the one who started that trend with my “ASK FANG-SUEI!” topic. This is the story of how that happened.

    The inspiration

    Before going any further, it’s important to acknowledge that I did not invent the ask-character format entirely on my own. Like many inventions, the format I created was greatly inspired by existing creations.

    Back in 2011, when LEGO fully launched their Alien Conquest theme, there was a neat “Ask an Alien Page”, where users could submit questions, and each day one of them would be answered by one of the aliens in video format. (Well, more like audio with the same visual footage over and over. 😛)

    An archived version of the “Ask an Alien” page on the LEGO Alien Conquest website.

    My memory is hazy, but I figure this must have been one of the things that inspired “ASK FANG-SUEI!”, considering I created that topic in early 2012.

    I do recall one thing being a definite inspiration: shortly before creating my topic, I saw a topic in the Hero Factory subforum by legoninja0701 titled “toxic reapa chat”. Unfortunately, though I was able to find it listed among other topics in an archived version of the subforum, the topic itself doesn’t appear to have been archived.

    The “toxic reapa chat” topic listed next to one of many “Ask ___” topics on April 9, 2012.

    Going off of memory, however, the topic was essentially just a prototype of the ask topic format. The title said it all, really: it’s a roleplay topic for chatting with the author, who pretended to be Toxic Reapa: a villain from the contemporary wave of Hero Factory sets. It had a decent number of responses, but it’s popularity wouldn’t last much longer than most other topics. Still, I liked the concept behind it, and it inspired me to try something similar.

    Having recently become a big fan of the Ninjago TV series, I decided to try and put my own spin on “toxic reapa chat”, using a Ninjago character. I chose the serpentine character, Fang-Suei, probably because he was a blank slate I could inject my own personality into without contradicting canon. And thus, on February 29, 2012, “ASK FANG-SUEI!” was born. Here’s an archived version of the topic.

    The topic as it appeared in November 2014. (I couldn’t find any earlier archives of the topic.)

    Rise of the sssssnake

    The topic was an instant hit. As you can see in the archived copy, people immediately bought into the concept and came up with all sorts of interesting questions.

    Since the character was just a background mook, I basically had to make up the answers to every question on the spot, though I tried to keep them consistent with each other and with the official canon.

    One of my gimmicks I came up with was to add extra “s”s to some words. You know, like thisssss. I imagined the character kind of sounding like a vampire, so I’d also start various words with “v”, because vhy not.

    The topic quickly grew to be more popular than I expected, reaching 176 replies by March 11. The next day, it was featured as an “Editor’s Pick” on the LEGO.com home page. This resulted in 267 new replies in a single day. The topic then remained on the home page for a whole week. It felt like my 15 minutes of fame, except it lasted way longer.

    The LEGO.com home page on March 12, 2012. Archived on the Wayback Machine.
    The Ninjago subforum on March 25, 2012.

    Soon, I started to see clone topics with titles like “Ask Jay”, “Ask Nya”, and etc. pop up in the Ninjago subforum. And soon after, the format had spread to every other subforum. If there was a relatively popular character in a given LEGO theme, you can bet there was an ask topic for them. There were so many, that there would often be multiple ask topics for the same character!

    Suffering from success

    Unfortunately, the topic ended up getting so popular, it became very difficult to keep up with replies. Simultaneously, one of two things happened, but I can’t remember which:

    • I got grounded from my computer, or…
    • I was considering giving up my LEGO obsession during Lent

    Either way, the timing could not have been more comedic. When I told my father about the topic getting so popular, he encouraged me to return to it, but by that point the backlog seemed insurmountable.

    Eventually, I just gave up on trying to play catch-up with the topic. At some point I tried to reboot it with an “Ask Fang-Seui 2” topic (I can’t remember the exact title), but I quickly lost interest and got busy with other things. In total, the original topic received 2822 replies (including my own).

    Hindsight in 2020

    I never set out to start a massive trend, but looking back, I think I now know why it happened.

    Obviously, being featured on the LEGO.com homepage had a lot to do with it. But the topic was already more popular than usual before that. And there had to be a reason for the LEGO website staff choosing my post in my particular.

    On the LEGO Message Boards, roleplay was huge. Almost every subforum had its own subforum for traditional forum-based roleplay. But beyond that, even the regular subforums had plenty of themed chatroom topics that were more or less just casual forms of roleplay, e.g. “LEGO Club Food Fight Room 2” and “The Nerd Refrigerator”.

    “toxic reapa chat” had the clever idea of having a roleplay chatroom based around a single character. But what my topic did was concentrate and refine that idea into a simple question-and-answer format. The purpose of a “chat” topic may feel a bit vague: what exactly are you supposed to chat about? But the title of “ASK FANG-SUEI!” immediately made it clear what kind of replies were expected, and it did so in all-caps. 😜

    Not only was the new “Ask ___” format easy to understand, but it was just as easy to remix. Just swap out Fang-Suei and insert literally any LEGO character, or even multiple characters at once. And that’s exactly what people did.

    It probably also helped that Ninjago was quickly becoming the most popular in-house LEGO theme, to the point where the theme was quickly brought back after its initial planned run had ended. I could not have chosen a better subforum to post in.

    Legacy

    The ask topics, as the official unofficial LMB Wiki calls them, became a staple of LMB culture. There were still active ask topics when the boards shut down in early 2017, 5 years after I started the trend. In fact, on the LMBs’ fan-run spiritual successor, The Brick Boards, people are still creating topics like “Another Ask the Ninja 2.0”.

    As for legoninja0701, I wondered if he was still active in the LEGO community. A quick search uncovered only a Brickset profile with the same name, though it’s been inactive since April 2012. Perhaps unsurprisingly, his set collection includes Toxic Reapa.

    If you ever happen to stumble upon this post, legoninja0701, I just want to say thanks. Without your “toxic reapa chat”, there would be no “ASK FANG-SUEI!”.

    I feel honored to have contributed to this part of LMB history. It was definitely fun to try and come up with answers to random questions, even if it did end up overwhelming me in the end. Maybe someday, just for a bit of nostalgic fun, I’ll open a new ask topic on The Brick Boards…

  • Consciousness Contradicts Materialism

    Consciousness Contradicts Materialism

    A popular belief challenged

    Most scientists follow the philosophy known as materialism: the belief that the physical universe is all that there is. According to materialism, everything can be reduced to particles interacting with each other. All that you are is nothing more than a bunch of particles interacting with each other according to the laws of physics.

    Perhaps you think this makes perfect sense right now. But I believe materialism is actually fundamentally, logically incorrect. In fact, I know it is incorrect. It goes without saying that this is a very bold claim. If one follows scientific reasoning, then one should not make this sort of claim without hard evidence to back it up. And that is exactly what I am about to do. In this article, I shall destroy the concept of materialism with facts and logic.

    Complexity and consciousness

    A simple machine

    Picture this: a crank connected to a gear, connected to another gear, connected to a wheel. This is a machine. A simple machine, but a machine nonetheless. It takes input through its crank, which could be considered a very basic sort of sensor. The crank “senses” input when it is turned, which causes it to turn the gears. These gears eventually give an output: a turning wheel, in this case.

    This machine is extremely simple. Between the input and the output is nothing but a few gears. Actually, the gears themselves could be considered part of either the output or the input. The movement of one gear is the output of the crank, and this gear acts as a sort of rotation sensor, which then affects its output: the second gear. And that is all there is to it. It is just a bunch of parts that take an input and give an output. The machine is certainly not conscious of anything. How could it be? It is just a bunch of parts moving together.

    Adding more gears only increases complexity

    But what if we make the machine more complex? We could add more inputs. We could also add more gears. More outputs. We could add all sorts of mechanical parts. With some patience and some clever engineering, you could turn the simple machine into a mechanical calculator. But it is still just a machine.

    Electrical is still a form of mechanical

    How about using electric components instead of mechanical ones? Does that make a difference? Nope. An electric computer is still a form of mechanical calculator. We have simply traded the clunky large-scale mechanics of gears for the small-scale mechanics of electrons. My laptop, in spite of its complexity, is still a machine that takes input and produces an output with nothing but a bunch of interacting particles in the middle. It is still nothing but a machine. No consciousness.

    Machine learning does not create consciousness

    But what if we make the machine learn stuff? Maybe that is the key to consciousness! Well, consider this: all forms of “learning” in computers can be reduced to basic concepts of logic. If A then do B, otherwise if C and D then do E. The machine may store data from past interactions, but that data is nothing more than particles charged and arranged in a particular way. There is still nothing more to the machine than what you can observe.

    Randomness does not create consciousness

    How about randomness? Does that change anything? No, not really. Random input is just random input. Ultimately, the randomness is derived from the physical mechanics of how the universe works.

    Complexity can not create consciousness

    No matter what you do, no matter how complex your machine gets, it is still nothing more than a bunch of particles interacting with each other according the laws of the physical universe. The only thing you can do is add more complexity. But that won’t magically make your machine conscious. And besides, science does not believe in magic.

    The brain is a computer

    Hang on, what about the human brain? Is it different from other machines? Well, it’s certainly quite complex. It’s got a lot of stuff going on inside it. But it’s still just something that takes input and produces output, with a bunch of neurons in between. In a way, the neurons are not that different from the gears mentioned earlier. So by reason of pure logic, one can deduce that the brain cannot be the source of consciousness. After all, it is just another machine.

    But wait… according to materialism, consciousness can be explained with physical phenomena. We have a problem here. The reasoning of materialism forces us to believe that consciousness must be reducible to physics, yet there is no way to explain where consciousness comes from.

    Well, maybe consciousness just isn’t real, then. That seems like a sensible answer. Until of course you realize that you are conscious.

    Consciousness and materialism

    I am

    As I write this, I look around myself. I see my hands typing on the keyboard and the laptop screen in front of me. I see a whole world all around me. But where does this picture come from? My eyes are only sending electrical signals to my brain. And once they reach the brain… uh… that’s it. At no point does the image I see in front of me exist. It’s just a bunch of particle interactions.

    So how is it that I am seeing? How is it that I am hearing? How is it that I am… wait a minute…

    I am. I am? How can it be that I am? How am I?

    I exist. I am myself, but I am not that which I observe. Everything that I observe is not me. Clearly, my brain is the center of my connection to the physical universe, yet the brain itself can not be me, for the brain is just another part of the world I observe.

    The fatal flaw of materialism

    Materialism ultimately forces you to believe that there is no such thing as consciousness. But to believe that means that you are nothing but a machine. At the base level you are controlled by the physical laws of the universe. You have no free will. There is no right and wrong. There is really no you. You could jump off a cliff right now and it would not matter. Nothing matters. It is all just a bunch of particles interacting with each other, according to materialism.

    And yet… that contradicts reality. The thing about humans is that we think. And if you think about it, thinking is not something that can be entirely explained with physics. Sure, the brain stores info, but that info is just a bunch of particles organized in a certain way. Particles don’t think. And your brain is nothing but a bunch of particles. As we already discovered, more particles and more complexity does not create consciousness. According to materialism, there is nothing there but the particles. And yet here I am. And there you are.

    Conclusion

    The spiritual is scientific

    Finally, reason and logic will take you to the only possible resolution: materialism is incorrect. Logically, there must be another side to the universe that is separate from the physical, yet is able to interact with it somehow. Most people call this the spiritual. In an ironic twist, true science does not deny the existence of the spiritual, but instead confirms its existence. In hindsight, this fact is rather simple to prove. But it seems that some of the most powerful truths are simple.

    Why I wrote this article

    I would be a fool to think that I am the first to point this out. You can bet I won’t be the last, either. I don’t expect this article to change the minds of the mainstream scientific community. In fact, I don’t think the word “scientific” accurately describes them. If they actually followed scientific reasoning, they would have abandoned materialism long ago. Materialism is their religion, and anyone who dares to question it is labeled a crackpot.

    I am writing this for the people with open minds. Those who are on the fence on whether or not the spiritual is real or not. Those who actually follow the scientific method. I fully believe that the existence of a spiritual side to the universe can be proven to exist via pure reason and logic. I hope that this article demonstrates that.

    Summary

    So, to summarize: materialism is incorrect because the laws of the physical universe cannot explain consciousness, and consciousness can be proven to exist by the fact that you are conscious. This proves that the universe must have a non-physical side, otherwise known as the spiritual.

    Until next time, this has been Zebulan, and I thank you all for reading.

  • Stuck Between a Block and a Hard Place

    Stuck Between a Block and a Hard Place

    Introduction

    WordPress Gutenberg icon

    WordPress is getting a new editor, and I’m getting a bit worried. The plan to introduce the new editor, Gutenberg, into core WordPress in the 5.0 update has been stirring up all sorts of emotions ranging from excitement and joy to confusion and frustration. I think most people agree that WordPress needs a new editor, but many have criticized the current state of the Gutenberg project and its management. Personally, I feel somewhat conflicted over the whole situation, both believing that Gutenberg is the future of WordPress while simultaneously feeling concerned over the management of the project. This article provides an overview of what Gutenberg is, the issues and controversy surrounding it, and my own opinion of the project.

    What Gutenberg is

    Project background and goals

    Images of Gutenberg 0.1.0 and 4.6.1

    Gutenberg is a long-term project to overhaul WordPress post and page creation, starting with the planned introduction of the Gutenberg editor in WordPress 5.0. The editor is currently available as a plugin. At the , Matt Mullenweg, co-founder and lead developer of WordPress, described the goal of the editor as follows:

    The editor will endeavour to create a new page and post building experience that makes writing rich posts effortless, and has “blocks” to make it easy what today might take shortcodes, custom HTML, or “mystery meat” embed discovery.

    The customizer will help out the editor at first, then shift to bring those fundamental building blocks into something that could allow customization “outside of the box” of post_content, including sidebars and possibly even an entire theme.

    Phased approach

    The project is being developed in phases, with the first phase resulting in the bulk of the WordPress 5.0 update. The second phase will likely come in WordPress 5.1. Quoting Mr. Mullenweg again:

    Phase 1 of Gutenberg has been about upgrading the writing and editing experience of WordPress, across posts, pages, and the delightful things people do with post types. The block framework will allow us to drastically simplify the various concepts and user interfaces across WordPress, including widgets, TinyMCE magic sections, and shortcodes.

    Phase 2 is about thinking outside the box, namely the post and page box, to allow Gutenberg to handle entire-site layouts. We will replace widgets with blocks, so any block will be able to be used in any registered “sidebar” for legacy themes, and we will upgrade “menus” to a navigation block.

    Phase 2 will be led by @alexislloyd on the design and product side, and @youknowriad on the technical side. Please join me in welcoming these two and sharing your thoughts on Phase 2.

    I’ll propose and discuss Phases 3 and 4 of Gutenberg at WordCamp US in December.

    I recommend reading more about the design principles and key concepts of Gutenberg in the official handbook.

    Project potential

    WYSIWYG editing

    Gutenberg is a project that has far-reaching and long-term potential for WordPress. Perhaps the most obvious benefit is the introduction of a more WYSIWYG editing interface. In the editor, unselected blocks should look as similar to the front-end as possible. While selected, they may optimize their appearance for editing (like a caption field appearing when you select an Image block) and reveal various other editing controls in the block toolbar and inspector. Currently, themes must specifically declare styles for the editor, since current technical restrictions (the lack of widespread browser support for Shadow DOM, for example) prevent the front-end theme styles from being used directly by the editor. The long-term hope/goal, however, is for the editor to use the same stylesheet as the front-end, once the necessary technical prerequisites are met.

    Blocks everywhere

    The block concept supersedes WordPress widgets, page builder widgets/modules (such as those found in Beaver Builder or Divi Builder), and some (but not all) use-cases of shortcodes and meta boxes. One of the goals is to provide a single way to add content to a page, whether that content be text, images, videos, embeds, galleries, accordions, columns, or whatever else you can think of.

    One possibility is that page builder plugins could adapt to use the block APIs for their modules/widgets. These blocks could then be made independent of any particular page builder plugin, helping to avoid the issue of vendor lock-in. Page builder plugins could become more modular, with the visual interface being one plugin, the functionality extensions being another, and the blocks being yet another separate plugin, ensuring optimum compatibility with other plugins and reduced dependency on monolithic all-in-one solutions that lock you in to a particular ecosystem.

    Usage outside of WordPress

    Speaking of avoiding vendor lock-in, Gutenberg itself has potential even outside of WordPress. The block concept, the block APIs, and even the entire Gutenberg editor could be adapted for usage within other content management systems or even standalone applications. Actually, there is already an implementation of this: Drupal Gutenberg. There is even already an online library of blocks that can used in both WordPress and Drupal called Gutenberg Cloud.

    The issues and controversy of Gutenberg

    Variety of opinions

    There are a variety of opinions regarding Gutenberg. Some folks dislike the concept of Gutenberg entirely, perceiving it as a flawed attempt to compete with Squarespace and Wix. Others like the concept but are disappointed with how various issues have (or have not) been handled. Additionally, some are concerned by potential backwards compatibility issues with existing sites. And then there are those who are simply confused entirely by Gutenberg. Just check out the comments on this article to see what I mean.

    Overall, it is hard to tell whether the reception of the editor has been mostly positive, mostly negative, or somewhere in between. Do high active plugin installation numbers mean people are happy with the new editor? Or does it mean that people are leaving it installed because they feel forced to learn the new editor? Do installation numbers for the Classic Editor plugin signal a wide disapproval of the new editor? Or is the case simply that people are taking precautions to ensure compatibility with old plugins? Are the negative reviews of the Gutenberg plugin just a loud minority? Would a WordPress 5.0 release right now be disastrous, or are people just overreacting? The rapid development of Gutenberg throughout the year has only made this more difficult. Feedback from last year or even 6 months ago may be completely obsolete, or it may still be as relevant as ever.

    ClassicPress

    ClassicPress icon

    Believing that WordPress was moving away from serving the business needs of its users with the introduction of Gutenberg, Scott Bowler created a business-focused fork of WordPress called ClassicPress. Right now, the only significant difference from WordPress is the lack of Gutenberg. Because of this, the fork is currently rather redundant since the Classic Editor plugin exists and will be supported until at least . Presumably, though, the fork will develop in its own unique direction apart from WordPress as time goes on. I have no idea if this fork has any lasting power, but I suppose we shall find out within the following couple of years. (Fun fact: WordPress is itself a fork of b2/cafelog.)

    Usability and accessibility

    General usability

    Many people have expressed concern over the usability of the editor, both for the average user and for those with disabilities. WordPress plugin developer John James Jacoby cleverly used a post created in Gutenberg to demonstrate his less-than-ideal experience with the editor. WordPress Tavern founder Jeff Chandler expressed his difficulty in figuring out how to float images next to text, despite the process technically being possible in fewer steps compared to the current editor (retroactively named the classic editor).

    Accessibility

    Controversy

    Accessibility in particular has been the source of much controversy. WordPress accessibility team lead Rian Rietveld resigned on due to how the development of Gutenberg was handled with regard to accessibility. , the WordPress accessibility team posted a Report on the Accessibility Status of Gutenberg, concluding with this statement:

    The accessibility team will continue to work to support Gutenberg to the best of our ability. However, based on its current status, we cannot recommend that anybody who has a need for assistive technology allow it to be in use on any sites they need to use at this time.

    As you can imagine, both the resignation and the report sparked a lot of discussion, both civil and not-so-civil. Recently, on , Matt Mullenweg wrote the following in a Gutenberg FAQ:

    We’ve had some important discussions about accessibility over the past few weeks and I am grateful for those who have helped raise these questions in the community.

    Accessibility has been core to WordPress from the very beginning. It’s part of why we started – the adoption of web standards and accessibility.

    But where I think we fell down was with project management — specifically, we had a team of volunteers that felt like they were disconnected from the rapid development that was happening with Gutenberg. We need to improve that. In the future I don’t know if it makes sense to have accessibility as a separate kind of process from the core development. It needs to be integrated at every single stage.

    Audits

    Notably, WPCampus is currently seeking funding to conduct an audit of Gutenberg accessibility. Automattic will also be funding a separate study of the accessibility of not only Gutenberg, but WordPress as a whole.

    Finally, Automattic will be funding an accessibility study of WordPress, Gutenberg, and an evaluation of best practices across the web, to ensure WordPress is fully accessible and setting new standards for the web overall.

    Release schedule

    Prior schedule

    Naturally, there has been much discussion over when WordPress 5.0 should be released. A proposal in suggested . Although the Gutenberg project had already stretched on for longer than initially planned, even supporters of the project (including myself) were unhappy with this date. Yoast founder Joost de Valk posted his thoughts on the current proposal on his blog, noting his appreciation for the new editor but also his concerns regarding accessibility and stability.

    Let me begin by stating that I love Gutenberg. It’s the best thing since sliced bread as far as content editing is concerned. I’m writing this post in Gutenberg. I started writing it on my iPhone. It rocks. But it also still has numerous bugs. In fact, the editor broke on me during writing this post and failed to autosave all the contents.

    Mark Root-Wiley of MRW Web Design also expressed concern over the planned November release:

    Various members of the WordPress community shared similar sentiments, with several pushing for a January release. As the proposed release date neared, the developers worked at an impressive speed to try and fix as many issues as possible. Ultimately, however, they could not resolve all the blocking issues in time. They tried pushing the release to the first fallback date: but soon realized they were unable to meet this date either. The first release candidate did come out on the , however.

    Current schedule

    The initial proposal gave as a second fallback date. Despite this, the project leads decided to drop the proposed schedule altogether. They decided that the release date should simply be dependent on the feedback received on the release candidates. Matt Mullenweg posted this explanation in his Gutenberg FAQ:

    The stability and open issues in the release candidates thus far makes me optimistic we can release soon, but as before the primary driver will be the stability and quality of the underlying software. We made the mistake prior of announcing dates when lots of code was still changing, and had to delay because of regressions and bugs. Now that things aren’t changing, we’re approaching a time we can commit to a date soon.

    The current release candidate is WordPress 5.0 RC3. The current plan is to release WordPress 5.0 on . Notably, this is the expected release date of PHP 7.3. WordPress 5.0 includes some fixes to make it compatible with that version of PHP. The release may be delayed if any new blocking issues are found. If such issues arise, a quick 4.9.9 release with backported PHP 7.3 fixes may be released. But at the moment, it looks like the next major WordPress update is right around the corner.

    There is also a series of bi-weekly 5.0.x updates planned to come out after the initial 5.0 release. These releases will focus on fixing various minor bugs (or newly discovered major bugs) and small improvements.

    My thoughts on Gutenberg

    Things I like

    For the most part, I really like Gutenberg. In fact, I wrote this article (and all the previous ones since ) in Gutenberg. I’ve been testing and using the editor since around this time last year. Rather than echo the obvious pros like WYSIWYG editing, contextual controls, and other stuff that everybody else talks about, this section will point out some things I am personally happy about in my own experience.

    Blocks

    I am a big fan of the block concept. I have always enjoyed modular, customizable systems. My favorite toy is LEGO. My favorite game is Minecraft. The block concept is a bit like those.

    I even like the decision to have each paragraph be a separate block. In fact, if you prefer having all paragraphs or even all text in a single block, there is nothing stopping you from creating a custom freeform text block that does exactly that. Actually, the core Classic block already does nearly the same thing, albeit tailored for backwards compatibility needs.

    I like that blocks fallback more gracefully than shortcodes. I also like that the block API provides a common format that page builder plugins could all share in a way they never could with widgets. One of the biggest issues with most existing page builder plugins is their usage of shortcodes. Trying to move to another page builder is a hassle, since the content is not directly transferable. Disabling the page builder results in a mess of unparsed shortcodes all over your site. Blocks could fix both of these problems.

    Block-level HTML editing

    Image of Edit as HTML option in Gutenberg

    One feature that I immediately liked was the Edit as HTML option, which let you edit the HTML of a block right there in the editor. Back in the classic editor, if you wanted to edit the HTML, you had to view the entire post markup. This meant having to find the section you were working on every time you switched back and forth. But with this new Gutenberg feature, only the block you were working on would switch to an HTML view. This made tweaking markup way easier. I had previously heard some people suggest that Gutenberg was dumbing things down at the expense of advanced users. But contrary to that idea, I found that Gutenberg made it easier for me to do advanced stuff with HTML.

    Reusable blocks

    One neat feature of Gutenberg is reusable blocks. You can save content and reuse it anywhere on your site, and changes sync across all instances of the block. I’ve already found a neat way to use this feature on my website. All my blog posts that I originally posted on SuperGeniusZeb.com now use this reusable block at the end:

    If I ever want to update the wording of this notice, I can do it once and every post that uses it will be affected.

    You can also convert an instance of a reusable block into a standard block. This allows you to use reusable blocks as templates. For example, you could create a call to action (CTA) template from existing blocks. This would allow you to quickly make a CTA and avoid building it from scratch.

    I imagine that in the future, website headers and footers could be made with reusable blocks as well.

    Cleaner content

    Despite its faults, I often enjoy using Gutenberg. I also enjoy using Divi Builder. I have never enjoyed using the classic editor. There are a couple reasons for that, but the most prominent is that the classic editor always felt messy to me.

    Things like autop have annoyed me since I started using WordPress back in 2009. On the one hand, the automatic creation of paragraphs made sense for people using the visual mode of the editor. But I was often using the text (HTML) mode, and it made no sense to me at the time that my line breaks were being turned into paragraphs on the front-end. I couldn’t see any <p> tags; they were just being magically added behind the scenes. And how could I forget the mysterious  s that would appear after trying to format the HTML myself?

    The same kind of issue occurred to a lesser degree with the other ways that WordPress cleaned up HTML. You could install plugins to disable the cleanup, but it would affect either your entire site or at least your entire post. What if I wanted WordPress to sanitize my code in some cases but not in others?

    When I started using Gutenberg last year, I noticed one thing very quickly. The paragraph tags were no longer invisible. I could actually see them in Code Editor mode. Additionally, it was now very clear where the start and end of a paragraph was. Semantic mistakes like lists nested in paragraphs were no longer possible. But if I wanted to do something special and avoid the automatic cleanup, there was now a Custom HTML block that I could use! Overall, Gutenberg felt both cleaner and more flexible.

    Thinks I dislike

    Gutenberg has improved dramatically since its first release, but there are still many things that are less than ideal. In this section I will talk about some of the things that bother me.

    Writing flow issues

    Issues that interrupt a person’s writing flow may be the worst kind of issue for an editor. Unfortunately, Gutenberg still has several of these kinds of issues. Of course, not all writing flow issues are as serious as others. Some are common, while some occur only in specific edge cases. Some are quirky bugs, such as this issue with HTML entities and the link interface that I found while writing this article. Others are simply oversights in the design process, such as the keyboard navigation issues of the Quote block. Personally, I am willing to put up with most of these issues for now, but I worry that others may not be so forgiving.

    Nested block UX

    One essential feature of Gutenberg is that blocks can be nested. This is useful for things such as columns, sections, accordions, and other advanced blocks. Unfortunately, the UX for interacting with nested blocks is far from perfect. The most notable issue is trying to select a block that contains child blocks. If the parent block is barely larger than its children, the clickable area to select the parent is often quite small. Things only get worse when you start having multiple levels of nesting.

    The Block Navigation menu introduced in Gutenberg 4.1 partially resolves this issue, but I think both it and the general nested block UI can still be improved. I think that the Block Navigation menu should let you drag and drop blocks from within the menu, as well as delete them. Another improvement would be to turn the Block Navigation menu into a sidebar and use the plugin API. This would allow you to unpin the feature from the main editor bar if you never used it. (I think the Document Outline should also use the plugin API for the same reason.)

    One suggestion I have heard is to expand the padding of a block in the editor when you select it or its children. I think that could definitely make interacting with nested blocks easier. I particularly like this idea since it fits in with Gutenberg’s methodology of adapting selected blocks for editing.

    As Gutenberg moves further into page building territory, interaction with blocks using nesting will become more common. Hopefully, this will result in more refinement of the editor UX around nested blocks.

    Release schedule

    The current release date worries me somewhat. Though I personally am fine with using Gutenberg right now, I don’t think everyone is as tolerant of bugs and quirks as I am. I know a lot of small improvements and bug fixes are coming in the bi-weekly 5.0.x updates. However, it seems strange that they are planning to release 5.0 while already working on a follow-up bug fix release. To be fair, most of these 5.0.x fixes are minor issues. But there are a few things like performance enhancements and writing flow fixes that, in my opinion, belong in the initial release. I fear that releasing now could mean a lot of bad first impressions. Despite being delayed multiple times, the release still feels premature.

    But maybe there is no reason to worry. People are often slow to update their software. Thanks to that and the bi-weekly 5.0.x updates, most people may never see the bugs on release day. Perhaps I just notice bugs more because I like to play around with features. It will definitely be very interesting to see the public reaction after the release of WordPress 5.0. All I know is that if I was the release lead, I would have delayed Gutenberg until at least January. Even if it wasn’t actually necessary, it might at least help ease some of the tensions in the community.

    An obscure and complicated but still annoying bug which will probably not be fixed before 5.0.

    Conclusion

    The Gutenberg project has great potential, both within WordPress and outside of it. Unfortunately, it also has a lot of controversy surrounding it. Opinions on Gutenberg vary greatly, both among its supporters and its opposition.

    Is Gutenberg ready? I don’t know. I clearly find it ready enough for my own use. It’s other people I’m worried about. It is hard to tell if the complaints you see on the internet foretell a larger reaction, or if, as Mr. Mullenweg suggests, this will end up being the most anti-climactic release in WordPress history. Ultimately, nobody can know for sure until it actually happens. And it looks like it is about to happen.

    In the end, I want Gutenberg to be a success. In the long run, Gutenberg could benefit everyone who uses WordPress. I just hope it doesn’t trip and fall at the start of that run.

  • New Website!

    I’ve been working on it for a while now, but I am finally ready to launch my new website: Zebulan.com! Since early this year, I have been wanting to move away from the SuperGeniusZeb name and to something less pretentious… like my actual name!

    Notably, I have not yet moved over the pages for my LEGO and Minecraft projects. I plan to make my own WordPress plugins to add custom post types for LEGO MOCs, and Minecraft mods and add-ons, and I wanted to use those when I moved over the content from my existing website. For now, I just link to the old site where necessary.

  • How to Install Pamac on Arch Linux

    The problem with pacman

    The default package manager of Arch Linux and its derivatives, pacman, is quite nice. Installing packages from the official repos is often quite simple once you learn a few commands.

    Another nice feature of Arch Linux is the AUR, which is a huge repository of community-maintained packages. The AUR has allowed me to install nearly everything on my laptop using the package manager, allowing me to benefit from simple package installation, uninstallation, and updates. On many other Linux distros, while most popular apps are in the repositories, you still wind up having to install multiple packages manually whenever you want to install something less common; keeping track of manual packages can get frustrating, as you do not get the benefits of automatic updates, and installing and uninstalling them is not the most straightforward process. The AUR is the primary reason I use Arch-based Linux distros.

    However, all is not perfect. Not by default, anyway.

    First of all, pacman is a command-line app. Of course, that is exactly what it is supposed to be, and CLI apps will always be useful in many situations (how else would you install packages when you were not using a desktop environment), but I am sure most people would agree that a CLI app is not the ideal way to install and update applications.

    Second, pacman can not directly install packages from the AUR. You have to use makepkg to install those packages. This is also far from ideal, and is definitely not as smooth of a process as installing apps from the official repositories.

    Thankfully, there is a solution to both of these problems.

    Meet Pamac

    Pamac is a GUI front-end for libalpm, the ALPM library. It allows you to easily browse, install, uninstall, and update packages from not only the official repos, but also the AUR. It is a fantastic application originally developed for the Arch Linux derivative, Manjaro, though it works in mainline Arch Linux and Antergos as well.

    Speaking of Antergos and Manjaro, both of those distros come with Pamac installed, so if you are using those distros then there is probably no reason to be reading this article. But Arch Linux itself does not have this app installed by default or even in the official repos, so you will have to install it from the AUR, and as stated earlier, this is not the simplest of procedures.

    The actual installation guide

    Now that I have explained why you would want Pamac, it is time to actually show you how to install it.

    Install the base-devel package group and git if you haven’t already.

    sudo pacman -Syyu base-devel git

    Clone the Pamac PKGBUILD and build dependencies into a newly-created temporary folder under your home directory.

    git clone https://aur.archlinux.org/pamac-aur.git ~/tempfolder

    Build and install Pamac.

    makepkg -sic BUILDDIR="~/tempfolder"

    Delete the temporary folder created earlier.

    rm -r ~/tempfolder

    And that is it! You have now installed Pamac. To enable AUR support, open Pamac and navigate to the options (the button next to the search), then to PreferencesAUR and enable Enable AUR support. I also recommend installing pamac-tray-appindicator if you are using KDE Plasma as your desktop environment to get a nice tray icon for Pamac.

    Useful additional resources

  • Looking Back on “A Laggy Boat Ride” (SGZ Plays MC #5)

    Looking Back on “A Laggy Boat Ride” (SGZ Plays MC #5)

    The title, the thumbnail, and the lag

    “A Laggy Boat Ride” was a laggy mess. At least in its original form, anyway.

    I’ll start with the title. It isn’t exactly a title that entices you to watch the episode. If anything, it deters you from watching it. It mentions the worst part of the entire video, and says nothing about the parts that are at least somewhat interesting. There isn’t even a pun in the title making fun of the lag, so it just ends up being a rather bland and generic title that tells you why you shouldn’t watch the episode, but not why you should.

    Then there’s the thumbnail. I forgot to mention that episode 4 was the first episode that I made a thumbnail for. That first thumbnail was pretty basic, lacking a screenshot from the actual episode, and having nothing but some images and text copy-pasted onto a white background.

    I wanted to have a consistent style for the thumbnails, but I ended up changing the style for episode 5 because I realized that white backgrounds were kind of boring. The thumbnail for episode 5 was made using the same project file, and so the logo and cropped image of my player skin were in the exact same position, but the rest of the thumbnail was changed quite a bit.

    But the inconsistency or relatively cheap look of the thumbnail doesn’t bother me nearly as much as the fact that the thumbnail, like the episode title, also spotlights the lag in the episode. I thought that since the episode had so much lag in it, I might as well advertise it as a “feature” of the episode or something, but in hindsight that was a bad idea. Pointing out your flaws doesn’t fix them or make them less bad.

    If I was smarter back then, I probably would have edited out the lag and used a title mentioning something about exploration, snow biomes, and/or the wolves. But for whatever reason, I didn’t edit the lag out. Perhaps it was because my current video editor at the time (VSDC Free Video Editor) crashed constantly, or because I was lazy, or because I was inexperienced, or perhaps all of the above.

    As for what caused the lag in the first place, I think it was a combination of my hard drive being almost entirely full and my recording software (Fraps) being very resource-intensive. My hypothesis is that because my hard drive was so close to being full and fragmented, the free space was scattered in small pieces throughout the drive, and so recording a video meant the hard drive had to keep jumping from place to place to keep up. And it wasn’t just small video files… Fraps made large AVI files, and even though I turned down the quality settings when I recorded the episode, the files were still pretty big. At the same time, when I would load in some chunks of the world or generate new ones, that would require reading from another part of the hard drive, so Fraps and Minecraft were battling for both CPU and hard drive usage.

    These days, I’ve cleaned out a lot of space on my hard drive by moving my videos onto external drives and cloud storage. I have also discovered that recording video onto an external hard drive seems to help by freeing up the internal drive to be used by the game. Additionally, when recording on Windows 10, I currently use the built-in Xbox Game DVR to record videos, which seems to be far less resource-heavy, in part due to the fact that it outputs compressed MP4 files whereas Fraps made near-lossless AVI files.

    (As a side note, I really wouldn’t recommend using either Fraps or VSDC Free Video Editor if you want to make videos. OBS Studio is better for recording and is also libre and cross-platform. The Windows 10 Xbox Game DVR also works well as a simple solution. And as for editing, I would recommend Kdenlive. I don’t know if VSDC still crashes as much as it used to, but Kdenlive has more features and has the bonus of also being libre and cross-platform, unlike VSDC.)

    The episode itself

    So far, I’ve only talked about the lag and title and thumbnail that advertised it. But what about the rest of the episode? Is there some good content left if you take out all the lag?

    Wheeeee!

    Unfortunately, even without the lag, the episode is still pretty boring. The entire segment in the caves feels kind of pointless and takes up far too much time. Messing around outside with the endermen is kind of fun to watch, and getting my first ender pearl is kind of significant, but it’s still a segment where not much happens. The boat ride really should have been sped-up or I should have at least been talking about something interesting during it.

    The part of the episode where I find the snow biome is probably the most interesting part of the entire episode. It has me exploring a new area unlike anything seen before in the series, and I find my first sugar cane and my first wolves there. I even get the “Cow Tipper” achievement. Actually, that might have been my first cow, but I haven’t checked the previous episodes so I’m not sure.

    Unfortunately, the best part of the episode is followed by the worst part: the boat ride back home that inspired the title. I really should have cut this part out. Since I already showed my trip to the snowy region, I didn’t have to show my trip back especially after the footage turned out to be so frustrating and boring to watch. If I had just cut out this one segment or ended the episode while I was at the snowy region, then the episode would have a different title and would have finished on a high note.

    Overall, episode 5 lacks in the area of interesting content, with most of the episode just being stuff that’s already been done in a previous episode. I already did cave exploration in the previous episodes, and this episode spends a long time underground and hardly shows anything new. I already fought mobs in previous episodes, and this episode just shows me doing that again, but with endermen. When I finally do something new in the form of riding a boat and exploring, I don’t utilize the time spent in that activity as well as I could, and then I waste time with pointless footage of riding back home, only this time with high amounts of lag.

    Ironically, there’s an apology for the audio quality in the episode at the end of the intro, and yet upon rewatch, I think the audio quality in this episode is completely fine… compared to the previous 4 episodes, anyway. If anything, there should have been an apology for the lag in this episode or an apology for the audio in episode 4, which had bird noises or something in the background.

    As I expected, episode 5 unfortunately breaks the trend of increasing quality throughout the previous 4 episodes. Overall, I would rank it as the second worst episode, with only episode 1 being worse. Very little happens in the episode, and what does happen doesn’t have much effect on the next episode. You could probably skip this episode and you would hardly miss anything.

    The re-edit

    But what about the re-edit? Was I able to salvage something decent out of this mess? Much to my surprise, yes! After cutting out all the lag and the majority of the cave segment, as well as speeding up the boat ride and making the usual polish cuts, I ended up with a fairly decent video that I’d say is pretty watchable. It’s not as good as the re-edits of episodes 3 and 4, but it’s a huge improvement over the original version of episode 5.

    In total, I cut the episode down from a length of to ; that’s a decrease of . The original version of episode 5 was already the shortest one I had made, and the re-edited version is similarly the shortest of the re-edits so far. Although not much happens in the episode, you only spend watching the re-edited version, so it doesn’t take up that much of your time and the lack of content is more forgivable.

    I probably could have cut it down even further down to below 10 minutes, but I was a bit worried that if I kept cutting it down, there would hardly be enough left to call it an episode. Unfortunately there’s not much interesting content in the episode, so I can’t just cut out everything that isn’t really exciting. If I did, then there probably wouldn’t be anything left. So instead, I tried to just make the episode feel like it was continually moving forward and not dragging on with nothing happening. I think this has the effect of making everything feel a bit more interesting and fresh.

    One thing I noticed while rewatching the episode and preparing for the re-edit was that, while in the caves, I mentioned the weird liquid physics in Minecraft and how it was unlikely that they would ever change due to the risk of breaking contraptions. Of course, if you’ve been keeping track of recent Minecraft news, you will have heard about how the developers had considered changing water mechanics in the upcoming Update Aquatic, but backed down due to not wanting to break existing builds and contraptions. I thought it was kind of funny how my statement from was unintentionally relevant to recent events, so I decided to keep that part of the caving segment and add a little joke about the canceled change to water mechanics.

    Another observation from re-editing this and other episodes: the Minecraft soundtrack sounds pretty cool sped-up, and speeding up footage sometimes makes it a whole lot funnier. I don’t know if it’s just me, but I think crashing my boat into the ice on the edge of the snow biome is a lot funnier sped-up, and my silly little Wheeeee! while running on the ice sounds even sillier. And of course, it has the bonus of making the footage take up less time and making the episode shorter, so that’s neat.

    Overall, I’m definitely pleased with how the re-edit of episode 5 turned out. It’s still not that great, but it’s such an improvement over the original and I was expecting worse, so I’m happy.

    Conclusion

    The original version of “A Laggy Boat Ride” is pretty bad, but the re-edit turned out surprisingly well. I still wish it could be better, and the episode could probably be skipped, but I’m happy that I was able to improve it as much as I did in the re-edit.

    Although episode 5 wasn’t that interesting and not much happens, the episode that comes immediately afterwards is the complete opposite… it’s very interesting and some really important and unusual stuff happens. I’m really looking forward to rewatching episode 6… and I think re-editing it will be quite fun as well.

    But until then, this has been SuperGeniusZeb, and I thank you all for reading!

    Watch the original version of “A Laggy Boat Ride” on LBRY and YouTube!

    Watch the re-edited version on LBRY and YouTube!

  • What I Use to Make My Videos – 2018 Edition

    , I wrote a blog post about what I used to make my videos. But now that article is outdated, since I’ve changed a lot of the software and some of the equipment I use. So here’s an updated version of that article. If you’re looking to start making videos and were wondering how I did it, then here you go…

    Equipment

    I’m still using the same laptop that I was back in . It’s a Samsung NP350V5C-A01US laptop. Its specs are as follows:

    The headset I was wearing broke, so I’m now using just earbuds and a YouMic lapel microphone, which has allowed me to record decent-enough audio.

    For video storage, I’m currently using OneDrive cloud storage, though I would like to switch to a self-hosted server at some point – partially to not be dependent on Microsoft (and Google), and partially because I want to be able to make my videos available on DTube permanently without having to pay others to host my videos on their nodes.

    Software

    Operating system

    My primary and favorite OS on my computer is Linux (or GNU+Linux, whatever you want to call it). My distro is Arch Linux, which I chose partially because I wanted a challenge for installing it, partially because I wanted to learn more about Linux, and partially because of the AUR (Arch User Repository).

    Recording

    When it comes to microphone audio recording on Linux, one neat feature I’ve discovered is that PulseAudio has an echo-cancelation module you can turn on. At least in my experience, this feature works great, and by using it and some tweaked settings in OBS, I’ve been able to get some surprisingly good audio out of my mic when recording on Linux. (My most-recent, and unfortunately also only example of this audio quality so far is “Looking Back on 2017”.)

    And speaking of OBS (Open Broadcaster Software), that’s my main video/audio recording tool on Linux. It’s a rather fantastic app for both recording and livestreaming. Unfortunately, I can’t actually use it to record most of my gameplay videos – not because of a fault in the software, but rather because of my mediocre hardware.

    My laptop lacks a dedicated graphics card, and so I only have integrated graphics (Intel HD Graphics 4000) provided by the processor. So how do I record my videos? Well, the processor has a feature called Quick Sync Video, which allows for quick video processing, but unfortunately there’s not much support for the feature on Linux. So in order to record videos with a decent framerate while playing a resource-intensive game like Minecraft, I have to use the other operating system installed on my laptop: Windows 10.

    On Windows 10, I usually just use the built-in Xbox Game DVR feature to record gaming videos. It works well enough for most cases, though sometimes it can be a bit confusing and/or tricky to know when I have started recording since the game bar doesn’t appear while playing Minecraft in fullscreen mode.

    Editing

    After recording all the footage for a video, it’s time to edit it. I use Kdenlive as my video editor, since it’s both kinds of free (libre and gratis), surprisingly powerful, and it runs on Linux (and Windows), unlike my previous two video editors. For music in my videos I usually use Kevin MacLeod music, since he licenses his music under the open/libre Creative Commons Attribution 3.0 license. I usually export my videos in WebM format using the open VP9 codec, though I hope to start using AV1 in the future once that format is completed and support for it becomes more widespread.

    When making video thumbnails, I use the built-in screenshot function of VLC Media Player to capture frames from my videos, and I use GIMP to edit them and create the thumbnails for my videos. For a series, I just re-use the same project file for the thumbnail of every episode and modify it to use the screenshot, title, and episode number of the one I’m currently working on. I then export the result as a PNG image, and that’s it!

    Conclusion

    Overall, I think my setup has improved from the last time I posted about it. I wish I had a laptop with more graphical power, and I also wish I had proper headphones and a better mic, but in terms of software, I’m quite satisfied with what I’m using right now. I would definitely recommend using OBS, Kdenlive, and GIMP if you’re wanting to do video production. I wish I had been using these tools when I first started making videos.

    For now, that’s all there is to say about the tools I use to make my videos, but after the next 2 years have passed, I’ll probably end up doing another one of these posts, in which case I’ll add a link to it here. I hope this post has been helpful and informative to you!