4 ms·
They're saying what is clearly explained in the article: “This is why users who disabled Telemetry would see this problem resolved even though the problem is n
by acdha 5y ago
They're saying what is clearly explained in the article:
“This is why users who disabled Telemetry would see this problem resolved even though the problem is not related to Telemetry functionality itself and could have been triggered otherwise.”
- KronisLV 5y agoYes, but the fact that telemetry is in place was the cause for the issue. > So you're saying that Firefox did not on fact have an outage due to a change in their telemetry servers? Not the telemetry code. Not the fact that it "could" happen elsewhere. But rather the fact that it was in place and in this instance happened because of it. Not that it matters that much. Regardless of the particular cause, a browser failing to work because of something changing externally is crazy (at least to me), no matter how you look at it. Edit: this is now largely a duplicate of the other comment, hmm: https://news.ycombinator.com/item?id=30179023 https://news.ycombinator.com/item?id=30179023