• 0 Posts
  • 8 Comments
Joined 10 months ago
cake
Cake day: October 11th, 2023

help-circle



  • Nahdahar@lemmy.worldtoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    9 months ago

    I’m kind of a generalist in terms of interest in the IT sector and have a surface level understanding of most things (professionally I’m just a fullstack webdev), one big crater in my knowledge is about how drivers work, really want to do something like this in my free time (next year because I’m pretty much drowning in tasks now). The closest (but still pretty far) to this I’ve done is write a small service that increases / decreases volume through pulseaudio based on ACPI events (windows tablet volume buttons weren’t working properly under linux).

    Reading my comment back, excuse my writing style (too many brackets lol).





  • My problems with telemetry:

    Scope: if you provide a service which is a “wrapper” for doing other things, I do not want you to collect usage data. Example: an entire fucking operating system

    Opt-out by default (or completely unable to turn it off) even if the service or software I’m using is paid: I want to have the ability to say no. Communicate properly what you collect when I get access to the service, allow me to say no and don’t hide it in 300 pages long TOSes. I don’t want to become your free UX tester when I already pay for the service.

    Telemetry-driven development: I absolutely hate this both as a user and a developer. We see there are thousands of users using a feature, but it’s a low % in general, so lead decides we need to remove it from our product. I know that those x thousand people will be annoyed, and so am I when I’m on the receiving end of this.

    Another reason that is not universal but service specific is making decisions that purposefully keep you on the platform, over optimizing the interface for maximizing profit.