• 0 Posts
  • 41 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle




  • I’ve been using various Aftershokz/Shokz models for many years and well over a thousand hours. They are a great option for speech-focused contents like podcasts, audiobooks and that’s what I use them for. I almost never use them for music, the lack of bass (even with earplugs) just doesn’t do it for me. But I don’t find any earbuds satisfactory for music either so maybe I am more picky than most.

    I agree with OP about the controls. They are workable but could be much better even considering the limited inputs. I particularly hate the choice of triple-click for backwards-seek and I mess up the timing half the time. Another pet-peeve is the loud beep on play/pause that cannot be turned off. Using the phone/computer controls instead of the on-device ones avoid these issues.

    As far as models I originally got the Aeropex and later on “downgraded” to the OpenMove. The audio quality is comparable between the two, the only thing you are missing with the lower end model is comfort - but that is highly subjective! I actually prefer the way the OpenMove feels.

    I really wish that there was more competition in this space. The Shokz products are a bit overpriced and slow to evolve and the rest of the options I’ve seen seems lower quality and worse form factor. Would love to hear if anybody has found a different brand that they prefer over the Shokz models.







  • donio@lemmy.worldtoLinux@lemmy.mlThe cost of maintaining Xorg
    link
    fedilink
    arrow-up
    20
    arrow-down
    1
    ·
    1 year ago

    Autotype is already solved - ydotool, wtype and dotool exists (and possibly others as well).

    These tools work by creating a virtual keyboard so they don’t let you send input to a specific window. The input goes to whatever happens to be focused at the moment. This makes them less reliable than the X11 equivalents and unusable for tasks where you need to guarantee that the right window gets the input.










  • Maybe other tools support this too but one thing I like about xdiskusage is that you can pipe regular du output into it. That means that I can run du on some remote host that doesn’t have anything fancy installed, scp it back to my desktop and analyze it there. I can also pre-process the du output before feeding it into xdiskusage.

    I also often work with textual du output directly, just sorting it by size is very often all I need to see.