Re: Finally Bitcoin Devolpers planning to kill Ordinals and Inscription

a) LukeJr is somehow unaware that 42 bytes and 83 bytes are not the same value and he's some sort of putz

or

b) LukeJr knowingly reduced the permitted size of OP_RETURN data in his Bitcoin Knots client (which that pool are using) because he wants to create a hostile environment for non-standard transactions and managed to unwittingly nuke some coinjoin transactions by mistake.

Or this limit existed in Bitcoin Knots for a very long time (maybe from the very beginning) and is not a new thing this implementation of the protocol is enforcing as standard rule. Here is a random oldest version I could find from 8 years ago with the 42 byte limit present:
https://github.com/bitcoinknots/bitcoin/blob/v0.12.1.knots20160629.rc2/src/script/standard.h#L30