Browser can scroll and handle scrolling well. Let them do it.
Show HN: Working on a Zero-Knowledge Daily Journaling App
51–60 of 112 posts
Re: Show HN: Working on a Zero-Knowledge Daily Journaling App
#52I've worked on 2 "zero-knowledge" apps (basically meaning all data is encrypted/decrypted on the client) and I would advise against it: * most consumers have no idea what you're talking about / don't care * 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 continu…
Your logic that the app could deploy a "rogue update" so it has little merit would essentially say there is no point in mitigating anything because insert unlikely failure case.
When saying it causes people to trust you less by raising the spectre I disagree. I would assume that a company focused on zero knowledge would also pay attention to other mitigations and related best practices.
Agree with the downsides.
Re: Show HN: Working on a Zero-Knowledge Daily Journaling App
#53I've worked on 2 "zero-knowledge" apps (basically meaning all data is encrypted/decrypted on the client) and I would advise against it: * most consumers have no idea what you're talking about / don't care * 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 continu…
While this is very well put, isn't this like saying "people could jump over the safety rail. So there is no point having it". Your logic that the app could deploy a "rogue update" so it has little merit would essentially say there is no point in mitigating anything because insert unlikely failure case . When saying it causes people to trust you less by raising the spectre I disagree. I would assume that a company foc…
In a classic setup, the client needs to trust that the service provider is not malicious or incompetent either.
The level of trust thats required for a zero-knowledge setup is not fundamentally different from that of a classic setup. Most importantly, the amount of trust required is substantially greater than zero.
Re: Show HN: Working on a Zero-Knowledge Daily Journaling App
#54I noticed you accept bitcoin, will you accept Monero as well?
Re: Show HN: Working on a Zero-Knowledge Daily Journaling App
#55Just do it offline, there's your zero-knowledge.
Re: Show HN: Working on a Zero-Knowledge Daily Journaling App
#56I'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.
1/ what do you feel like you've learned or gained from this? 2/ do you ever go back and study what you wrote or is it more about giving your thoughts clarity today?
It's one of the things I'm most grateful of doing for so long.
Re: Show HN: Working on a Zero-Knowledge Daily Journaling App
#57I've worked on 2 "zero-knowledge" apps (basically meaning all data is encrypted/decrypted on the client) and I would advise against it: * most consumers have no idea what you're talking about / don't care * 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 continu…
Re: Show HN: Working on a Zero-Knowledge Daily Journaling App
#58I've worked on 2 "zero-knowledge" apps (basically meaning all data is encrypted/decrypted on the client) and I would advise against it: * most consumers have no idea what you're talking about / don't care * 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 continu…
This is why I like decentralized apps where you can use a content-addressed frontend that is just pinned to a specific version. I can choose to update to the next major version if I want to.