TL22+ will include new topic clusters from 2023–2025, but it will require the patched core to function. Without the "archive fix patched" base, TL22+ will not install. If you rely on legacy topic clusters, structured web archives, or historical link analysis— yes, absolutely. The original Topic Links 22 archive was a treasure trove of digital culture, but it was fundamentally broken. Running it without the patch meant citing dead ends and corrupted databases.

Verify your current version. Open the archive’s root manifest.json . If the version field is 1.0.0 or 2.0.0 , you need the patch.

Re-index your local archive: tl22 index –rebuild –resolver=dynamic

Apply the patch_set_22_final.diff using: patch -p1 < patch_set_22_final.diff

The update restores integrity, revives chunk 22, and future-proofs the dataset for at least another three years. Download it from the official source, run the checksums, and enjoy a fully functional archive once again. Have you applied the patch successfully? Encountered any edge cases? Join the discussion on the official TL22 Community Forum (link in the patched archive’s README ).

However, for nearly eight months, users have been plagued by a recurring nightmare: The "Topic Links 22 Archive" seemed broken beyond repair. That changed last week.

Additionally, the patched archive is —about 14.6 GB uncompressed (up from 11.2 GB)—due to the resolver table and checksums. Ensure you have adequate storage. The Future After the Patch The patch is considered the "final stable release" of Topic Links 22. The maintainers have announced they will not be developing a Topic Links 23. Instead, they encourage users to fork the patched version and contribute to a community-maintained extension called TL22+ .

Run the integrity checker: ./tl22_check –fix-chunks