<p>As discussed in <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="407216809" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq/issues/2378" data-hovercard-type="pull_request" data-hovercard-url="/bisq-network/bisq/pull/2378/hovercard" href="https://github.com/bisq-network/bisq/pull/2378">bisq-network/bisq#2378</a>, I have some concerns using the snapcraft store as an official way to distribute Bisq. Essentially it comes down to the following points:</p>
<ol>
<li>
<p>Uncertainty whether locally generated signatures for a snap file (when we prep a release) can still be used to validate once installed via the snapcraft store.</p>
</li>
<li>
<p>Do we want to rely on snap to auto-update Bisq for the user? Aside from concerning issues about data consistency discussed in the snapcraft community when it comes to snap auto-updates (<a href="https://forum.snapcraft.io/t/bug-saves-are-blocked-to-snap-user-data-if-snap-updates-when-it-is-already-running/3226/16" rel="nofollow">https://forum.snapcraft.io/t/bug-saves-are-blocked-to-snap-user-data-if-snap-updates-when-it-is-already-running/3226/16</a>), the more secure method of updating is via the in-app mechanism which downloads and automatically performs signature verification. Also, the user should be able to choose when they want to update rather than snap updating it automatically.</p>
</li>
</ol>
<p>I feel that we need to address those concerns before we can consider this as an official distribution method.</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/proposals/issues/70#issuecomment-461998025">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtjckvRp2XVt-XePrRyrPwHCKkm-dks5vLiAygaJpZM4aMxRm">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZthGNiPTOXNLC2Cm6f-01AhbNUhC6ks5vLiAygaJpZM4aMxRm.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/proposals","title":"bisq-network/proposals","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/proposals"}},"updates":{"snippets":[{"icon":"PERSON","message":"@devinbileck in #70: As discussed in https://github.com/bisq-network/bisq/pull/2378, I have some concerns using the snapcraft store as an official way to distribute Bisq. Essentially it comes down to the following points:\r\n\r\n1. Uncertainty whether locally generated signatures for a snap file (when we prep a release) can still be used to validate once installed via the snapcraft store.\r\n\r\n2. Do we want to rely on snap to auto-update Bisq for the user? Aside from concerning issues about data consistency discussed in the snapcraft community when it comes to snap auto-updates (https://forum.snapcraft.io/t/bug-saves-are-blocked-to-snap-user-data-if-snap-updates-when-it-is-already-running/3226/16), the more secure method of updating is via the in-app mechanism which downloads and automatically performs signature verification. Also, the user should be able to choose when they want to update rather than snap updating it automatically.\r\n\r\nI feel that we need to address those concerns before we can consider this as an official distribution method."}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/proposals/issues/70#issuecomment-461998025"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/proposals/issues/70#issuecomment-461998025",
"url": "https://github.com/bisq-network/proposals/issues/70#issuecomment-461998025",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>