Originally created by @ghost on GitHub (Jul 4, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
Problem Description
The problem is that huggingface and all the network entities in between me and huggingface know when i run openwebui, which is poor security and i can't believe i run openwebui for privacy and then i have this umbellical chord to huggingface and who knows what else.
Desired Solution you'd like
Stop pinging huggingface or reveal if there is an agreement to share traffic in the name of transparency, which nowadays is a rare good
Alternatives Considered
Alternative is stop using openwebui and move to a different, more private system
Additional Context
We are tired of our data treated as if they were a natural resource to exploit
Originally created by @ghost on GitHub (Jul 4, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
The problem is that huggingface and all the network entities in between me and huggingface know when i run openwebui, which is poor security and i can't believe i run openwebui for privacy and then i have this umbellical chord to huggingface and who knows what else.
### Desired Solution you'd like
Stop pinging huggingface or reveal if there is an agreement to share traffic in the name of transparency, which nowadays is a rare good
### Alternatives Considered
Alternative is stop using openwebui and move to a different, more private system
### Additional Context
We are tired of our data treated as if they were a natural resource to exploit
Even using pihole and blasklisting huggingface.co is not enough because i expect more, isn't there more?
It would be great if there was a document were external connections are listed together with the reason like commercial agreement, analytics etc.
Don't you accept sponsorship? then why would you go this extra mile to share user data and ruin the experience of your users?
@ghost commented on GitHub (Jul 4, 2025):
Even using pihole and blasklisting huggingface.co is not enough because i expect more, isn't there more?
It would be great if there was a document were external connections are listed together with the reason like commercial agreement, analytics etc.
Don't you accept sponsorship? then why would you go this extra mile to share user data and ruin the experience of your users?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ghost on GitHub (Jul 4, 2025).
Check Existing Issues
Problem Description
The problem is that huggingface and all the network entities in between me and huggingface know when i run openwebui, which is poor security and i can't believe i run openwebui for privacy and then i have this umbellical chord to huggingface and who knows what else.
Desired Solution you'd like
Stop pinging huggingface or reveal if there is an agreement to share traffic in the name of transparency, which nowadays is a rare good
Alternatives Considered
Alternative is stop using openwebui and move to a different, more private system
Additional Context
We are tired of our data treated as if they were a natural resource to exploit
@ghost commented on GitHub (Jul 4, 2025):
Even using pihole and blasklisting huggingface.co is not enough because i expect more, isn't there more?
It would be great if there was a document were external connections are listed together with the reason like commercial agreement, analytics etc.
Don't you accept sponsorship? then why would you go this extra mile to share user data and ruin the experience of your users?
@tjbck commented on GitHub (Jul 4, 2025):
OFFLINE_MODEenv var is provided for this specific purpose.