vinney on Nostr: Re: privacy, you're saying "trust us". (at the same time as you're on nostr ...
Re: privacy, you're saying "trust us". (at the same time as you're on nostr attempting to appeal to a "don't trust, verify" crowd). I understand the legal and resource reasons why you are doing so, but at the end of the day it's still "trust us, we'll be good".
> the data is not encrypted at rest, so that we can process it for title-generation, length, PDF generation and so on, and so backups and syncs are easy
Why not do that generation on-device and sync encrypted data? Is processing data for "title-generation" and "length" really so resource intensive that it must be done in centralized servers? If so, why not allow users to self-host their own services for providing this computation to themselves? Obsidian Sync works this way - that is, you either sync _encrypted-at-rest_ data with the for a fee, or you provider your own sync service - and I've noticed you guys like to be seen as travelling the same seas as Obsidian.
> the data is not encrypted at rest, so that we can process it for title-generation, length, PDF generation and so on, and so backups and syncs are easy
Why not do that generation on-device and sync encrypted data? Is processing data for "title-generation" and "length" really so resource intensive that it must be done in centralized servers? If so, why not allow users to self-host their own services for providing this computation to themselves? Obsidian Sync works this way - that is, you either sync _encrypted-at-rest_ data with the for a fee, or you provider your own sync service - and I've noticed you guys like to be seen as travelling the same seas as Obsidian.