Requests, Please | Hacker News Reader

Requests, Please

morronel.github.io

76 pointssysoleg20 comments

This is pretty cool, but at the same time i'm horrified that somebody might walk away thinking you need to deny these requests to protect against XSS or SQL injection.

Maybe i want to sell coffee mugs with `<img src=x onerror=alert(document.domain)>` on them.

Parse, dont validate. (And never interpret what shouldn't be)

Though in this case, it would be: escape, don't sanitize. "Parse, don't validate" applies to taking inputs; this is about generating outputs (like SQL queries or HTML markup).

Yes, I believe the term is "output encoding"

This is a ton of fun! Small suggestions:

    - A way to copy (or better yet, email) a session link so I can switch between devices while maintaining my progress
    - Allow 1 and 2 to function as hotkeys for Allow and Block, so I don't have to move between "a" and "b" for Allow and Block, and then the number keys for the block reason

Oh, also, change “Uptime” to “Availability”

I made a similar thing, but you are the LLM

https://avneeshk.me/you-are-the-model/

I enjoyed this!

Seems like a lot of people did. My free cloudflare limit ran out lol, it'll be a couple hours before it resets

So, it's "Papers, Please" but you're a firewall? I like it. Pretty cool.

Papers Please isn't really about the act of checking things. It's about the stories and moral choices. A lot of copycat games miss that point too.

Why not both?

So this game needs a story arc where you become an accomplice to specific threat group to bring vigilante justice while maintaining plausible deniability by blocking some of their requests without letting your total numbers drop below a specific threshold?

That would be pretty cool actually :-D

In the first round one of the POSTs was to be rejected because it was supposed to contain JSON but contained something else; that should have been made a 400.

You're acting as the firewall, not the application. That was not one of the rules for the day. In the first place a waf is specifically to stop malicious requests hitting the app.

That's true but not an argument for 403 over 400. Certainly either works. But one is more correct.

Please keep the missed attacks on screen instead of rushing to the next request and just leaving some error log.

Only tested the first round but identifying SQL injections and XSS brings back memories. Fun project!

This is really fun, I enjoyed it a ton!

I know some middle schoolers who are writing PHP apps. I could give them this game, but they don't deeply understand SQLi yet, for instance. Would you consider a mode that could be used to brief software-adjacent but security-ignorant students on the background of each attack style? This could be powerful as an education tool.

Reply on news.ycombinator.com