{"version":"2.1.267","anchor":"attribution-source-can-now-be-owner-in-addition-to-typedr","canonical_anchor":"attribution-source-can-now-be-owner-in-addition-to-typedr","heading":"Attribution source can now be 'owner' in addition to typed\/relay","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/attribution-source-can-now-be-owner-in-addition-to-typedr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Attribution source can now be 'owner' in addition to typed\/relay\n\nMessage attribution now recognizes 'owner' as a source, alongside typed and relay\n\n**What**\n\nThe code that determines who or what sent a message previously recognized `typed` and `relay` as attribution sources, collapsing anything else to \"unattributed.\" It now also recognizes an `owner` source value and passes it through instead of discarding it, with corresponding new cases added to related switch statements.\n\n**Why**\n\nMessages attributed to an owner are now tracked distinctly instead of being lumped in as unattributed, giving more accurate accounting of where a message came from.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}