HNHacker News
TopNewBestAskShowJobs

ADD-SP

28 karma · joined April 4, 2021

submissionscomments
ADD-SP··on Show HN: Open-source AI teammates with their own computer
Maybe all AI assistants need desktop context.
ADD-SP··on Show HN: FrontierHarness Eval – 9 harness, same model, cost per pass varies 17x
Codex is the best harness to me because of its GUI and subscription.
ADD-SP··on Show HN: JSON-Threat-Protection Rust High-Performance Crate
Totally agreed, this is also what I want to say.
ADD-SP··on Show HN: JSON-Threat-Protection Rust High-Performance Crate
This crate is not an alternative of the serde_json, it only do the validation.

Currently, there is no other crates do the sames validation works on JSON, so I have to parse the dataset by a common JSON parser (sede_json) and do the same validation on its deserialized value as the comparable results.

So it would be better to compare to other crates which do the same work, but I didn't found the similar crate so far. And this is also the reason I developed this crate.

ADD-SP··on Show HN: JSON-Threat-Protection Rust High-Performance Crate
Haha, looks like the GitHub Copilot is not good at marketing, I have made it more marketable. Thanks for your pointing out!
ADD-SP··on Show HN: JSON-Threat-Protection Rust High-Performance Crate
Makes sense, numbers added.
ADD-SP··on Show HN: JSON-Threat-Protection Rust High-Performance Crate
Great to see this article, I totally agreed with the view that rejecting any invalid case by designing the right data structure.

Unfortunately, it is hard to achieve it in practice and people even don't realize this, JSON Object is a good example, Human are incline expecting the duplicated key is not allowed in JSON, but it happens.

For this goal, I think the Protobuf is good way to eliminate the possible invalid data for data transportation.

ADD-SP··on Show HN: JSON-Threat-Protection Rust High-Performance Crate
Perhaps checking a service's behavior in response to such JSON is high on the security researcher's list of things to do that are high priority and simple.

"( – ⌓ – )

ADD-SP··on Show HN: JSON-Threat-Protection Rust High-Performance Crate
The JSON RFC (https://datatracker.ietf.org/doc/html/rfc8259#page-6) doesn't require the unique entry name, and also the fact is that many parser uses the last-win strategy like serde_json.

For human, this is invalid, but many web services accepts this kind of JSON consciously or unconsciously.

I'm guessing this may have become a feature of some services and it's hard for maintainers to break this behavior. ᵕ︵ᵕ