Hoop.dev – the only access gateway with packet manipulation | Hacker News Reader

Hoop.dev – the only access gateway with packet manipulation

github.com

20 pointsandriosr9 comments

It's incredibly clever for sure but I feel like it's a massive hack for things like the DB obfuscation feature.

If my access is read-only then it's probably fine but if I have write access and I write back a whole row (my DB tool only updates the changes I think but IDK if every tool works that way) isn't it going to write back the "cleaned"/"hidden" data?

Again, it's very impressive and clever but I just worry I'd blow my foot off by accident.

Thanks for the feedback and kind words! You bring up a valid concern. Let me clarify how it works:

The obfuscation is designed to be intelligent and context-aware. When you have write access and make changes, hoopdev ensures that only the intended modifications are written back, not the obfuscated data. We've implemented safeguards to prevent accidental overwrites with "cleaned" or "hidden" data.

Let me know if you have any specific scenarios or tools you'd like to test with.

I don't think they are communicating the benefit or the purpose in an accessible enough manner.

Appreciate the feedback, would love to get your takes on this description, what are we still missing?

Hoop.dev keeps sensitive data safe and checks important changes to make sure they're done right. It hides sensitive data in databases automatically and turns repeated tasks into easy, automatic ones. It also helps teams fix problems quickly by connecting with chat tools like Slack and MS Teams.

Take it out of the abstract and give me one crystal clear example.

For context, I'm CTO of a gaming startup that uses a Kubernetes cluster to host online multiplayer videogames, and when I read your github and product landing page, I still have no idea who or what this is for. Seems like its targetted for enterprise cloud architects or something. Someone who works on clusters more advanced than ours. Thats fine, but my feedback is simply that I'm no beginner and your landing page basically goes right over my head.

Also, to make people _switch_ from one solution to another, you have to be more than a little bit better, you have to be WAY better. Especially for enterprise clients. To make a enterprise client change their cloud architecture is probably a hard sell, because of the risk involved. Why should anyone attach their professional credibility to your project? I think basically what I'm saying is, you gotta do more to sell this thing.

It sounds technically advanced, but I think you gotta take off your engineer hat and put on your sales hat and make me want it. Or if not me, than make _someone_ want it.

I would love to see a screenshot or visualization of session recordings / audits.

Honestly, why are people so bad at devising two phrases saying who is this for and what problem does it solve?

I don't want to do homework just to know whether this is useful for me. Though it's also probably true that if you have the problem this thing solves you'd recognize it right away. Still, I feel most projects suck at making a proper sales pitch.

This is great feedback, I'll strongly consider updating the description to help people make this decision faster.

Would love to get your feedback on this description, is it clear? what is missing:

It's a small improvement but not nearly enough for me at least, as an outsider.

Admittedly I don't know what an access gateway is. So at the top of the README I'd have something like this:

---

- Hoop.dev is an access gateway, which $insert_what_it_does_here (one phrase or two).

- The API for packet manipulation solves $insert_problem_here.

- Hoop.dev is better than $insert_competition_here by doing (insert your feature list that you already have in the README here).

Reply on news.ycombinator.com