• 0 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • At least for me, there is a big difference between naming things at home and naming things for work.

    Work “pet” machines get systematic names based on function, location, ownership and/or serial/asset numbers. There aren’t very many of them these days. If they are “cattle” then they get random names, and their build is ephemeral. If they go wrong or need an upgrade, they get rebuilt and their replacement build gets a new random name. Whether they are pets or cattle, the hostnames are secondary to tags and other metadata, and in most cases the tags are used to identify the machines in the first instance, because tags are far more flexible and descriptive than a hostname.

    At home, where the number of machines is limited, I know all of them like the back of my hand, and it’s mostly just me touching them, whimsical names are where it’s at.


  • marmarama@lemmy.worldtoSelfhosted@lemmy.worldWhat is your machine naming scheme?
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    2
    ·
    edit-2
    1 year ago

    Ungulates. Because who doesn’t like a hoofed animal?

    My client machines are even-toed ungulates (order Artiodactyla) and my servers/IoT machines are odd-toed (order Perissodactyla). I’m typing this on Gazelle. My router is called Quagga, both after the extinct zebra subspecies and the routing protocol software (I don’t use it any more but hey, it’s a router).

    Biological taxonomy is a great source of a huge number of systematic (and colloquial) names.


  • Yeah, I agree.

    I bought them for their noise cancelling primarily, and they’re excellent at that, but otherwise they’re not great. The un-EQed frequency response is terrible for headphones in their price range: flabby, wildly over-exaggerated bass and no mids at all. Running without EQ I can barely hear lyrics - every singer sounds like they’re mumbling underwater. I’ve had $20 IEMs with better tonal balance. They respond well to EQ but the on-board EQ doesn’t have enough frequency bands to even come close to fixing them. Wavelet on Android doing EQ duty makes them listenable. Even when you do EQ them properly, they still sound a bit dull and lifeless.

    No idea how they got so much praise when they were launched. The power of marketing budgets I guess. For a while I was gaslighting myself thinking I had a faulty pair or maybe there was something going wrong with my hearing, but having heard another pair, and doing comparisons with my other headphones - most of which are far cheaper - I realised that no, they’re just not very good as headphones.


  • It is worse than uncompressed, but 990Kbps LDAC is the closest codec to totally transparent I’ve heard for Bluetooth audio. AptX HD is nearly as good to my ears, and is better than 660Kbps LDAC. The differences are very small though, especially when compared with the differences on the analog side, e.g. the amp, and particularly the headphone design.

    Apple side-steps the problem by, at least when you’re listening to Apple Music, simply sending the AAC stream as-is to the headphones and has them decode the audio. I don’t know why that isn’t a more common approach.

    I’m still somewhat bemused that we’re talking about Bluetooth codecs at all. It surely can’t be that difficult technically to get 1.5Mbps actual throughput on Bluetooth and simply send raw 16-bit/44.1Khz PCM. 2.4Ghz WiFi is capable of hundreds of times that speed. Bluetooth has been stuck at the same speeds for decades.


  • I have a Radsone ES100 Bluetooth DAC/headphone amp, and that supports LDAC, multipoint, and doesn’t compromise the LDAC bitrate when you have multipoint enabled. You can even leave it plugged in as a USB DAC and still use multipoint BT with LDAC, and it switches smoothly between the sources depending on which device started playing a stream most recently.

    I was distinctly underwhelmed by the BT implementation when I got my Sony XM4s, it’s kinda weak by comparison.




  • Converted-to-Bluetooth Stadia controller.

    It’s actually a really nice controller. The ergonomics are great for my big meaty hands, it’s got some weight to it and feels really solidly built. The heft means the vibration really has some kick to it. The battery life is really good too - it was specced for having Wi-Fi on all the time, so now it’s running only a little Bluetooth LE radio, the battery is massive. Even when it runs down, the charge rate is quick - full in about half an hour, and then good to go for weeks. Again, probably because it was specced for Wi-Fi, the radio circuitry is way above average and the range is stupid - I can control a Steam Deck from two rooms away, through two solid brick walls, something none of my other controllers can do.

    The sticks are accurate and don’t drift, the buttons are pretty good, and the D-Pad is a bit stiff but perfectly serviceable. My one significant complaint is that the springback on the triggers is way too light, which makes it difficult to be subtle with the triggers, a little annoying for driving games.

    Still, if you see one at a sensible price, they’re a steal.


  • I always interpreted it as Kubrick trying to give you a feel for how vast even just the solar system is, and how long space travel takes. It’s slow and not much happens for long periods, because travelling to Jupiter is slow and not much happens for long periods.

    I agree that doesn’t make it an easy watch, but if you get into the right frame of mind to watch it, it gives you a kind of uneasy existential dread at the vastness of the universe and our inconsequential smallness in it, that very little other sci-fi does.