[–] 2 points 1 month ago (1 child)

Was the KabelDirekt one advertised as being suitable for headphones?

I share your frustration about not being able to tell in advance what's inside a cable.

Years ago, as a side hustle, I sourced audio cables; custom-making them where needed. Since then, the market has been flooded with Chinese imports that don't mention the specifications that used to be commonplace:

  • Shield type
  • Shield gauge and qty
  • Conductor material
  • Conductor gauge and qty
  • Resistance per metre
  • Capacitance
  • Outer diameter
  • source
  • parent
  • context
  • [–] 2 points 1 month ago

    The only negative point I saw in reviews of the Syncwire cable is that the braided jacket transmits mechanical noise to headphones. As someone else here mentioned, that's a problem with braided headphone cables generally.

    Unfortunately, all the similar cables I could find on Amazon have braided jackets:

    They all cost $10-$15 and look a lot like each other. Maybe from the same factory?

    As you say, it's virtually impossible to buy tinsel-cored audio cable in suitable lengths for DIY. If you want non-braided, I guess you'll have to either spend more money or cannibalise a cable from an existing pair of earphones/headphones.

    Let us know how it goes!

  • source
  • parent
  • context
  • [–] 3 points 1 month ago* (3 children)
    1. It's advertised to be suitable as a headphone cord (not just a headphone extension cord or aux cord).

    2. The cable is quite slender, <4mm OD (compare it to the 3.5mm plug in the photo). Yet it has a braided jacket, probably over a PVC jacket. That combo takes up more width than a PVC jacket alone. Therefore, the inner cores must be slender.

    3. Slender conventional inner cores in a wire advertised for headphone use would likely result in low reliability and bad reviews. But this cable has good reviews.

    4. Therefore, it's probably made with tinsel wire.

    N.B. Any pair of headphones/earphones (and old broken pair, or from a junk shop etc) likely has tinsel wire. Most headphones/earphones use captive cables, but you can always just snip the cable at the headphone end, solder on a 3.5mm plug (see tips in earlier comment), and thereby make yourself a cable that will work with headphones that have a 3.5mm socket.

  • source
  • parent
  • context
  • [–] 10 points 1 month ago* (last edited 1 month ago)

    Somewhere halfway last century

    IIUC, it was around the time the artistic set (F. Scott & Zelda Fitzgerald, et al) started to be written about & photographed sunbathing, playing outdoor sports, & generally enjoying themselves around Antibes.

    Suddenly the world wanted a piece of that luxury, or at least wanted to look like they’d had a piece of it.

    In addition to being tanned, the bright young things of the French Riviera were fit and lean. So this, too, became fashionable. In previous centuries, fat was instead the sign of wealth.

  • source
  • parent
  • context
  • [–] 20 points 1 month ago* (last edited 1 month ago) (10 children)

    Your Monoprice cables were probably made with ordinary stranded copper wire, which is suitable for use in an aux cable but not a headphone cable.

    Good headphone cables are instead made with tinsel wire, for far more flexing cycles than typical stranded copper. This page has close-up photos showing how it differs from ordinary stranded wire.

    Based on its advertised intended usage, I would guess this $13 Syncwire cable is made with tinsel wire.

    It looks decently-made. From a BIFL perspective, you may want learn to be able to replace the 3.5mm jacks. Tinsel wire isn't easy to solder, but here are some tips on how to do it:

  • source
  • [–] [S] 5 points 1 month ago (8 children)

    I'm probably having a brainfart (watched the video during insomnia), but re: the section 12m 10s into the video, can someone please clarify why "the instructions are dangerously wrong"?

    I understand it relates to the earlier demo in which those instructions gave the illusion of "verifying" an ISO that was in fact malicious. But:

    • why did those instructions fail to genuinely verify the ISO?
    • what would the correct instructions have been?
  • source
  • [–] 1 point 1 month ago*

    How could something designed for human communication be so utterly cumbersome and confusing ?

    Several reasons, I guess?

    1. The PGP (later, OpenPGP) protocol.

    The proprietary PGP software, which was the initial implementation of the PGP protocol(s) also suffered from usability problems:

    2. GnuPG maintainers are implicitly using asymptotic software versioning

    Donald Knuth was probably the most notable proponent of the idea that software packages should increasingly tend toward stability, with fewer and fewer patches needed. He used explicitly asymptotic version numbering for TeX and Metafont.

    Some of the quotes in OP's video make imply GnuPG's maintainers are implicitly following a similar approach, e.g. the section about "Sequoia's need for churn".

    With encryption software, there is an especially strong argument for being conservative about changes. Patches may have unforeseen consequences, adding subtle vulnerabilities.

    However, the downside of this, as the gpg.fail team pointed out, is that it biases the GnuPG maintainers towards excessive rejection of patches. Especially patches that would improve usability. Arguably, TeX suffered from a similar bias; hence the development of LaTeX and newer TeX front-ends to improve usability.

    3. Changing the interface would be effortful

    Improving GnuPG's interface would require quite a lot of work in itself, both to the codebase and the documentation.

    Releasing a version with those changes would also require fielding a lot of support queries for many years, because decades of software manuals all over the web were written for the traditional GnuPG interface, and aren't going to be updated overnight. Some of those manuals will surely never get updated, because they are no longer maintained even though they are still online and still used.

    I can sympathise with the GnuPG maintainers for finding this daunting. But the improvements are needed. Thankfully, developers of tools like minisign, age, and sequoia are taking on much of this work; it's just a pity that the work had to be done in this fragmented way through third-party efforts, instead of in GnuPG itself.

  • source
  • parent
  • context
  • [–] 4 points 1 month ago (1 child)

    Agree re ads.

    I know people who like Apple Music. I don’t want a subscription service, but it might suit you?

    MP3 player or self-hosted streaming bring music under your control while still allowing portability & arbitrarily long playlists.

    Like you, though, I don’t always want to manually curate my playlists. I need to look into self-hosted options that will automatically refine playlists for me similar to how Apple Music does for its users. Open to recommendations!

  • source
  • view more: next ›