tony_codes

I just deployed a fix for this; if you see this and happen to check let me know if it's better :)

Sorry for that; I'm a backend engineer; still learning some of the frontend best practices. I just deployed a fix for this; if you see this and happen to check let me know if it's better :)

just deployed a fix for this; if you see this and happen to check let me know if it's better :)

just deployed a fix for this; if you see this and happen to check let me know if it's better :)

one benefit of online is privacy. I've talked to many people that really don't like having a physical journal laying around with personal information that a partner might read. But yeah, I get there are workaround to that problem and not everyone has this kind of privacy issue

It would go the SAAS route if enough people find it useful; if there are consistent users I can't afford to make it free forever unfortunately

Thanks a lot, this is really useful feedback. I completely agree the landing page branding needs some work. I've recently done some workshops to get some clarity on target audience and will try to tighten this up.

Currently the app is light on features so indeed it does not differentiate well, but we will build out a retrospective flow which is unique and helps users find actionable insights from past entries, and explore their best ideas on specific topics over time.

Just bitcoin for us :)

1/ For me it's similar to meditation in terms of the appeal. It's a way to slow down and think, not necessarily for measurable gain but to be a bit more present in the flow of things. I've learned a lot about myself as I do a lot of introspection when writing. 2/ Yes, a major feature I'd like to build is a retrospective flow as I've developed a pretty nice system for going back and pulling out "nuggets" from past entries. Seeing your own thoughts after some time, as a stranger is a really useful tool to understand how your mind works.

thank you! It's an SPA build with React

probably not in the near term, I want to make the webapp work well on mobile and encourage users to employ a keyboard when journaling

Interesting, haven't heard this approach before.

Thanks for the advice, yeah I'd like to add guided journaling modules and some optional prompts. Just knowing where to get started helps a lot with journaling

some users hesitate to journal due to privacy concerns

ah yes, thanks for posting that

Built with serverless tools on the backend. AWS Lambda, dynamo, S3. ReactJs SPA for frontend.

The main thing is that the encryption keys never leave the browser. So even an engineer in control of the backend cannot see the information being saved. With E2E encryption the owner of the data usually also handles the decryption keys.

interesting; I benefited from the opposite, which was having a goal of filling one page. This acted as a sort of reward and feeling of accomplishment. But also found any expectations on quality tend to deter me.

yes agree, thanks! The white paper is here https://docs.google.com/document/d/1T0SEj5WrymfyzNDD8rNGKQ2O... need to add to landing page

I agree with the pain points you've highlighted -- but I think certain applications do benefit from zero-knowledge. Password managers for example. In the case of journaling, I think one reason people resist is fear of exposure. I agree though, the challenge is communicating the added security to non-technical users.

True users must trust the developers to not make a rogue update, but in practice I think it works fine. We also trust library dependencies to not push a rogue minor update that will crash our site or do something malicious.

Is Azure truly locked out from access to the decryption keys and access the unencrypted data (whilst being run against a model)? I followed the link but didn't find these details regarding their security model

I did not have in mind a way to keep data on the customer premise, it's more about a verifiable zero-knowledge architecture so the data never leaves unencrypted, and the decryption keys never leave the secure enclave which decrypts the data and runs the model on the data. This kind of secure enclave is exactly what AWS Nitro is designed to do, but it runs in the cloud, so the data is off premise.

thanks a lot!

that sounds difficult. Is it possible? Once the customer has access to the data, how can you guarantee they don't copy it?

interesting, how did you end up implementing this?

exactly as any existing API, it's just that you would encrypt the prompt with the API public key before querying the API; since it's running in a secure enclave environment, it is highly secure. My idea is that this could be interesting for applications that are sensitive but would benefit from AI features. For example, providing sentiment analysis for a journaling application (private journal entries)

Great article. Buidling a chess engine is an awesome way to level up as a software developer! https://blog.devgenius.io/level-up-as-a-software-engineer-by...

I wrote a guide that may help -- it enables gdb debugging within consistent containerised environment: https://blog.devgenius.io/getting-started-writing-assembly-l...

This guide provides a dockerized dev environment that works well with GDB and provides some Assembly Language basics for getting started.

Maybe people here find it interesting. I'm in the process of a guide on writing x86-64 with Docker with ability to write in VS Code and debug within a docker container -- https://medium.com/@tony.oreglia/getting-started-writing-ass...