I've actually just been watching this... a few times.

Raw JSON

{
  "kind": 1,
  "id": "ce69fcfe3f790aa6de7ca9c8dfeff06382e6e0b25f001ddcadc5b5331eefd79c",
  "pubkey": "7c4bd52d032a3cd7ed97d9fcb14aacbbf76a1dc4e797c6cd206838b0d543a3dd",
  "created_at": 1782067638,
  "tags": [
    [
      "alt",
      "A short note: I've actually just been watching this... a few tim..."
    ],
    [
      "e",
      "0e713d2db4026a1b393a8d8d2d756885e1143d8d50440f949d1e86697744ef18",
      "wss://relay.snort.social/",
      "root",
      "314072c16fa9433e1374f62e5b02c8163946ed298a9cde3b1541513c29d19fff"
    ],
    [
      "p",
      "77f56243a824d22573fb755dd52c73c14986d15c0c98512d45f4deb08e9f879a",
      "wss://nostr.mom/"
    ],
    [
      "p",
      "314072c16fa9433e1374f62e5b02c8163946ed298a9cde3b1541513c29d19fff",
      "wss://nostr.wine/"
    ],
    [
      "p",
      "2abbc13897a4218b673db7473f00303f99bed2f70b0d37943a69af92656908de",
      "wss://nos.lol/"
    ],
    [
      "client",
      "Amethyst"
    ]
  ],
  "content": "I've actually just been watching this... a few times.\n\nMy thoughts are unchanged. BIP-110 or Not BIP-110 is a false dichotomy.\n\nI am anti arbitrary-data, but also find BIP-110 highly problematic. A temporary soft fork doesn't work for me because it creates time pressure for a post-110 solution. A good engineer would not sign-off on such a set-up. Another proposal is required, preferably written by fresh people.\n\nJack Kruse overplays his hand in a lot of knowledge areas. I largely agree with nostr:nprofile1qqsz4w7p8zt6ggvtvu7mw3elqqcrlxd76tmskrfhjsaxntujv45s3hsppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7lsfc9m but would kill 110 in favour of a permanent soft fork in mid 2027 that has more concensus.",
  "sig": "eb88618f878a029511f5427b86eeef5834b7d8c4566afe7fd8f6f0f0fc0085be6cd1536deee7a2fd4ebef7208bf571fb4b5a52fa6b26bd8626fa1051660da66e"
}