Huggingface Access Token Removal

[Ivan2getdmodelz]

Consider removing the requirement for a huggingface access token for utilizing this project. Requiring a token seems counter to having it released with an MIT license file, especially considering the fact that this tool is suitable for offline applications, and not need the internet after initial download.

[Karen86Tonoyan]

Consider removing the requirement for a Hugging Face access token to use this project. Since the project is released under the MIT License and appears designed to run locally, requiring authentication feels unnecessary. The tool seems perfectly suitable for offline use, and after the initial model download it should not require internet access or an external account. Allowing the project to run without a Hugging Face token would make it more consistent with the spirit of open-source and improve accessibility for users who want to run it fully offline. pon., 9 mar 2026, 21:22 użytkownik Ivan2getdmodelz ***@***.***> napisał:

…

Consider removing the requirement for a huggingface access token for utilizing this project. Requiring a token seems counter to having it released with an MIT license file, especially considering the fact that this tool is suitable for offline applications, and not need the internet after initial download. — Reply to this email directly, view it on GitHub <#1988>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BUHB4E6LE6HPOJXAKUDZAXL4P4RZ5AVCNFSM6AAAAACWMJMA6GVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZZGYYDSNBYGY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[hbredin]

See https://huggingface.co/pyannote/speaker-diarization-community-1#offline-use for offline use, without HF token.

[Ivan2getdmodelz]

But in those instructions, it still requires an HF token as the loggin with a username and password is depricated for cloning the git repo:

# make sure git-lfs is installed (https://git-lfs.com)
git lfs install

# create a directory on disk
mkdir /path/to/directory

**_# when prompted for a password, use an access token with write permissions.
# generate one from your settings: https://huggingface.co/settings/tokens_**
git clone https://hf.co/pyannote/speaker-diarization-community-1 /path/to/directory/pyannote-speaker-diarization-community-1

[hbredin]

Cloning the repo does require a token indeed -- and we do not plan on changing this.

If you need a token-less solution, feel free to create a token-less copy of the repo.

[Ivan2getdmodelz]

To quote the commenter above, " Allowing the project to run without a Hugging Face token would make it more
consistent with the spirit of open-source and improve accessibility for
users who want to run it fully offline." Seeing that you have no plans to change this, what steps do I need to follow to create token-less copy of your repo?