to the end of , so their fixed seat is the screen itself on every browser, never a wrapped container. */ .reader-stand{width:64px;height:64px;flex:0 0 auto;pointer-events:none;filter:drop-shadow(0 2px 6px rgba(0,0,0,.45))} .reader-stand svg{width:100%;height:100%;display:block} .reader-stand.stand-r{transform:scaleX(-1)} /* READER FOOT ROW (owner, Nov 13, 2026): one fixed row at the foot of the screen -- lamp, the wide green reading bar, lamp -- the lamps the bar's height and its bookends, inset from the corners; the QS script seats the three into this row, and the spacer keeps the chapter's last words clear of the row. The row's parts share ONE bottom line (owner, Nov 14, 2026, pointing at this box and the lamps in his Matthew 19 screenshot: "I want this box and lamps to stay at the bottom of the page"): the lamps' feet and the box's foot stand on the same bottom edge at every box height -- align-items:flex-end, never a lamp floated at the tall box's middle. PERMANENTLY AFFIXED (owner, Nov 15, 2026, over his 1 Samuel 1 screenshot: "they need to be seated at the bottom of the page. permanently affixed"): the row stands flush on the bottom edge (bottom:0), the lamps a little bigger (64px), the tracker box smaller (tighter padding, 13.5px type in src/reading.js), and seatFootRow runs before the toolbar guard so the unit is affixed even on a page whose toolbar fails to stand. LAMPS FLANK THE BOX, WHOLE AT THE BOTTOM (owner, Nov 15, 2026, over his 1 Samuel 1 phone screenshot: "Fix the lamps -- to the bottom of the page"): the old row stretched the full screen width with space-between, which flung the lamps to the extreme corners, detached from the box and clipped by the phone's bottom edge/nav area. The row is now capped at 356px and centred: the tracker box flex-fills between the lamps inside that cap, so on any screen wider than the cap the whole unit -- lamp, box, lamp -- stands together in the middle of the bottom edge, inset from the corners, instead of stretching corner to corner; and padding-bottom:env(safe-area-inset- bottom) lifts the unit clear of the phone's nav/gesture area so no lamp is clipped at the bottom. The narrower box stands a little taller, so the footspace rises 150px -> 170px to keep the last verse clear. Lamps whole, feet on the same bottom line as the box, on every reader page. SLIM + FLUSH (owner, Nov 15, 2026, over the live page: "I dont like the size of the green box" -- picked slim, one short line with just the verse count -- "and the fact that the lamps are not at the bottom"): (1) the tracker box is slimmed to ONE line in src/reading.js (verse count only; the explanatory paragraph is gone from the box -- the tracking itself is untouched), so the row now stands at the lamps' own 64px height; (2) the safe-area padding is REMOVED from this rule. That padding sat INSIDE the row: bottom:0 anchors the row's outer edge to the screen edge, so wherever a phone reports a nav/gesture inset (the owner's Samsung does), the env() term held the lamps' feet exactly that many px ABOVE the bottom edge. With the term gone, bottom:0 alone seats the unit flush -- lamp feet on the bottom edge of the screen, no gap beneath, on every device. The footspace is re-proved at the slim height: 170px -> 84px (64px unit + 20px of air) and the last verse still clears the unit at max scroll. */ .reader-footrow{position:fixed;left:50%;transform:translateX(-50%);bottom:0;width:min(356px,calc(100% - 12px));display:flex;align-items:flex-end;justify-content:center;gap:10px;z-index:940;pointer-events:none} .reader-footrow>.rd-track{margin:0;flex:1 1 auto} .reader-footspace{height:84px} .reader-stand.unlit svg{filter:brightness(.93) saturate(.96)} .reader-stand .cflame{opacity:0;transition:opacity .6s ease} .reader-stand .cflame.on{opacity:1} .reader-stand .cwash{opacity:0;transition:opacity .6s ease} .reader-stand[data-lit="1"] .cwash{opacity:.41} .reader-stand[data-lit="2"] .cwash{opacity:.46} .reader-stand[data-lit="3"] .cwash{opacity:.52} .reader-stand[data-lit="4"] .cwash{opacity:.58} .reader-stand[data-lit="5"] .cwash{opacity:.63} .reader-stand[data-lit="6"] .cwash{opacity:.69} .reader-stand[data-lit="7"] .cwash{opacity:.75} /* the small floating reading box is removed (owner, Nov 13, 2026) -- the wide green bar in the foot row is the single notice */ body.reader-fs main::after{content:"";display:block;height:196px} body[data-reader-bg="pulpit-cream"] .reader-stand,body[data-reader-bg="scroll-paper"] .reader-stand,body[data-reader-bg="torn-scroll"] .reader-stand,body[data-reader-bg="cave-stone"] .reader-stand,body[data-reader-bg="sackcloth"] .reader-stand,body[data-reader-bg="torn-edge-scroll"] .reader-stand,body[data-reader-bg="scroll-on-wooden-rollers"] .reader-stand,body[data-reader-bg="aged-papyrus"] .reader-stand,body[data-reader-bg="pale-vellum"] .reader-stand,body[data-reader-bg="desert-parchment"] .reader-stand,body[data-reader-bg="candlelit-parchment"] .reader-stand,body[data-reader-bg="burnt-edge-scroll"] .reader-stand,body[data-reader-bg="ruled-cream-scroll"] .reader-stand,body[data-reader-bg="honey-aged-scroll"] .reader-stand,body[data-reader-bg="grey-weathered-scroll"] .reader-stand,body[data-reader-bg="scroll-over-dark-wood"] .reader-stand,body[data-reader-bg="stone-and-scroll"] .reader-stand,body[data-reader-bg="leather-and-parchment"] .reader-stand,body[data-reader-bg="side-roller-scroll"] .reader-stand{filter:sepia(.16) brightness(.96) drop-shadow(0 2px 5px rgba(60,35,0,.35))}
Bible Characters & Character Studies

Gog

First appears at 1 Chronicles 5:4

← All characters in order

First named in Scripture at 1 Chronicles 5:4 — read the chapter.

From Easton’s Bible Dictionary (1897)

(1.) A Reubenite (1 Chronicles 5:4), the father of Shimei. (2.) The name of the leader of the hostile party described in Ezekiel 38,39, as coming from the “north country” and assailing the people of Israel to their own destruction. This prophecy has been regarded as fulfilled in the conflicts of the Maccabees with Antiochus, the invasion and overthrow of the Chaldeans, and the temporary successes and destined overthrow of the Turks. But “all these interpretations are unsatisfactory and inadequate. The vision respecting Gog and Magog in the Apocalypse (Revelation 20:8) is in substance a reannouncement of this prophecy of Ezekiel. But while Ezekiel contemplates the great conflict in a more general light as what was certainly to be connected with the times of the Messiah, and should come then to its last decisive issues, John, on the other hand, writing from the commencement of the Messiah’s times, describes there the last struggles and victories of the cause of Christ. In both cases al ik e the vision describes the final workings of the world’s evil and its results in connection with the kingdom of God, only the starting-point is placed further in advance in the one case than in the other.” It has been supposed to be the name of a district in the wild north-east steppes of Central Asia, north of the Hindu-Kush, now a part of Turkestan, a region about 2,000 miles north-east of Nineveh.

← ShimriJaanai →

Reading photograph: “Colosseum in Rome, Italy - April 2007” — the Colosseum at dusk — by Diliff, CC BY-SA 2.5, via Wikimedia Commons — resized.