Funny thing is that people assume that tracking only happens over the web, in their browsers.

While Microsoft and company have been doing it for ages in their operating systems and office suites, many didn't think that some of the console tools they use did the same.


Here is why I am very hesitant about adopting new and flashy systems. You can't trust them.

I would posit that, after finding out they have a "telemetry" flag, it makes them untrustworthy entirely.

This should be a warning in any software stack. Look deeper. I'm sure there is more bullshit hiding in the code that "accidentally" leaks more information.

@nathand you might want to talk to @aral who forked an entire software stack to get rid of telemetry in there :)

@sheogorath @nathand Yeah, I wrote Auto Encrypt ( from scratch because Greenlock (not linking to it) had/has telemetry (and is a bloody mess of a codebase otherwise also).

@sheogorath @nathand (As @sheogorath said, I originally forked the whole mess of modules and tried to remove the telemetry but it was such a mess that I ended up creating my own module from scratch. Side effect: it’s also rock solid and simple as can be right now for a single use case.)

@aral @sheogorath Neat!

It's frightening how much data is collected, even by trusted tools. Tools that should be "offline" will often hoover up data just because and ship it off at the first sign of network connectivity.

I think because we don't get to see *how much* data is actually collected, we're more apt to be casual about it.

Having looked at some of the private telemetry data from O365, it's *a lot*.

Your company knows when you're (not) working. Down to the minute.

@nathand Unlike many products, though, they're giving you the option to say no. I've also seen some software which make "no telemetry" the default.

@binyamin Sure, it's better than nothing. I don't debate that.

What I have at issue here is that they do ✨ "telemetry" ✨ *at all*. Tools that are designed to do a thing are now, in greater number, phoning home for *no good reason*.

Data on where, when, why or how I use, or even who I used it with does not belong to the developer. It belongs to me. If you need to find out the software is used: Ask.

If I give you something, you shouldn't have to be paranoid that it's reporting its usage to me.

@nathand those should be opt-in anyway, not opt-out.

@mmu_man @nathand Guy accuses Syncthing but they are already opt-in WRT telemetry and crash reporting. Kinda spammy with the issue reporting approach too it seems.
Tools that spy should be rejected, asking creeps nicely isn't a winning strategy IMHO

No, its not. If you run the official syncthing app from F-Droid, for example, it will call four different domains before you even get the chance to configure something.
@fdroidorg any reason this is not marked as an anti-feature?

@mmu_man @nathand

@nathand this is a bad idea and also already illegal in EU.

Any telemetry gathering (because let's face it - even if it doesn't have its own UID they can check the src IP) should be opt-in only.

@Makdaam Yes.

If you'd like or "need" information on usage. Ask. If someone is unwilling to give you information, respect that. These are basic social decency things that organizations seem to ignore (for money).

Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.