Remove countly.ipfs.tech telemetry

[lidel]

This is a placeholder issue: we won't have paid Countly after Feb 18th, 2024
and iiuc should remove / disable code that sends requests to countly.ipts.tech.

There is a proposal in ipfs-shipyard/ignite-metrics#133 to update ignite-metrics to use Plausible instead and then have this repo update to use the new ignite-metrics.

Regardless of the chosen path, the Countly shutdown will happen first, independent of this work. This means that for a time, metrics will be POSTed to countly but not stored.

cc ipfs/ipfs-webui#2198 ipfs/ipfs-desktop#2743

[markg85]

I was just about to report a bug for this till i say this one.

On my pc IPFS companion was enabled as in the extension but the functionality was disabled (grey box).

Yet in my DNS records i saw a call to countly.ipfs.tech every minute or so:

...
2025-02-07 19:49:53	AAAA	countly.ipfs.tech	10.0.3.55	OK (cache)	NXDOMAIN (0.0ms)	
2025-02-07 19:49:53	A	countly.ipfs.tech	10.0.3.55	OK (cache)	NXDOMAIN (0.0ms)	
2025-02-07 19:49:53	AAAA	countly.ipfs.tech	10.0.3.55	OK (cache)	NXDOMAIN (0.0ms)	
2025-02-07 19:49:53	A	countly.ipfs.tech	10.0.3.55	OK (cache)	NXDOMAIN (0.0ms)	
2025-02-07 19:48:48	AAAA	countly.ipfs.tech	10.0.3.55	OK (cache)	NXDOMAIN (0.0ms)	
2025-02-07 19:48:48	A	countly.ipfs.tech	10.0.3.55	OK (cache)	NXDOMAIN (0.0ms)	
2025-02-07 19:48:48	AAAA	countly.ipfs.tech	10.0.3.55	OK (cache)	NXDOMAIN (0.0ms)
...

This probably is a bug as:

• My ipfs companion wasn't enabled (grey box, aka, plugin is loaded and accessible)
• I had disabled telemetry

[SethDocherty]

@markg85, I'm witnessing the same behavior as well.

• IPFS companion app is not enabled
• telemetry disabled.

2025-02-07 15:09:14	A	countly.ipfs.tech	192.168.86.1	NXDOMAIN (0.2ms)	
2025-02-07 15:09:14	HTTPS	countly.ipfs.tech	192.168.86.1	NXDOMAIN (0.2ms)	
2025-02-07 15:09:14	AAAA	countly.ipfs.tech	192.168.86.1	NXDOMAIN (0.2ms)	
2025-02-07 15:09:14	AAAA	countly.ipfs.tech	192.168.86.1	NXDOMAIN (0.0ms)	
2025-02-07 15:09:14	A	countly.ipfs.tech	192.168.86.1	NXDOMAIN (0.1ms)	
2025-02-07 15:09:14	A	countly.ipfs.tech	192.168.86.1	NXDOMAIN (0.2ms)	
2025-02-07 15:09:14	HTTPS	countly.ipfs.tech	192.168.86.1	NXDOMAIN (0.2ms)	
2025-02-07 15:09:14	AAAA	countly.ipfs.tech	192.168.86.1	NXDOMAIN (0.2ms)

I had to disable the extension via the browser extension settings to cut off background processing.

According to my Pihole setup, I have 9300+ requests in the past 24 hours. Blacklisting helps some by reducing the number of requests to the upstream DNS server (1.1.1.1).

[markg85]

I'm not worried about an upstream dns, i'm using unbound in pihole. Note the cache and 0.0ms in my log dump.

What i am worried about is IPFS still doing "something" when disabled, that's not nice at all. I removed the extension as i hadn't been using it for years anyhow. It was just the trigger i needed to clean up.

[SethDocherty]

I'm not worried about an upstream dns, i'm using unbound in pihole. Note the cache and 0.0ms in my log dump.

What i am worried about is IPFS still doing "something" when disabled, that's not nice at all. I removed the extension as i hadn't been using it for years anyhow. It was just the trigger i needed to clean up.

Got it.

Exactly! It shouldn't be doing anything, e.g. making requests, when it's disabled. I was merely providing context into how much it's doing "something" over a 24hr period.

[SethDocherty]

@lidel, would commenting out this line disable the request from happening? If so, at least this removes unnecessary requests from being made.

❗ This doesn't solve the overarching issue that we've pointed out here, which is doing something like making telemetry requests when the extension is disabled.