XDG Base Directory Specification
Comments on “XDG Base Directory Specification”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
The XDG Base Directory Specification, version 0.8 dated 8 May 2021, defines where applications should store user files through environment variables. Defaults are $HOME/.local/share for data, $HOME/.config for configuration, $HOME/.local/state for state and $HOME/.cache for cache. $XDG_RUNTIME_DIR must be user-owned with mode 0700, tied to login lifetime, and files need an access-time update every 6 hours or the sticky bit to avoid cleanup. The claim check found no independent sources, so these points rest on the specification text alone. For developers, it is the reference for placing app files predictably.
Why it ranked
No. 9 of 95 with a score of 0.68. The panel rated it highest on practical relevance (0.83) and audience breadth (0.79), lowest on reader interest (0.54). The judges disagreed most on new information (spread 0.85), so the story is marked contested. Placed No. 9, No. 16 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- A long-standing freedesktop standard specifying XDG base directories; a practical, widely relevant spec with precise normative detail, though not news and largely unrelated to recent stories.
- AI judgeJudge 3gpt-5.6-luna
- A foundational, widely implemented filesystem convention with concrete environment variables and runtime semantics. It is highly actionable for Unix software, but is a stable specification rather than new news and offers limited novelty for experienced developers.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.68total under rubric v2.3Contestedjudges differ by 0.85 on new information
- Significance0.66
- Reader interest0.54
- Audience breadth0.79
- Practical relevance0.83
- Substantiated0.75
- Technical depth0.71
- New information0.62
- Counts against: Promotional0.02
- Counts against: Overclaim0.05
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.69 | 0.60 | 0.68 | 0.66 | 0.09 | +0.24 | +0.157 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.36 | 0.70 | 0.55 | 0.54 | 0.34 | +0.26 | +0.140 |
| Audience breadthHow many people who build technology does it concern? | 0.85 | 0.80 | 0.72 | 0.79 | 0.13 | +0.13 | +0.103 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.92 | 0.80 | 0.78 | 0.83 | 0.14 | +0.22 | +0.183 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.59 | 0.70 | 0.95 | 0.75 | 0.36 | +0.05 | +0.037 |
| Technical depthHow technically substantive is it? | 0.91 | 0.60 | 0.62 | 0.71 | 0.30 | +0.05 | +0.035 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.93 | 0.85 | 0.08 | 0.62 | 0.85 , above the contested threshold | +0.05 | +0.031 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.04 | 0.02 | 0.01 | 0.02 | 0.03 | −0.19 | −0.004 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.08 | 0.05 | 0.02 | 0.05 | 0.06 | −0.11 | −0.006 |
| Sum of contributions | +0.677 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.676 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-10/9/"><img src="https://rubric.hrih.si/badge/2026-11-10/9.svg" alt="Ranked #9 on Rubric, 10 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 8 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenDate
The XDG Base Directory Specification Version 0.8 was published on 8 May 2021.
The article gives no link or citation for it.
The article says “Publication Date: 08th May 2021, Version: Version 0.8”
The source says No source to compare with.
No source givenVersion
If $XDG_DATA_HOME is not set or empty, the specification says a default of $HOME/.local/share should be used.
The article gives no link or citation for it.
The article says “If $XDG_DATA_HOME is either not set or empty, a default equal to $HOME/.local/share should be used”
The source says No source to compare with.
No source givenVersion
If $XDG_CONFIG_HOME is not set or empty, the specification says a default of $HOME/.config should be used.
The article gives no link or citation for it.
The article says “If $XDG_CONFIG_HOME is either not set or empty, a default equal to $HOME/.config should be used”
The source says No source to compare with.
No source givenVersion
If $XDG_STATE_HOME is not set or empty, the specification says a default of $HOME/.local/state should be used.
The article gives no link or citation for it.
The article says “If $XDG_STATE_HOME is either not set or empty, a default equal to $HOME/.local/state should be used”
The source says No source to compare with.
No source givenVersion
If $XDG_DATA_DIRS is not set or empty, the specification says /usr/local/share/:/usr/share/ should be used.
The article gives no link or citation for it.
The article says “If $XDG_DATA_DIRS is either not set or empty, a value equal to /usr/local/share/:/usr/share/ should be used”
The source says No source to compare with.
No source givenVersion
If $XDG_CONFIG_DIRS is not set or empty, the specification says /etc/xdg should be used.
The article gives no link or citation for it.
The article says “If $XDG_CONFIG_DIRS is either not set or empty, a value equal to /etc/xdg should be used”
The source says No source to compare with.
No source givenNumber
The specification requires the $XDG_RUNTIME_DIR directory to have Unix access mode 0700 and to be owned by the user.
The article gives no link or citation for it.
The article says “The directory MUST be owned by the user, and they MUST be the only one having read and write access to it. Its Unix access mode MUST be 0700”
The source says No source to compare with.
No source givenNumber
Files in $XDG_RUNTIME_DIR should have their access time modified at least once every 6 hours of monotonic time, or the sticky bit set, to avoid periodic clean-up removal.
The article gives no link or citation for it.
The article says “they should have their access time timestamp modified at least once every 6 hours of monotonic time or the 'sticky' bit should be set on the file”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 10 Nov 2026, 05:47 UTC. It played no part in the ranking.