sbysb
Joined 5 years ago
Karma
101
Submissions
38
Member since
Sep 30
https://bitwizard.dev
https://github.com/sbysb
View on Hacker NewsRecent submissions
Comment · 1 month ago
No, I don't think captchas are a reason people are leaving platforms, at least not in any large number. If the content of a platform is good, the (extremely slight) roadbump for people is not going to deter them.
Keep in mind that for the average person (and even the average techy), they will not even see the captcha, because they have enough tracking them across the web that it will 'autoresolve' them as a human. I only see captcha's nowadays when I am working on web scraping automation or browsing from my VPS.
Comment · 2 months ago
I had another comment in a thread last week about this: https://news.ycombinator.com/item?id=49111625
I really think that using something like Paseo (I use Ouijit[1] because I think it's actually a step ahead of where most of these multiplexers are) and nono[2] is basically the best coverage you can have, and really lets you go crazy with auto mode or permission skipping withiout having to worry about any security concerns.
A lot of people lean into the VMs but realistically it's not actually doing a lot of the security work that you need and leaves you wide open to prompt injection/exfiltration attaacks. The flexibility of a good nono setup (which is easy because they ship a nono skill that claude can consume) actually locks things down significantly better
Comment · 3 months ago
There is a really good video by the author of pi.dev (which I have used to build some of my own harnesses): https://www.youtube.com/watch?v=RjfbvDXpFls
The basis of the argument is that the labs are constantly pushing updates to their system prompts that are used in claude code or codex, which are exceptionally bloated and change the sand beneath your feet with every update.
By rolling your own harness, as long as you keep up with the latest advances and changes in the ecosystem, you capture a lot of the 'control' that LLM-based development feels like it strips from you.
Obvious disclaimer that I use pi.dev when I am aiming for consistency, not absolute quality. Custom harnesses on pi are what I ship, claude code is still my fallback if I need to make sure a PR is the highest absolute quality
Comment · 3 months ago
Oneleet (YC S22) | Multiple Roles | US & NATO Countries | Remote | Full-time
Oneleet is an all-in-one cybersecurity startup that has built its own Attack Surface Monitoring (ASM), Code Scanner, Dependency Management, Endpoint Protection, and Compliance Platform. We recently raised a Series A and are growing at an rapid pace and working on some very exciting projects.
What we're looking for:
- Strong problem solvers who can work independently in a remote environment
- Security-minded professionals passionate about building robust, scalable systems
Tech stack: Go, TypeScript, React, Kubernetes
We have a huge number of roles open across the organization from Engineering (backend, frontend, fullstack, AI, infra) to Operations.
If you're interested in joining our team, please reach out to join<at>oneleet<dot>com with the subject line "HN: <Job Title>" and your resume attached. Alternatively, you can also apply at https://jobs.ashbyhq.com/oneleet
Comment · 3 months ago
> nono is great but you'll still won't be able to run multiple dev servers, dbs or test in the browser...
With our profile setup you can do all three of those things - there is a fresh chrome profile that is blocked against the same network firewall. Claude and Playwright can navigate to the dev stack and screenshot/test it (and non-allowlisted websites are blocked at the network level).
As long as the developer runs the `task start` command outside the sandbox (because docker is blocked), the agent can then interact with it all that they want, and our devs can run 2-3 of these per machine and work on concurrent projects. (based on memory usage / cpu usage)
> a tool to teleport your files, skills, settings, claude/codex subscriptions etc in any of the popular sandboxes
FWIW this is _explicitly_ the opposite of our threat model - everything other than your git credentials that you 'teleport' in (code, settings, Claude/Codex subscription tokens) now lives inside the blast radius, on third-party infra, and a prompt-injected agent in the box can send it anywhere unless you're also egress-filtering. A VM isolates the machine - it doesn't protect the data.
Much easier to keep it all local and refuse any network or file access to anything you don't explicitly approve
Comment · 3 months ago
All git config and hooks are not writable inside the sandbox. This can be somewhat frustrating as you have to run git config commands outside, but the tradeoff is worth it imo. Nono allows for directory level permissioning, so the entire `.git/hooks` directory and `.git/config` / `.git/worktrees/*/config.worktree` are write blocked.
Worth calling out that this doesn't close all of these types of attacks, just the ones that are invisible (claude could very well write ./hack.sh and tie that in to your main.go, but at least it would be a diffable change, instead of invisible like a git hook)
Comment · 3 months ago
Git worktrees are a great isolation boundary for _changes_ (especially making changes in parallel on a single machine), but not behavior. If you are trying to actually run autonomous agents securely you need something that lives outside the harness that actually blocks actions in a way that can't be prompted around.
We use nono [1] for this internally, essentially blocking any actions we don't want agents to be able to do without human approval. Our developers can just run `task claude` or whatever their harness is) and it pre-wraps it with our profile that enforces:
- Filesystem: read/write only the worktree plus dev-tooling dirs (Go, Doppler, Graphite caches, git common dir); explicitly no Docker socket and it can't edit its own Claude settings files (so it can't loosen its own permissions).
- Network: outbound only to an allowlist - Anthropic, Doppler, Go module proxies, our dev environments while still allowing binding local dev-server ports.
- GitHub: read anything in the org, and create/edit PRs and push branches - but it cannot merge, close, review, or comment on PRs, delete branches, touch repo settings/secrets, manage auth, or use raw gh api. Those are all "human-only". GitHub tokens are never exposed to the agent; they're injected by a proxy so it can't read or exfiltrate them.
This is great because it is harness agnostic - any developer can use whatever harness they want as long as they port the nono profile to it, as it will enforce all of the above in a way that is not tied to a specific harness implementation
Comment · 4 months ago
I mean most of these tools pair the notes/transcript with a video recording of the call. It can be super helpful to search the summaries to find the right recording, and then click the line in the transcript to re-watch the meeting.
For work, this is strictly better than not recording the meeting, as it allows for much faster searching, and it is very rarely wrong about the high level topics of a convo. I almost always go "General AI summary search" -> Transcript -> recording when trying to remember a specific item from a call.
That being said the parent article is spot on and I can't imagine someone bringing a recording to a conversation they aren't being paid to have.
Comment · 4 months ago
Oneleet (YC S22) | Multiple Roles | US & NATO Countries | Remote | Full-time
Oneleet is an all-in-one cybersecurity startup that has built its own Attack Surface Monitoring (ASM), Code Scanner, Dependency Management, Endpoint Protection, and Compliance Platform. We recently raised a Series A and are growing at an rapid pace and working on some very exciting projects.
What we're looking for:
- Strong problem solvers who can work independently in a remote environment
- Security-minded professionals passionate about building robust, scalable systems
Tech stack: Go, TypeScript, React, Kubernetes
Open role highlights:
- Application Security Engineer: Help drive the design and implementation of bleeding edge security tooling
- Application Software Engineer: Contribute to an all-in-one cybersecurity agent for devices, including security alerting and mobile device management
- Product Marketing Manager: Build the sales enablement arsenal and thought leadership content that turns technical capabilities into deals won
- We are also hiring across the stack (backend, frontend, fullstack, AI, infra) on the engineering team.
If you're interested in joining our team, please reach out to join<at>oneleet<dot>com with the subject line "HN: <Job Title>" and your resume attached. Alternatively, you can also apply at https://jobs.ashbyhq.com/oneleet
Comment · 4 months ago
I do not think that is the problem with markdown lol. There are lots of problems with markdown, especially vanilla or the more limited versions of it - but really its super power is that it is readable with a regular text editor (or `cat`) and can be rendered without a compilation step.
Markdown is not competing with latex or typst, it is competing with (and has won against) .txt files
Comment · 6 months ago
It's difficult because even if the underlying model is very good, not having a pre-built harness like Claude Code makes it very un-sticky for most devs. Even at equal quality, the friction (or at least perceived friction) is higher than the mainstream models.
Comment · 6 months ago
You should check out Ouijit [1] - I use it regularly for work and it's nice because it focuses on the environment that you want, and just gives you a shell that you can use any tooling in, as well as VM isolation per worktree if needed.
Comment · 6 months ago
https://meza.chat/
Been building an E2EE chat client on the weekends that sits right between Discord (but dis-enshittified) and Matrix (but with good UX around encryption). Still got some rough edges - we are in the second nine of the march of nines in terms of quality.
Comment · 7 months ago
I have used Claude Code in the terminal to the tune of ~20m tokens in the last month and I have very little to complain about. There are definitely quirks that are annoying (as all software has, including vs code or jetbrains IDEs) but broadly speaking it does what it says on the tin ime