Decryption key derived from master password never leaves the browser. It's just a text editor so far, but a we have a few features planned: retrospective tooling, sentiment analysis, journaling modules, guidance and information inline, better habit formation & rewards UI.
I've worked on 2 "zero-knowledge" apps (basically meaning all data is encrypted/decrypted on the client) and I would advise against it:<p>* most consumers have no idea what you're talking about / don't care<p>* those who know what "zero trust" is, also know that it's not really trustless. You do have to trust the company that it will never send the password or plaintext data back to the server. Checking this on a continuous basis is essentially impossible, a rogue update can be pushed anytime. The amount of trust you need to put into the company is not dramatically different from a normal setup. I think psychologically it's also a bit self-defeating - promoting zero-trust aspect somehow suggests that customers shouldn't trust you.<p>* the design is a major pain, since you never know what surprises await you in the customer's data (data tends to rot). Data migration to a newer version is a pain since you can migrate only when the user logs in, which can be years later (in effect you need to keep backwards compatibility forever). Debugging such customer migration problems blindly is hell.<p>* there will be useful features which you won't be able to implement without violating the zero knowledge principle. Chances are that many users would place a higher value on those features rather than on the zero knowledge aspect.<p>If you really want to decrypt/encrypt on the client, then try to minimize them - no encrypted structures, just encrypted text / images / whatever payload. Metadata, keys etc. can remain plaintext and thus accessible for your maintenance needs.
I've been journaling for about 15 years now. The big key to getting consistent at it was to stop worrying about trying to write a lot, or trying to write something insightful, and just write a sentence or two at a minimum. Often, that turns into more or into something insightful.
Can't find any info about journal encryption on the website itself. Perhaps there should be a page dedicated to explaining how your data is protected. Otherwise great stuff!
It feels like the Venn diagram of 1) people who know what "Zero Knowledge" is and 2) would be willing to create an account on a web service to store their writing… would look like two circles that don't touch.<p>I wonder if this would do better as an open source native mobile app?
On desktop, I can only scroll the middle section of the site. If I hover anywhere on the side margin and try to scroll, nothing happens. (Firefox, macOS)
If I can offer some unsolicited feedback:<p><pre><code> - This space is very crowded - to consider this app, I need to know a differentiator much sooner. Is it the streak? Is it the zero-knowledge? What makes this different from the 20 other options? It seems like the value prop here is "this is a simple journal that tracks whether you wrote today or not, and that is zero knowledge." If there's more, it's missing from the marketing here.
- There's some confusion in the branding. You're using the word "guru", as well as the word "jumble" as a verb. Pick a tagline and a CTA, and stick to those.
- I like the point you are trying to make about the value of writing itself... but how does your app take advantage of that value prop? Can I capture those insights in a unique way? Otherwise, I can take your value prop and accomplish it in the writing app I already have an account and history with.
</code></pre>
I think you're on the way to something good here, but it's a little too confusing to get me to convert.
For the love of anything, please stop messing with the scrollbar. Not only (as two others mentioned) does scrolling only work on part of the screen, it also moves at a completely different speed than what I have set up, and hides the scrollbar.<p>Browser can scroll and handle scrolling well. Let them do it.
Looks nice! I have been using empty git commit messages for journaling in the past few months and found that I'm more willing to journal in the command line with this git-abuse than most applications specifically designed for journaling. Don't know if anyone else has tried this
In case anyone wonders, the illustrations are done by <a href="https://absurd.design/" rel="nofollow">https://absurd.design/</a>
Shameless plug for my own password protected daily journal app where all your data stays on your device!<p>Built it late last year to build the habit of writing out my thoughts.<p>* iOS: <a href="https://apps.apple.com/us/app/a-journal-a-day/id1659288235" rel="nofollow">https://apps.apple.com/us/app/a-journal-a-day/id1659288235</a>
* Android: <a href="https://play.google.com/store/apps/details?id=com.georgejose.journal">https://play.google.com/store/apps/details?id=com.georgejose...</a>
> "A good writer doesn't just think, and then write down what they thought, as a sort of transcript. A good writer will almost always discover new things in the process of writing. And there is, as far as I know, no substitute for this kind of discovery." -Paul Graham<p>What is it about writing that makes it different than thinking?
On a marketing tangent, I wish the security practitioners had names better than "zero-knowledge" and "trustless". To an average person, they really make the system sound dumb and dubious despite them being beneficial.<p>Curious what alternative names people have?
I dont actually think this product is finished. It has a buggy interface, specifically the tag and search for tag functions don't seem to work from my Macintosh 12.0.1 (Monterey) using Chrome (Version 109.0.5414.119 (Official Build) (x86_64))