durkes

5 ms·

1.
by durkes 4y ago
Example config: const domainToPort = { 'localhost:3000': 3001, 'example.com': 3002, 'api.example.com': 3003, };
2.
by durkes 4y ago
I wonder if you remind it with those instructions with each prompt, if that would help? Also, I'm curious, approx how much does it cost for each small app build / iteration?
3.
by durkes 4y ago
This is really cool. I had a lot of fun building a hangman style game just now! It took 3 prompts to get it right... here was my third iteration (sorry, didn't save the first two): There is a problem where player 1 is unable to enter t
4.
Show HN: Simple reverse proxy router in Node.js for multi tenant server(github.com)
1 points by durkes 4y ago|1 comments
5.
by durkes 4y ago
It seems risky to be storing sensitive information including passwords. How are you protecting this data?
6.
by durkes 4y ago
This worked for me. Thanks!
7.
by durkes 4y ago
Somewhat off topic, but I'm getting a lot of network errors lately. Has anyone else noticed an increase? I'm also curious if any Plus users here can share their experience...
8.
by durkes 4y ago
Cool and fun app! Without knowing much about the GPT3 API, I'm curious if you had to provide training data for each character, or if it's simply a setting on the API
9.
by durkes 4y ago
There isn't any exponential backoff built-in, just the 500ms timeout in between fails. You can, however, set the number of retries to something you want your app to tolerate and then if it still fails, handle the error accordingly to p
10.
by durkes 4y ago
It's coded to retry connecting every 500ms. Usually the connection will have to timeout first, so it takes longer for each retry. I set my retries to Infinity. Messages that the client publishes while trying to connect are pending also
11.
by durkes 4y ago
I appreciate that. I used redis in the past, but wanted a node-only solution to keep things simple.
12.
Show HN: Simple pub/sub using WebSockets in Node.js(npmjs.com)
13 points by durkes 4y ago|6 comments