News for hackers. Stuff that matters.
Re:I’ve banned query strings by deepsun on Saturday May 09, 2026 @11:01PM (#48080582)
But the path misses param names (or types?). E.g who said the hex-encoded part is a commit hash? Maybe it's a tree hash, or just weird ref.

Query strings are more verbose as force to give each param a name.

Re:I’ve banned query strings by altairprime on Saturday May 09, 2026 @11:39PM (#48080789)
Which target audience of github needs extra verbosity in the commit hash, though? Once you know it you know it; if you don’t know git you aren’t the target audience; etc. Saying /user=foo is no better than ?user=foo if your audience can work it out without confusion from your unadorned paths. We have a great deal of history with filesystems showing that people are capable of keeping up with paths that lack key names if exposed to and familiar with them, and if the filesystem isn’t being constantly randomized.
Re:I’ve banned query strings by deepsun on Monday May 11, 2026 @01:31PM (#48097974)
> Saying /user=foo is no better than ?user=foo

I mean /foo vs ?user=foo

I know git enough, there's more than one type of hashes -- object hashes, tree hashes.