• 0 posts
  • 56 comments
Joined 3 years ago
Cake day: June 16th, 2023
  • Connections to apple streaming source CIDR blocks, connections to apple auth CIDR blocks, and a bunch of ips in apple blocks I have no idea what they do.

    Apple domains are easy to identify. https://support.apple.com/en-us/101555

    A lot of it associated with iTunes and apple store stuff like mzstatic.com but also https connections to unknown domains. It’s almost all https, so impossible to say what’s being sent.

    The content streams are easy to pick out, because only a handful of stateful sessions go to known CDNs.

    Why starting a movie or show on an apple TV requires a check to siri and search is probably explainable, but certainly 1400 requests during movie play to diagassets.apple.com (the “diagnostics” domain known to be a black hole of Apple mystery) is probably reporting data of some kind.

    It goes on like that, mysterious connections that occur during video play and at startup to domains like Apple Education raise a few eyebrows.

    And then there are the plugins, which do a lot of phoning home.

  • I don’t think there is anything, really. I use a soulseek client to get flac files and convert them to opus manually.

    Radarr and Sonarr work because the naming conventions for videos are more or less established.

    With music, everyone has a different philosophy for tagging, renaming files, transcoding, how to handle best-of albums, compilations, etc. So what works for you probably doesn’t work for me and vice versa.

    Lidarr gets very few updates, I don’t think anyone is working on it anymore. I remember the problem was keeping up with metadata handling.

  • I have been in IT for 30 years, and in security for the last 16.

    You’ll find lots of arguments from a productivity and removing barriers point of view that say don’t bother with strict user access controls, just layer on other security measures. Others (usually older-school sysadmins) preach “doing the work”, meaning secure your users well and audit access often. There are advantages and disadvantages to both approaches.

    I personally do a bit of both. The old way of being meticulous with access works, but not without diligence and self-audit. The newer devops way if doing things with secrets management and treating everyone as untrusted works too, as long as you document the automation.

    Maybe one suggestion about user control in a homelab setting is not to use the same username across multiple services, but rather name your users something like name.of.service.admin so that you a) don’t forget where you are and b) if you start collecting logs centrally, you can easily identify which system the logs came from.

  • Well, related to time, the one guy who maintained Linux NTP client/server almost had to stop doing it and go get a job a couple years ago.

    These projects are important, and while the article is a bit dramatic, I would argue that the folks doing work like writing IEEE specs and the drudgery of IANA cleanup are what keep the internet from being any shittier than it already is.

  • I just looked back over your post and your answers there and in here. With respect, your writing style sounds combative. I would never ask you to change it for anyone, but you should understand how it comes across.

    Regarding the AI disclosure stuff, you aren’t the first burgeoning dev posting to Lemmy to go through this exact gauntlet of “AI slop” accusations. You are on a platform used by a fairly specific group of people who were pissed off enough to leave reddit, so not the usual general “tech enthusiast” crowd, and a fairly militant bunch.

    The way I see it, AI is 1) already here and 2) just a tool. It’s being used in the background of a LOT of projects and there is by now simply no way to cover our ears and pretend it doesn’t exist. For better or worse, it’s also changing the pace of development, check out how fast PS5 emulation is happening because of AI tooling.

    That said, developer practices that took us 40 years to make standard are still valuable, so folks have legitimate reason to call out your commit and documentation practices. If there is anything I objected to in your project, it might be that.

    Ultimately, a created work starts to live a different life once it is public. You started without sharing it, shared the source, and now you have to make a decision: continue sharing and accept that not everyone will like it, or stop sharing. It’s really that simple.

  • Sir… You came to us for these comments this time. Are you just here for a fight? It’s not clear what you want from us.

    I don’t find your project interesting enough for me, but I was happy you did it. I prefer to keep my infrastructure at home in a controlled environment and take my maps out with me, but I don’t use navigation, I just record GPS tracks.

    Now with this post, I’m starting to wonder what your motivations are altogether, particularly considering your responses here.

  • Booooo.

    Prime example of why you don’t ask an LLM for actual information.

    1. Samsung Odyssey G9 cannot drop to below v1.4, not to mention any display port mode over 1.4 should understand mode, so this isn’t necessary.
    2. There is no ‘Y’ in /sys/module/<some graphics driver>/modeset, it is 0 for disabled, 1 for enabled, and 2 for headless.

    I know you think you’re helping, but it’s just muddying the water.

    STOP ASKING LLMS FOR ACCURATE INFORMATION.