<p><a class="user-mention" data-hovercard-user-id="39171116" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/Anderskargaard">@Anderskargaard</a>, I think when it comes to "delivered" work, the "YouTube exposure"<br>
and "Meetup related" items above are reasonable, because they are events that happened in the real world for the benefit of users.</p>
<p>I wouldn't call the "Bisq internal" items delivered work, though. Conversations in Slack aren't worth anything to users if they don't manifest in some delivered software or service or other material benefit to the network. In the SEO conversations we essentially decided on the status quo, i.e. non-action. So I think there's nothing <em>delivered</em> to be claimed here. It's important to clearly distinguish delivery in this way, because we must avoid accidentally incentivizing internal chatter. Every conversation we have is a cost, not a delivered good. Ideally, we would deliver non-stop valuable improvements to the network with zero conversations required to do so, right?</p>
<p>What I do think is of value to the network, though, is conversations like this one where we figure this stuff out. Thanks.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/compensation/issues/81#issuecomment-402217773">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtp7Uy7hWVPlri3ax17X_C8WgQdlHks5uC5ywgaJpZM4UXape">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtjU00TfaJEmuSPH1GlqB75nfD3v0ks5uC5ywgaJpZM4UXape.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/compensation","title":"bisq-network/compensation","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/compensation"}},"updates":{"snippets":[{"icon":"PERSON","message":"@cbeams in #81: @Anderskargaard, I think when it comes to \"delivered\" work, the \"YouTube exposure\"\r\nand \"Meetup related\" items above are reasonable, because they are events that happened in the real world for the benefit of users.\r\n\r\nI wouldn't call the \"Bisq internal\" items delivered work, though. Conversations in Slack aren't worth anything to users if they don't manifest in some delivered software or service or other material benefit to the network. In the SEO conversations we essentially decided on the status quo, i.e. non-action. So I think there's nothing _delivered_ to be claimed here. It's important to clearly distinguish delivery in this way, because we must avoid accidentally incentivizing internal chatter. Every conversation we have is a cost, not a delivered good. Ideally, we would deliver non-stop valuable improvements to the network with zero conversations required to do so, right?\r\n\r\nWhat I do think is of value to the network, though, is conversations like this one where we figure this stuff out. Thanks."}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/compensation/issues/81#issuecomment-402217773"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/compensation/issues/81#issuecomment-402217773",
"url": "https://github.com/bisq-network/compensation/issues/81#issuecomment-402217773",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
},
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [bisq-network/compensation] For May - June (#81)",
"sections": [
{
"text": "",
"activityTitle": "**Chris Beams**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@cbeams",
"facts": [