I love how wholesome the comments are, probably the most wholesome thread about startups I've ever seen. congrats :)

Your API key is only stored client-side, on the server-side only a hash of it is stored. Your entire chat history is encrypted/decrypted on the client-side so there is no way someone else can read your history.

It's an Open Source project, if you want you can host it yourself. https://github.com/aminmarashi/gpt-api-companion/tree/main/c... I'll add a Github badge to build some trust.

Edit: you can read more in this page https://chat.lit.codes/privacy-and-security

It already mentions the GitHub repo, so I'm not adding the badge.

Came here to say this. It's unfortunately not a new problem. I use Shadow Tech on my M1 Macbook to play windows games, and this has been bugging me ever since. The irony is that this problem is non-existent on old Macbook pros.

Here's an example of SOF solution: https://apple.stackexchange.com/a/413735

But if you search around the internet you will see different solutions proposed for it, none worked for me except for this script.

This popping up on HN gives me hope that next versions give you at least a tool to disable Wifi direct.

> Can chatgpt replace software developer's job?

It is unlikely that chatbots or large language models like GPT-3 could replace the job of a software developer. While they may be able to assist with certain tasks, such as providing suggestions or generating code based on user input, they are not capable of the complex problem-solving and critical thinking required for software development. Additionally, chatbots and language models do not have the ability to learn and adapt to new situations like a human software developer can. Therefore, it is unlikely that chatbots or GPT-3 could replace the role of a software developer.

---

P.S. It may be stealing part of my job, but it's the part that I don't enjoy doing anyway.

People said a lot of the same things about blockchain (and bitcoin) a couple of years ago. The world has changed in many ways since then, just not in the way they predicted.

> Containers at near-native speeds

Wow, I'm dying to see how it works!

> brew install qemu

:|

It looks nice in code, but it's a hell to debug.

Yep, debugging Ramda code is terrible experience.

We maintain a service which is making heavy use of Ramda. It seemed like the right tool for the job, because the service is mostly doing data transformation, and the code ends up "clean" and terse. However, we found that onboarding people who are not familiar with FP is time consuming and often people outright refused to learn it. We decided to ditch Ramda, rewrite the service in vanilla JS, prefering immutability where possible. We're about halfway done and it was definitely the right decision. Sure, `R.mapObjIndexed(doSomething, someObject)` is simpler compared to `Object.fromEntries(Object.entries(someObject).map(doSomething))` and now there's a ton of multi-level object spreads, but at least it's simple enough to understand for anyone familiar with JS.

We also came up with a `pipe` function that handles Promises. It makes chaining (async) functions very convenient:

const pipe = (...functions) => (input) => functions.reduce((chain, currentFunction) => chain.then(currentFunction), Promise.resolve(input));

Nothing wrong with getting some help from automation though. It makes things more effective, so if you want to keep relationship with friends/family then you will get that, if you don't want that person to be in your reminders, just remove them. It helps keeping your mind free for other stuff.

I highly recommend the book "Kill It with Fire" by Marianne Bellotti

Thanks for sharing. The only actual useful thing I got from this post.