_zer0c00l_

3 ms·

1.
by _zer0c00l_ 6mo ago
what problem is this helper trying to solve?
2.
by _zer0c00l_ 6mo ago
I have one (at least) fundamental concern about the approach - let's say I'm building an anti-fraud system that uses AI (through API), and maybe I'm asking AI whether my user totally+fraud@gmail.com is a potential fraudster.
3.
by _zer0c00l_ 6mo ago
I love the design, it's really cool. Do you have data that supports your hypothesis that users care about "their files leaving their computers"?
4.
Show HN: We're rebuilding Google, YouTube and 3 more giant apps with vibe coding(rebuildtheinternet.com)
1 points by _zer0c00l_ 6mo ago|0 comments
5.
by _zer0c00l_ 6mo ago
There is one potential issue with scanning the entire codebase IMHO - if the codebase is old enough, there can be old snippets of code that DON'T correspond to the current preferences anymore. So scanning the last 200 PRs and reading c
6.
by _zer0c00l_ 6mo ago
You can do this with OpenRouter though, can't you? They have a markup which is annoying, but they also have a long list of LLMs
7.
by _zer0c00l_ 6mo ago
Your example is with Codex - OpenAI could implement this easily on their end right? Every prompt of yours was an API call and they have a log, they can easily re-create a quick history of what you did/asked for before?
8.
by _zer0c00l_ 6mo ago
how does this scale - what if you have 50 Linux instances? the screenshot only has 3 or 4 so that looks good
9.
by _zer0c00l_ 6mo ago
I think CodeRabbit/others do this already? They learn from your code base/previous PRs, then use that in the future. I built a mini PoC of this a few weeks ago as well, out of curiosity