There was something in there that I missed from last week tho: https://x.com/Rob1Ham/status/1999159393300980193

This article is pretty surface level and clearly not feeling the fork, but it's a quick summary if the state of things re bip 110

Scoresby

As the filter feud rages on, we finally got a release client in-hand to review for Bitcoin Improvement Proposal (BIP) 110, the Reduced Data Softfork that would create a consensus mechanism to scrub arbitrary data on bitcoin such as inscriptions.

Up until now, the filter softfork has seen a lot of mudslinging with little actual code in the wild. Now, we actually have some code to apply to the proposal, and Bitcoin developers are tearing it apart.

bitcoin

> *By Charlie Spears*
>
> As the filter feud rages on, we finally got a release client in-hand to review for Bitcoin Improvement Proposal (BIP) 110, the Reduced Data Softfork that would create a consensus mechanism to scrub arbitrary data on bitcoin such as inscriptions. 
>
> Up until now, the filter softfork has seen a lot of mudslinging with little actual code in the wild. Now, we actually have some code to apply to the proposal, and Bitcoin developers are tearing it apart.
>
> - The reduced Data Temporary Soft Fork (BIP 110) explained
> - Bitcoin developers poke holes in BIP 110 client
> - What’s broken in the BIP 110 client?
> - BIP 110 and the parable of Segwit2x 
>
> **[...read more at blockspace.media](https://blockspace.media/insight/dathon-ohm-releases-bip-110-client-for-uasf-softfork/)**