[Removal Request] - g.live.com and h.live.com (Expedite if Possible)

[MNLierman]

As of 12-29-2024 at 6AM MST, these domains are still present in the blocklist.

URL(s) to be removed:

• g.live.com
• h.live.com
• Any other one-letter *.live.com domains, except for c.live.com or other telemetry endpoint confirmed by Microsoft in blog posts.

Expedited Request: As explained below, due to the impact blocking these subdomains has OneDrive Enterprise sync (which uses OneDrive.exe sync client) I am requesting a faster response, if that's possible. In the meantime, I have disabled this blocklist.

Reason for False Positive: Blocking g.live.com, h.live.com, and other *.live.com domains (excluding c.live.com and other Microsoft confirmed telemetry endpoints) impedes OneDrive syncing. Specifically, several of my PCs are experiencing issues with OneDrive Enterprise syncing. It is important to note that OneDrive Enterprise uses the same OneDrive.exe sync client as the consumer versions. This issue does not pertain to SharePoint sync, as I do not have it installed and thus have not tested its behavior in this context.

Since incorporating this blocking list, my OneDrive sync clients get stuck on “Uploading x MB of x MB at 0.0 KB/s, x files remaining” indefinitely. Upon further investigation, I discovered hundreds of queries to g.live.com and h.live.com per hour from these OneDrive sync endpoints. Disabling this blocklist and restarting the clients resolved the sync issues.

List URL: https://blocklistproject.github.io/Lists/ads.txt
List Name: “Blocking List Project: Ads.txt”

Additional Information: This continuous querying is problematic from a networking standpoint, as my DNS query logs are flooded with requests to g.live.com and some to h.live.com Additionally, there are numerous comments online indicating that h.live.com and g.live.com are required for saving BitLocker Encryption keys to the Microsoft Account dashboard; it may also block updating the Last Active field, which could complicate retrieving recovery keys in the future if the user has multiple keys saved from past OS installs and cannot determine which key is currently in use.

BEFORE DISABLING BLOCKLIST

AFTER DISABLING BLOCKLIST

[spirillen]

As IT Expert - Developer - Managing Director, you of course looks true the lists of issue's and investigated if the project seems solid, maintained and curated. No? Maybe you have to many wife's then...

#1210

[MNLierman]

Hi, no-thankyou for your comment. I say this respectfully. You, of course, need:

1. Better English and grammar skills, yours suck.
2. Better
   professionalism skills, yours suck.

I'm not sure how my Business or Dating skills
have any relevancy to the issue report that I submitted. You can verify that the issue I reported includes enough information to investigate the matter and includes a screenshot showing that indeed devices are getting blocked with this blocklist.

Because of this I kindly request that you: F—k Off, (kindly of course).

Please do not bother to comment further, as I do not enjoy my time wasted or being insulted on GitHub. Don't want someone to swear at you? Then don't insult them. My dating preferences are none of your business.

Also, if you are trying to tell me that this repo is no longer maintained anymore, then, as per GitHub recommended policies for developers, the following needs needs to happen!

• Place banner text at top of your repo ReadMe.md: IMPORTANT: THIS REPO IS NOT MAINTAINED RIGHT NOW.
• Turn off Issue Reports, or, create a GitHub Action that comments on all issue reports that the repo is not maintained at the moment, and suggests a few alternatives.

However, such a warning is not present on the description page, and there are many other issue reports that have been submitted by other people, which suggests that it is NOT CLEAR that this repo is no longer maintained.

As such, I request in the future that you refrain from insulting other people, as that is just bad behavior for GitHub. Insulting someone's intelligence, their businesses, or their dating preferences have NO PLACE AND NO TOLERANCE ON GITHUB.

E: Because GH email replies do not format.