Skip to content

[Archive] Tracker issue for clients compliant with the new caching source #20832

@kbdharun

Description

@kbdharun

As stated in #12048 and client specification releases v2.2 and v2.3, we are deprecating providing assets via the old https://tldr.sh/ domain and instead are fully migrating to GitHub releases.

This tracker issue aims to inform and encourage client authors to update their clients to the new source, or else to fallback to GitHub's archive (i.e., https://github.com/tldr-pages/tldr/archive/main.zip, https://raw.github.com/tldr-pages/tldr/main/pages, etc.) if a client update isn't possible.


Analysing the actively maintained clients in Wiki, I have categorised the clients into those compatible with the new structure, clients that fallback to direct GitHub repo/archive (i.e. https://github.com/tldr-pages/tldr/archive/main.zip, https://raw.github.com/tldr-pages/tldr/main/pages, ...), and incompatible clients (clients that need to be migrated/patched)


Compatible Clients (using GitHub releases) ✅

Console

Mobile

Application Integrations

Compatible Clients (using the repo or other fallback methods) ✅

Web

Console

Application Integration

Unknown Clients (with no known caching source) ⁉️

Web

  • Distrowatch (not sure if the pages are being updated)
  • Dendron (not sure if it's even updated since 2024)
  • Linux Command Library (not sure if the pages are being updated)

Incompatible Clients ⚠️

Console

Metadata

Metadata

Assignees

No one assigned

    Labels

    architectureOrganization of the pages per language, platform, etc.archiveArchive of changes made in tldr-pages, etc.decisionA (possibly breaking) decision regarding tldr-pages content, structure, infrastructure, etc.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions