2025-2026 is available (to purchase/read outside or ur site) and the last version 2026-2027 is planed for release on April 7th, https://www.amazon.com/CIA-World-Factbook-2026-2027-ebook/dp... .
Somehow it escaped me that these were published books as well. Thank you kind stranger.
Show HN: CIA World Factbook Archive (1990–2025), searchable and exportable
81–90 of 106 posts
Re: Show HN: CIA World Factbook Archive (1990–2025), searchable and exportable
#82Re: Show HN: CIA World Factbook Archive (1990–2025), searchable and exportable
#83Yes it is an ambitious project, yes it is useful in theory, but I’m interested in its viability as a legitimate tool for the sort of people who would rely on it for research purposes as opposed to the sort of people who find it a fascinating project but in practice it is little more than something to pique their curiosity—a toy.
At the same time maybe it doesn’t have to be either. It could just be a display of the initiative and ingenuity of the person behind it. But little else can be inferred about them I reckon.
Re: Show HN: CIA World Factbook Archive (1990–2025), searchable and exportable
#84Re: Show HN: CIA World Factbook Archive (1990–2025), searchable and exportable
#85This is how Show HN should work. Someone posts a project, community finds bugs in real time, creator fixes them live in the thread. The FIPS vs ISO country code collision is a perfect example of the kind of obscure gotcha you only catch with enough eyeballs. Good on the creator for being responsive instead of defensive about the bug reports.
Re: Show HN: CIA World Factbook Archive (1990–2025), searchable and exportable
#86This is how Show HN should work. Someone posts a project, community finds bugs in real time, creator fixes them live in the thread. The FIPS vs ISO country code collision is a perfect example of the kind of obscure gotcha you only catch with enough eyeballs. Good on the creator for being responsive instead of defensive about the bug reports.
And despite all of that this is an LLM comment, right?
Both accounts are used to advertise their website.
Re: Show HN: CIA World Factbook Archive (1990–2025), searchable and exportable
#87Earlier quoted context omitted.
And despite all of that this is an LLM comment, right?
Yep, all their comments are LLM output. As well as their alt https://news.ycombinator.com/threads?id=ruhith Both accounts are used to advertise their website.
Re: Show HN: CIA World Factbook Archive (1990–2025), searchable and exportable
#88This is how Show HN should work. Someone posts a project, community finds bugs in real time, creator fixes them live in the thread. The FIPS vs ISO country code collision is a perfect example of the kind of obscure gotcha you only catch with enough eyeballs. Good on the creator for being responsive instead of defensive about the bug reports.
And despite all of that this is an LLM comment, right?
AI is present everywhere these days. I wouldn’t be surprised if a OpenClaw bot autonomously create a project on GitHub and then submit it to HN, without any human involement.
Re: Show HN: CIA World Factbook Archive (1990–2025), searchable and exportable
#89Earlier quoted context omitted.
I found another example: searching for "Nicaragua" takes you to the page for "Niger".
Hi there, I have located the root cause and will be fixing the issue: Root cause: CIA uses FIPS codes (CanonicalCode), which differ from ISO Alpha-2 for many countries. Templates and SQL queries prioritized CanonicalCode over ISOAlpha2, so URL codes like /archive/2025/AU matched the wrong country. Australia (AU) -> American Samoa (AS = CIA FIPS for Australia) Singapore (SG) -> Senegal (SG = CIA FIPS for Senegal) Germ…
This is a good example of the importance of strong toping patterns. The GDP of Germany just tanked, we didn’t lose a mars climate orbiter this time. :)
Re: Show HN: CIA World Factbook Archive (1990–2025), searchable and exportable
#90This is how Show HN should work. Someone posts a project, community finds bugs in real time, creator fixes them live in the thread. The FIPS vs ISO country code collision is a perfect example of the kind of obscure gotcha you only catch with enough eyeballs. Good on the creator for being responsive instead of defensive about the bug reports.
And despite all of that this is an LLM comment, right?