|
|
|
|
|
|
by whileonebegin
4510 days ago
|
|
|
At first, I liked this idea. It's an ego boost. But then I realized this extra HTTP header information is going out with every request, and really only serves to increase bandwidth. Yes, I know, what's 72 more bytes per request? Still. With humans.txt, the request is on demand. |
|
|
With the goal being that this can run in your browser as you browse the web, would it be more expensive to make an additional entire HTTP request to a, possibly non-existent, humans.txt for every single domain? Or simply pass additional bytes along?
In the discussion on github[1] I raised the suggestion of possibly having the browser extension pass a special accepts or requests header so that it's only passed for people who have the extension installed. Then a simple conditional would be used for the server configuration instead of a statement.
Does that satisfy concerns with "bloat" or are there other considerations, do you think?
[1] - https://github.com/randomdrake/human-headers/issues/1