Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It’s essentially an API testing tool. It is mostly used to poke endpoints on a development server and sometimes to learn the output patterns of a public API, what security concerns are there in stripping the UI?


It's less about the actual changes made and more that one person is maintaining a branch that diverges (significantly?) from upstream, on a project that is fast-paced and constantly under attack. If I'm using this tool to run tests on the network, and I'm several patches of Chromium behind, that makes me vulnerable.

That tradeoff can be worth it, but all I'm getting out of it here is reduced application footprint? I'd rather use the bloated tools or wait for someone with deeper pockets to make a less bloated tool. Or a similarly small project that writes it natively.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: