Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #5519] [DOCS]: Audit and document outgoing connections #5143

New Issue
Closed
opened 2026-06-05 14:52:15 -04:00 by yindo · 4 comments
yindo commented 2026-06-05 14:52:15 -04:00
Owner
Copy Link
Copy Source

Originally created by @tredondo on GitHub (Apr 24, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5519

Description

Given the states focus on privacy, it would be great to list all domains that AnythingLLM legitimately attempts to connect to, so that system/network administrators can implement the necessary firewall rules.

Example domains that AnythingLLM connects to after disabling telemetry:

  • raw.githubusercontent.com
  • cdn.anythingllm.com
Originally created by @tredondo on GitHub (Apr 24, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5519 ### Description Given the states focus on privacy, it would be great to list all domains that AnythingLLM legitimately attempts to connect to, so that system/network administrators can implement the necessary firewall rules. Example domains that AnythingLLM connects to after disabling telemetry: - raw.githubusercontent.com - cdn.anythingllm.com
yindo added the documentation label 2026-06-05 14:52:15 -04:00
yindo closed this issue 2026-06-05 14:52:15 -04:00
yindo commented 2026-06-05 14:52:16 -04:00
Author
Owner
Copy Link
Copy Source

@tredondo commented on GitHub (Apr 24, 2026):

@timothycarambat Thank you for the quick resolution.

However, given the summary dismissal of most of the other issues I've filed as "not planned", without any explanation, I'm going to migrate to an LLM front-end with a friendlier attitude towards QA volunteers.

<!-- gh-comment-id:4316327400 --> @tredondo commented on GitHub (Apr 24, 2026): @timothycarambat Thank you for the quick resolution. However, given the summary dismissal of most of the other issues I've filed as "not planned", without any explanation, I'm going to migrate to an LLM front-end with a friendlier attitude towards QA volunteers.
yindo commented 2026-06-05 14:52:16 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Apr 24, 2026):

@tredondo That was done as an effort to manage the issues. You opened ~12 issues in the space of about an hour. This leads to a frustrating level of notification spam to triage and while I can appreciate what the attempt was I was actually in the process of triaging them into 1 big "Feedback issue" - which is something you can see other tickets of. It's just how we do things.

Opening up an atomic ticket for stuff that may or may not be a bug is really not sustainable and it is easier for "QA Feedback" to be done in a single issue with PR's tying back to them. However, if that is how you feel then of course you are open to do and use whatever you like

<!-- gh-comment-id:4316430337 --> @timothycarambat commented on GitHub (Apr 24, 2026): @tredondo That was done as an effort to manage the issues. You opened ~12 issues in the space of about an hour. This leads to a frustrating level of notification spam to triage and while I can appreciate what the attempt was I was actually in the process of triaging them into 1 big "Feedback issue" - which is something you can see other tickets of. It's just how we do things. Opening up an atomic ticket for stuff that may or may not be a bug is really not sustainable and it is easier for "QA Feedback" to be done in a single issue with PR's tying back to them. However, if that is how you feel then of course you are open to do and use whatever you like
yindo commented 2026-06-05 14:52:16 -04:00
Author
Owner
Copy Link
Copy Source

@tredondo commented on GitHub (Apr 24, 2026):

You opened ~12 issues in the space of about an hour.

A positive perspective is regarding that as a volunteer offering one hour of their time to improve the polish of the product.

This leads to a frustrating level of notification spam

I'm sorry. Unfortunately that's how GitHub works. "Spam" was definitely not my intention.

It's just how we do things.

Fair enough. The vast majority of projects I've contributed to prefer to have separate tickets per issues.

Image
<!-- gh-comment-id:4316501983 --> @tredondo commented on GitHub (Apr 24, 2026): > You opened ~12 issues in the space of about an hour. A positive perspective is regarding that as a volunteer offering one hour of their time to improve the polish of the product. > This leads to a frustrating level of notification spam I'm sorry. Unfortunately that's how GitHub works. "Spam" was definitely not my intention. > It's just how we do things. Fair enough. The vast majority of projects I've contributed to prefer to have separate tickets per issues. <img width="855" height="501" alt="Image" src="https://github.com/user-attachments/assets/61f22566-6a85-4dce-a4e3-c3309d9d37c6" />
yindo commented 2026-06-05 14:52:16 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Apr 24, 2026):

Yeah I am not arguing with your logic as it if unsound or illogical - just explaining the circumstance. Understandably it looks like everything just got dismissed instantly

<!-- gh-comment-id:4316657110 --> @timothycarambat commented on GitHub (Apr 24, 2026): Yeah I am not arguing with your logic as it if unsound or illogical - just explaining the circumstance. Understandably it looks like everything just got dismissed instantly
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#5143
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?