Yup, I’m posting another this week. Sorry.

This week I’m hoping we can wrangle a solution around AI and our selfhosted community. There are plenty of strong opinions (both pro and con), but one thing is for certain - there needs to be better disclosure in promo posts. Two options (that aren’t mutually exclusive):

  • Any posts of an AI focused, AI Developed, etc software gets an [AI] tag. No, a [Not-AI] tag is not needed to accomplish this, thats kind of a “non-golfer” sort of tag.
  • Comment requiring an AI disclosure response to every promo post, if its not detailed in the post itself. Specifics (generating docs for commands, translation, whole-boat vibe-coded this app, etc) would be requested.

I will say that having disclosure and/or tagging would mean that comments that just say “slop” or “fuck ai” or whatever would be off topic at that point, that information is already provided, so its just noise (and sometimes pretty uncivil - I’ve been light on that for now due to the need for a rule on this).

The tag [AI] would make it easy to filter out (or search for, if that’s your thing), but there is a wildly different degree of AI use out there, and from the posts with a positive score, its usually due to responsible AI use (translations, a snippet they had to do something obscure with, available to use with AI but doesn’t require it, whatever), which is why I think the disclosure has a place as a benefit to everyone.

Please provide any input or alternative options on this, and I can then put it to a vote like the last one. Comments seem to be the best approach without involving something off-site, but if you have a better idea/option, please share.

  • SuspiciousCarrot78@aussie.zoneEnglish
    2·
    3 hours ago

    What Ollama did what that distill is shameful.

    For those not in the know: they took a small, 8B model with Deepseek fine tune (Qwen3-8B iirc) and claimed it was the 400+B param Deepseek.

    They essentially tricked folks into thinking they were running a near-peer SOTA model at home when in fact they were running a small language model (SLM) with crippled settings (again, iirc, ctx -4096 by default).

    Lying via obfuscation is still lying.

      • SuspiciousCarrot78@aussie.zoneEnglish
        2·
        3 hours ago

        I think it’s actually a pretty interesting case study of how something from the open source community can get co-opted and fucked over.

        That article is a good read.

        As always, the game plan seems to be “disrupt, own the market, enshittify”.

        • brucethemoose@lemmy.worldEnglish
          2·
          2 hours ago

          As always, the game plan seems to be “disrupt, own the market, enshittify”.

          But with a slimy veneer of SEO/engagement spamming as the primary business strategy.