HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
randomdrake
human-headers
Web Development2014–2014
randomdrake / human-headers

human-headers

Human Headers is a project to let developers put a little more of themselves into their work without visibly impacting the web.

2Distinct people
3Mentions
0Explicit recommenders
23GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Human Headers is a project to let developers put a little more of themselves into their work without visibly impacting the web.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2014-02-05 18:53:42 UTC to 2014-03-14 17:24:24 UTC. Weeks start Monday, UTC.

0122014-02-03 00:00:00 UTC to 2014-02-10 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsFeb 32014-02-10 00:00:00 UTC to 2014-02-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-02-17 00:00:00 UTC to 2014-02-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 172014-02-24 00:00:00 UTC to 2014-03-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-03 00:00:00 UTC to 2014-03-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-03-10 00:00:00 UTC to 2014-03-17 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 10

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 32014-02-03 00:00:00 UTC2014-02-10 00:00:00 UTC211
Feb 102014-02-10 00:00:00 UTC2014-02-17 00:00:00 UTC000
Feb 172014-02-17 00:00:00 UTC2014-02-24 00:00:00 UTC000
Feb 242014-02-24 00:00:00 UTC2014-03-03 00:00:00 UTC000
Mar 32014-03-03 00:00:00 UTC2014-03-10 00:00:00 UTC000
Mar 102014-03-10 00:00:00 UTC2014-03-17 00:00:00 UTC101

What Hacker News says

3 sources
Great point. 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
In Show HN: Human Headers

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.