{"version":"2.1.280","anchor":"isverified-flag-threaded-through-for-unverified-content-bloc","canonical_anchor":"isverified-flag-threaded-through-for-unverified-content-bloc","heading":"isVerified flag threaded through for unverified content blocks","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/isverified-flag-threaded-through-for-unverified-content-bloc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### isVerified flag threaded through for unverified content blocks\n\nContent blocks can now be marked as unverified via a new isVerified flag\n\n**Unclear.** It's unclear what kind of content this applies to or how an unverified flag is shown to the user.\n\n**What**\n\nA rendering or content-handling path now sets `isVerified: false` when a fourth captured field in the underlying data equals the string \"false\", alongside the existing color and summary handling.\n\n**Why**\n\nThis suggests some content blocks can now be flagged as unverified, but the finding doesn't say what unverified content looks like to the user or what triggers it.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}