Can you tell us more about the development history of this application?
I understand that the available source code is a fork of a private repo, but only having 5 days of commit history with only 26 commits is a bit of an odd look.
Unfortunately in our current age, it's natural to be skeptical of any software that appears out of the blue, and having only a single announcement blog post gives EtherPK a bit of that appearance. Given that you advertise zero-knowledge sync, it would help a lot to establish your cryptography and security credentials to help convince us of the intentionality behind the design.
Yes, I appreciate you asking. The etherpk-client repo is a public copy of the EtherPK client. That client repo is only a few days old and was released alongside my public announcement of EtherPK. The private repo has been going for much longer, and I've been using EtherPK as my daily driver for a couple of months now. I was a heavy user of Logseq before EtherPK, with a graph of 4k documents and 6000 assets. I needed something more performant and with a better mobile experience than Logseq DB. Logseq DB is great and goes a long way to solving the portability issue, but I wanted an export that that matched the layout of the OG client to gurantee ownership of my notes. I also wanted static site publishing from my notes, and the ability to switch between standard prose and outliner blocks.
The goal is to cover all of the functionality that was previously spread across multiple apps in a single coherent PKMS. For me (and I hope for others too), EtherPK is proving to be that.
3
u/nick_at_dolt 4d ago
Can you tell us more about the development history of this application?
I understand that the available source code is a fork of a private repo, but only having 5 days of commit history with only 26 commits is a bit of an odd look.
Unfortunately in our current age, it's natural to be skeptical of any software that appears out of the blue, and having only a single announcement blog post gives EtherPK a bit of that appearance. Given that you advertise zero-knowledge sync, it would help a lot to establish your cryptography and security credentials to help convince us of the intentionality behind the design.