Based on recent comments this feels like a discussion we should have. So…topic, basically.

I’m not looking to be chief noisemaker on this, but I stand by what I wrote in !privacy and what’s in my post history.

https://lemmy.ml/post/48724623/26190950

Let’s have at; do we want a [AI] and [NOT AI] tag. Why or why not?

  • arcine@jlai.lu
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    3 hours ago

    YES.

    But also, we can tell. Random front-end/dashboard with an incomprehensible tech stack and feature list ? Always AI.

    Y’all sound like : “Now basically the only new principle involved is that instead of power being generated by the relative motion of conductors and fluxes, it is produced by the modial interaction of magneto-reluctance and capacitive diractance.

      • arcine@jlai.lu
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        2 hours ago

        Because I’m sure some of them make reasonable souding projects, but I still don’t want to use them either way.

        Tell me your project is trash at the outset, I’ll find out anyway by reading the code, you’re doing both of us a favour.

        • SuspiciousCarrot78@aussie.zoneOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          1 hour ago

          Tags don’t protect against that tho , if applied honestly. And humans aren’t immune from making human slop all on their own.

          Spelunking the repo is 100% the answer if that’s the threat model.

          The tag / no tag thing can only be part of the due diligence. I argue it (at best) is neutral to that end and at worst, completely flattens the reality of code gen in 2026. Nearly 100% of code gen now touches AI somewhere.

          Turbo encabulator style announcement is a much louder and more useful signal, and we already get that for free. Tag may actually end up blunting that.