[–] 1 point 1 month ago

When I finally tried out passkeys, Windows required me to use Windows Hello with a PIN, so login to my account was now with a (length limited) PIN instead of my account password. Soon after, my mainboard broke, meaning the keys were gone too. What a hassle. I don't use them anymore.

(I'm aware the Windows store may be just one of multiple options. It's what you're being pushed to, supposedly the straight-forward convenient way. It was not.)

  • source
  • [–] 6 points 1 month ago (2 children)

    I've been pretty pissed off at "helping bad people" with my freely given information since roughly the summer of 2022.

    The true test of our industry and community; will or how much will the current felt theft non-attribution and non-appreciation of good-will work influence or destroy good-will work like FOSS, free public resources and commons, and their communities.

    Good-will work was, presumably, always thankless for most people. No monetary gain, little direct feedback and appreciation or acknowledgement.

    Now that, seemingly, AI becomes the consumer and interface instead of people, it feels even worse. I would understand if this tips the scales for many people.

  • source
  • [–] 2 points 1 month ago

    For me, the same rules apply, but as you say or hint, SQL as a language is different from higher, "structured" programming languages.

    Adding comments on subqueries, applies, conditions, doing deliberate line breaks or oneliners, procedure comments and documentation where they make sense - most of the same things apply and are applicable. Structuring and commenting works quite well, until it doesn't for performance and readability reasons where you don't want to introduce additional procedures or functions or separate other aspects.

    In those cases, it is what it is. Often comments can live on the lines where the aspect is.

    I also like to use block comments with open and closing block indication like

    -- \ Table or aspect something stuff \
    […]
    -- / Table or aspect something stuff /
    

    The language doesn't provide the structure for it, but I can still implement that structure through text comments alone.

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

    The Media Player Remote Interfacing Specification (MPRIS) is a standard D-Bus interface which aims to provide a common programmatic API for controlling media players.

    This metadata is only for media streams, not something that would be embedded as metadata in a file?

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

    My colleague who didn't ask nor describe his changes now generates descriptions and code comments through AI and it doesn't improve anything. It's verbose, imprecise, confusing, and irritating.

    I wonder if and how much communication reduced with my other colleagues. I guess probably a bit where they now ask AI (first). But not significantly, in my team, luckily. We still regularly talk. But maybe it's on a path of reduction right now. I would find it sad and bad as well.

  • source
  • parent
  • context
  • [–] 1 point 1 month ago

    It really is a very visible demonstration of human faultiness.

    A reasonable engineering approach would have been an interesting new technology with open discussion and assessment and expansion of exploration. Instead, we get hype cycles and hyperbole claims and lies primarily driven and publicized and repeated as market marketing and investor marketing and an industry driven by money and investment rather than technology and reasonably explorative and increasing usage.

    It's sad and tragic. But not surprising. It's a consequence of human psyche, social constructs and market and society system structure.

    When I hear my colleague does a presentation differently for internal towards developers with more reasonable AI takes and a different one for external which basically practically joins the AI hype instead of voicing boundaries, it's pretty sad that it can't be honest communication throughout and be understood as such.

    I don't see it as an isolated fault of "corporate leadership" as in of development factories/teams. It's a broad issue, from the AI companies, press hype, industry hype, to then corporate and broader industry leadership eating it up and implementing and expecting marketing and hype claims.

  • source
  • parent
  • context
  •  

    AI models have a knowledge cutoff and do not have access to your personal or company data by default.

    While context engineering is a broader topic, this post will focus on enabling access to high-quality data through data ingestion pipelines.

    … we’re excited to announce the preview release of data ingestion building blocks for .NET.

    … how these building blocks empower the .NET ecosystem to build composable data ingestion pipelines for their AI applications.

     

    Over the past week, we've identified and tracked an unprecedented 23 extensions which copy other popular extensions, update after publishing with malware, manipulate download counts, and use KNOWN attack signatures which have been in use for months. Many of these relate to Glassworm malware, but there could be mulitple campaigns at work also.

     

    When Zork arrived, it didn’t just ask players to win; it asked them to imagine. There were no graphics, no joystick, and no soundtrack, only words on a screen and the player’s curiosity. Yet those words built worlds more vivid than most games of their time. What made that possible wasn’t just clever writing, it was clever engineering.

    Beneath that world of words was something quietly revolutionary: the Z-Machine, a custom-built engine. Z-Machine is a specification of a virtual machine, and now there are many Z-Machine interpreters that we used today that are software implementations of that VM. …

     

    During OpenAI’s GPT-5 launch event, they demoed the model’s ability to fix real bugs in production code. Live on stage. In their own repository. The kind of demo that makes CTOs reach for their credit cards and engineers nervously update their resumes. There’s just one small problem: the fix they promised to merge “right after the show” is still sitting there, unmerged, three and a half months later.

     

    binfmt_misc (short for Binary Format Miscellaneous) is a Linux kernel feature that allows the system to recognize and execute files based on custom binary formats. It’s part of the Binary Format (binfmt) subsystem, which determines how the kernel runs an executable file.

    In 2019, SentinelOne published a two-part analysis describing a persistence technique called Shadow SUID (Part 1, Part 2): Shadow SUID is the same as a regular suid file, only it doesn’t have the setuid bit, which makes it very hard to find or notice. The way shadow SUID works is by inheriting the setuid bit from an existing setuid binary using the binfmt_misc mechanism, which is part of the Linux kernel.

    Interestingly, this technique seems to have fallen into oblivion again, as neither MITRE ATT&CK nor the five-part Elastic Security “Linux Persistence Detection Engineering” series mentioned it (the last part here with links to all other parts). As of 2025, however, the technique works wonderfully and would probably be very difficult to detect (see the hunting section later).

    view more: ‹ prev next ›