• 1 Post
  • 96 Comments
Joined 1 year ago
Cake day: November 20th, 2024
  • MarkaostoAndroid@lemdro.id•Google confirms Android’s Quick Share-AirDrop interoperability is expanding to more Android devices this yearEnglish
    1·
    7 days ago

    For context, AirDrop is a proprietary communication between Apple devices, but the EU forced them to open it up and adopt an open protocol called WiFi Aware.

    EU forced Apple to adopt WiFi Aware, but not to switch AirDrop to use it - the intended effect is that WiFi Aware is available to developers who can then create their own alternatives to AirDrop that are not locked to one OS.

    Also Pixel 10 series can currently share even to iPhones that never got the new iOS with WiFi Aware support, so claiming this is thanks to EU is absolute BS (although often repeated, for some weird reason). This is just AWDL (which was reverse engineered long ago btw, and there has even been an experimental implementation on Linux for years) + some reverse engineering of the actual AirDrop protocol implemented on top of it.

  • MarkaostoLinux@lemmy.ml•LD_PRELOAD: What is it and how to use it
    6·
    4 months ago

    In fact, I think you’d be better off writing a deep dive into what/how environment variables work at build time, and also invoking commands on the CLI.

    But LD_PRELOAD doesn’t really have much to do with build time behavior (unless you’re talking about replacing parts of the compiler) - it allows you to force a shared library to be loaded with higher priority than anything else, so it overrides symbols from other libraries.

    It is recognized and used by Linux’s dynamic linker, which is run-time, not build-time.

  • MarkaostoOpen Source@lemmy.ml•Open source GZDoom community splinters after creator inserts AI-generated code - Ars Technica
    5·
    4 months ago

    Yes, the DE-specific implementations is pointless (as far as I know, I use a WM), but the XDG implementation is actually used first, and the function returns true if any impl returns true, like xdg() || gnome() || gnome_old() || kde().

    True, I must’ve read the code wrong when making the comment.

    This isn’t that bad?

    Yes, which is why I take issue with a PR (or rather what should have been a PR) that introduces crap code with clearly visible low effort improvements - the submitter should’ve already done that so the project doesn’t unnecessarily gain technical debt by accepting the change.

    With multiple impls, you have to resolve conflicts somehow.

    Yep, that’s why I think it’s important for the implementations to actually differentiate between light and fail state - that’s the smallest change and allows you to keep the whole detection logic in the individual implementations. Combine that with XDG being the default/first one and you get something reasonable (in a world where the separate implementations are necessary). You do mention this, but I feel like the whole two paragraphs are just expanding on this idea.

    But it’s better to criticize the code’s actual faults (…)

    I made a mistake with the order in which the implementations are called, but I consider the rest of the comment to still stand and the criticisms to be valid.

  • MarkaostoOpen Source@lemmy.ml•Open source GZDoom community splinters after creator inserts AI-generated code - Ars Technica
    91·
    4 months ago

    Well, the detection is broken for KDE and backwards in the XDG implementation (which is also only used as a fallback when the three DE-specific implementations fail, even though all of them actually support XDG so having separate implementations is pointless).

    Also with the way it’s implemented, it will have unexpected results for users who have both KDE and Gnome installed (or at least have leftover configuration files) - if you for example used KDE in the past with a theme considered to be “dark” by this and now use Gnome and have it set to light mode, you will get dark mode GZdoom with no obvious reason why.

    Oh and the XDG implementation is also very fragile and will not work on everyone’s system because it depends on a specific terminal utility being installed. The proper way would be to use a DBus library and get the settings through that.

    And when somebody comes to fix it, they will have to figure out a) what’s so special about the DE-specific implementations that XDG wasn’t enough (they might just assume that XDG isn’t supported widely enough), b) learn how to detect dark theme properly on the DE they’re fixing, c) rework the code so that there is a difference between “this DE wants light mode” and “couldn’t figure out of this DE is in light or dark mode” - both of these are now represented by the “false” return value.

    I don’t think a well written and functioning code made with AI assistance would get a response this strong, but the problem here is that the code is objectively bad and its (co-)author kept doubling down about something they probably barely even checked.

  • MarkaostoSelfhosted@lemmy.world•removed a homeplugEnglish
    1·
    4 months ago

    Don’t know about the UK, but in central Europe it’s common for houses to get three phase power that can then be used on 400V three phase circuits and gets split (ideally evenly) into 240V circuits. And the fact that the phases have effectively zero coupling means that you also need to just try the adapter to find out if it’s going to work or not unless you happen to know how exactly your house is wired up, just like with split phase power.

    Apartments usually get a single phase though, but IMHO it’s also less likely that WiFi won’t be enough there, so it’s questionable if that’s even a point for powerline.