Re:Why I Tend Not to Use Content Negotiation
by manwe150 on Sunday November 19, 2023 @11:04PM
(#38342120)
It is a good trick with GitHub though that you can add .patch or .diff to the url to fetch the content without styling
Re:Why I Tend Not to Use Content Negotiation
by amake on Monday November 20, 2023 @01:04AM
(#38343124)
It's not just styling. The content is actually a `git format-patch` patch for the former a unified-format diff for the latter.
Re:Why I Tend Not to Use Content Negotiation
by going_north on Monday November 20, 2023 @01:35AM
(#38343434)
Another good one for GitHub is that you can do
github.com/[username].png
to get that username's profile picture.
Re:Why I Tend Not to Use Content Negotiation
by theblazehen on Monday November 20, 2023 @02:54AM
(#38344185)
And
github.com/[username].keys
to get their ssh keys
Re:Why I Tend Not to Use Content Negotiation
by barosl on Monday November 20, 2023 @03:01AM
(#38344250)
We have
github.com/[username].gpg
to get their OpenPGP keys, too!
Re:Why I Tend Not to Use Content Negotiation
by rapnie on Monday November 20, 2023 @03:58AM
(#38345074)
Just go for .secrets to get it all in one request.
Re:Why I Tend Not to Use Content Negotiation
by withinboredom on Monday November 20, 2023 @06:17AM
(#38346375)
2 things.
What about any of that is "secret?"
This endpoint does not work.
If /fred returns HTML, then the URL is perfectly fine, since the only real consumer of fred.md or fred.json are automated systems/API clients, and they couldn't care less what the URL looks like, only that it's predictable.