[bisq-network/proposals] Official Snap (#70)

[Devin Bileck]

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:

1. 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.

2. 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.

I feel that we need to address those concerns before we can consider this as an official distribution method.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/70#issuecomment-461998025
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190208/f0341f83/attachment-0001.html>