• 1 Post
  • 332 Comments
Joined 3 months ago
cake
Cake day: June 23rd, 2026

help-circle

  • Last fall, OpenAI shared research showing that about 1 million people a week have conversations with ChatGPT that include explicit indicators of potential suicidal planning or intent.

    In the sub-linked article:

    our initial analysis estimates that around 0.15% of users active in a given week have conversations that include explicit indicators of potential suicidal planning or intent and 0.05% of messages contain explicit or implicit indicators of suicidal ideation or intent.

    0.15% sounds rare on the surface, but percentages stop being intuitive at massive scales like that. If many people are using this thing as a suicide hotline, it needs to handle this gracefully; or at the very least not encourage them for God’s sake.








  • I always thought this stance to be interesting, because it reminds me of soldiers in a conflict. The arguments are that the enemy rank and file are just doing their jobs, they have a family, the actual evil bigwig is out of reach, etc.

    But also, are you just going to do nothing and let them steamroll you? They’re choosing to continue to work at that business, and are the only “frontline” that you can interact with. The fact that the business made a policy specifically addressing this common complaint, means it actually reached the ears of someone in power.

    I’m not encouraging violence or anything of course. But, by design, there’s nobody else to voice your displeasure to. The only other option is to quietly accept their changes and be ignored.

    If they didn’t want angry people calling, maybe they shouldn’t make terrible decisions?




  • By that I mean you have to be careful which libraries you use. There’s a good chance that a System.* or random NuGet package will either completely fail to run on Linux, or be horribly buggy if you force it to work via build flags. In fact, they’ve completely removed the build flag in .NET 7+, System.Drawing.EnableUnixSupport. It used to be supported via libgdiplus.

    I would expect .Net to be fully compatible with Linux out of the box. Especially system libraries. You can’t say that you support cross-compatibility, and then deprecate cross-compatibility of system libraries; that’s just insane.

    I don’t remember the exact details because it’s been several years, but it was far more than just System.Drawing.Common that broke on Linux after updating to .Net 6. Some breaking changes were undocumented, only appearing later in GitHub issues. Some were buried in sub pages or individual library documentation.

    In the patch notes they even had the gall the claim that our business use case doesn’t statistically exist, and we can just drop in replace SkiaSharp; which was absolutely not the case. It was an unmitigated fucking disaster, even accounting for rolling back to .Net 3.1 for a few months while we sort it out and wait for critical 3rd party libraries to accommodate the change. Before anyone says it, yes we actually paid handsomely for our critical third party libraries; we didn’t mooch off open source and whinge about it. Even so, it never really worked right after that change. A hundred small things, like differences in how SkiaSharp draws differently and handles edge cases. In an enterprise application, it was a big problem.

    More reading: https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/6.0/system-drawing-common-windows-only


  • Zarobi@aussie.zonetoTechnology@lemmy.worldHang on to your Firefox!
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    8 days ago

    Firefox does only exist because Google pays for it. Google is Mozilla’s single greatest financial contributor. They’re essentially keeping a competitor on life support to avoid breaching antitrust laws. Essentially, the argument is that as long as Firefox exists, Google isn’t a monopoly.

    However, at any time, Google could simply stop paying, and Firefox would quickly die. Laws change.