
Cipher work traces in early modern letters: A mother to her daughter. One ciphered passage gives discreet advice for a fashionable linen headdress to conceal her daughter’s hair loss. vanishedcomforts.org/2026/04…

History, Scotland

Cipher work traces in early modern letters: A mother to her daughter. One ciphered passage gives discreet advice for a fashionable linen headdress to conceal her daughter’s hair loss. vanishedcomforts.org/2026/04…

Warkworth Castle, Northumberland (England) 'Infoseepage' image & reconstruction showing slots for wooden hoarding that could be dropped (once damaged/set ablaze) on attackers & defence could continue from stone battlements behind. A Percy family stronghold. #WarkworthCastle

Newcastle Town Walls (England) reconstruction. Walls breached and burnt by Scots in 1402 and 1644. With a few raids/skirmishes in-between for good measure! #Newcastle #EnglishCastles #HistoryRebuilt

Garage on the Nethergate, now the site of the DCA Date: October 1993 Ref: IN042-104 CL0761

Play Park by the Alexander Street Multis Image is not dated Ref: DCC-SA2148


Pre-fabricated houses on Montgomerie Crescent Date: c.1965 Ref: GD/X1269-2-3

Invoice issued by Henry Knuck & Co to C Arnot & Sons for 17 bundles of 2nd Hand Riga Mats (a type of Jute mats, possibly used for protection or insulation). The picture is Whitehall Works on Dens Road (just below the Dura Street Junction). Date: 12th November 1930 Ref: GD/X566

Mains Road Date: c.1982 Ref: IN050-151 BW179

Findlater Castle, Aberdeenshire (Scotland) reconstruction mock-up over @TheCastleGuy image. A Gordon family stronghold besieged by Mary Queen of Scots forces in 1562. #FindlaterCastle #ScottishCoastalCastles #HistoryRebuilt

The importance of clothing to social standing and professional success has a long history, dating back to ancient Rome! This week I discuss how Tudors and Stuarts used clothing and jewels to create a royal image they hadn’t really earned.

Walmgate Bar (Walbergate) York. Main gate started in 12th century. Barbican was added in 14th century. Gatehouse burnt by rebels in 1489 and damaged by cannon during 1644 siege. #YorkTownWalls

Eleiven coft in three days! Fae Scenes like these, auld Scotia’s grandeur springs! Tell yer friens the £0.99p bargain offer on Kindle bides till Setterday nicht.
Eicht in twa days! Gaun yersels!

Historic postcard of Millheugh, a much-loved view from a slightly different angle from other postcards we have, showing the great edifice of Broomhill House looming above Morgan Glen... this was sent to Dublin in 1905.

Folks often bad-mouth Brussels, but its medieval town hall is unrivaled.

I am sharing a new paper today with Dario Caldara: “Can Peer Review Survive AI-Generated Text?” sas.upenn.edu/~jesusfv/Peer_… Dario and I, as editors, are increasingly getting papers submitted to our journals that are 99 percent AI-generated. Even worse, we are also receiving many AI-generated referee reports, both as editors and, more frustratingly, as authors. And we cannot emphasize this enough: the real problem is not that the papers and reports were AI-generated; it is that no one had done the thinking behind them, and you can so easily tell. The papers were eminently forgettable, and the referee reports were disappointingly uninsightful. We have seen too many reports of the form: “The paper is well-written and addresses an important problem. However, the authors should consider additional baselines.” This deluge of AI-generated text puts peer review in jeopardy: journals will be flooded with low-quality submissions, economists will decline requests to referee papers or routinely use AI to referee them, and which papers get published will become less and less linked to their quality. We do not want to defend the status quo entirely. Peer review is slow, many reports are poor, and editors (including us!) make bad calls all the time. Still, well-executed peer review remains the best system we have for assessing each other’s work and advancing the profession. AI could improve peer review if used deliberately for that purpose, for instance, to check proofs and code. That is not what we are seeing. The difficulty is that readers, including editors and referees, cannot see how AI was used. As a result, in practice, the burden of verification shifts from the author to the reader. Since we reject this shift, Dario and I did what economists always do when something bothers us: we wrote a paper. So, what do we do in it? First, we check whether AI detectors such as Pangram get this right: is a referee report flagged as AI-generated indeed AI-generated? Or is Pangram just flagging proofreading and editing? No. We run an experiment with 25 referee reports from the pre-AI era. Proofreading and editing do not trigger AI-generated flags. Only when we ask the LLMs to substantially rewrite the referee report or to generate a new report do we get the AI-generated flags. Pretty compelling evidence, if I may say so. Second, we build a theoretical model to explore who should bear the burden of verification: the author or the reader? (Yours truly always enjoyed the courses on the rules of evidence in law school; yes, as Billy Wilder would say, nobody is perfect.) The answer is that it is much more efficient for the author to do it, because the author can verify at a much lower cost and only needs to do it once (rather than each reader repeatedly). Before AI, the authors more or less had to verify the results, even if only because they had to type them in. This was not perfect (and all papers ever published in economics probably have at least one mistake). But the problem is that, with AI, the author does not even need to read the text. Or can just skim it. Writing is thinking, and without writing there is usually not much thinking. So, a paper flagged as AI-generated is prima facie evidence that the author has not verified it. Should this lead to an automatic rejection? No. But there should be a zero-tolerance policy for serious mistakes. The first serious mistake we find in the paper, and it is out! In comparison, for a non-flagged paper, a serious mistake is something that the editor might determine it can be fixed in a revision. We are stricter with referee reports. There is absolutely no point in the referee generating a report using an LLM. As an editor, I can do that directly and save myself the trouble of asking you for it. Now, of course, you can use the LLM to help you with the report (if the journal allows it! Many journals do not allow you to upload the paper to an LLM, and you need to follow the rules). For example, you can use the LLM to search for existing results in the literature. But peer review is not about finding one sentence that is not entirely precise or a slightly sloppy mathematical proof. Referees are asked: “Is this idea important despite its flaws?” And, relatedly: “Is the paper a good fit for the journal in terms of quality and focus?” That judgment is the task for which you are selected as a subject expert. We also propose that journals require that, before a paper is submitted, the author submit it to an LLM using an approved prompt and include the LLM report and a discussion of what was and was not fixed. That way, the referee would not need to check (or at least not check so carefully) every technical detail, and they could focus on the big picture: Is this a good paper? Is this a good fit for this journal? What is fundamental for this paper to become publishable at this journal? Anyway. The paper has many other arguments, and we try to be nuanced. So, before ferociously typing the first complaint that crosses your mind, would you consider reading it? Chances are that we have already discussed your objection. We have been thinking about this for a long time. But by all means, leave good comments!