Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)S
Posts
19
Comments
326
Joined
3 mo. ago

  • Can we talk shop? I don't want to come across as badgering you if you're happy to put a pin in it, but I think this is a bad take. Like, if you're going to try and solve this with Regex soup and spite, it's going to hurt.

    What happens if Codex, Claude, Cursor, LLM or phrases like "machine learning", "generative ai" etc are mentioned?

    Or when someone wants to have a discussion like this?

    \bAI\b will miss almost all of it.

    Note: I have no stake in you using or not using AI, an I am not trying to convert you to the church of Latter day Aiology. I am simply trying to []avoid doing real work[] chat.

  • I'm midly curious as to how.

    How would (say) you using Qwen 3.5 4B be bad for you (specifically) in this case?

    Qwen's open weights, already trained, runs locally on your rig, doesn't leak PII to the cloud and does the job.

    Surely if AI discussion in feeds is causing grief, anything that removes that for you (your stated intention) is "good" for you?

  • Hey, even Che Guvera wore a Rolex. :)

    PS: I think you're circling something though - people are objecting to the idea of what they think AI is, based on emotional appeal. It's a category error.

    As in - you know damn well that the correct tool for sentiment analysis is an AI but you'd rather avoid using it because ... whatever.

    It's that "because whatever" I'm pointing at, because right now it's unexamined and at best scores you a pyrrhic victory. Sentence transformers, rankers and re-rankers are AI, the right tool for the job and you won't use them because.... Ai bad.

    (You in the general sense, not you you).

  • Fucking snake assholes, amirite? Kill em all.

    PS: I see you Jake Sully.

  • @curbstickle@anarchist.nexus - as per your suggestion, here is the AI tags discussion, which I imagine you've been eyeballing.

    I don't know where this leaves the community, nor how many responders are part of the community vs lookie loos. I would have put up a staw poll but that likely wouldn't have helped much, signal:noise wise.

    As the mod, do you have a read on all this or a preferred direction going forward?

  • Ironically...ai is probably an excellent tool to prefetch your content, perform sentiment analysis and then sanitise the content to your liking.

  • I'm up voting this twice.

    [DOUBLE RAINBOW]

  • Sure. And while I'm doing that, you might like to google Poe's Law.

    Edit: you know what - I over reacted there and I apologise. Child slavery is a hot topic button and my head went to a weird place. I'm not going to uncook the chicken by deleting my post but I will admit I probably read it wrong at 5AM.

    I stand by my read that their post was deliberately inflammatory framing, but it probably wasn't intended as a "so, when did you stop beating your wife".

  • I'm sorry, what? Did you just equate AI use to actual child slavery?

    I don't even know how to begin to respond to that.

    Your analogy is irrational and frankly disgusting. Blocked.

  • Oh you wanna snark?

    Sure, let's just tag everything then. 97% of projects tagged. (I cited 2 sources to back that number up btw and I resent your implication that I made it up out of whole cloth).

    Boom - done. You wanted all AI touched projects tagged, wish granted.

    Hey, let's tag posts with [USES ELECTRICITY] too while we're at it. That'll be equally fucking useful.

    People don't want an [AI] tag. They want a [SLOP] tag. Guess what - they can't have it.

    Do you think slop merchants will tag their posts with [SLOP]? No?

    Do you need a tag to detect slop code? No? Then what the fuck is the point of tagging anything?

    [AI] and [SLOP] aren't in the same universe, and a tag can't distinguish them.

    You're going to have people honestly trying to disclose AI use, only to get heckled, because Lemmy is so delightfully unbiased on anything AI.

    Brilliant - that will do wonders for engagement.

  • Right?

    To be clear - I don't know how to solve this problem, or how big the problem is.

  • Good question - and that's another problem. Not sure - can't see any in Voyager. Can you see any on your end?

  • What does this mean? Are you saying we all have different tolerances and preferences for how much we value digital sovereignty?

    Are you suggesting that we are all at the mercy of the Powers that Be and that they "turn the dial"?

    Let's use SearXNG as framing device.

    SearXNG is a metacrawler. It's not a search engine, it's an aggregator. People talk about it like it's a search engine but it's not.

    Which means your operation of it is beholden to others (quite a lot in that case). Sure, you control the hop. You don't control what's upstream of it. Whoever you use still gets pinged. Eg: Google still gets queried. Bing still gets queried.

    You've added privacy at the point of entry, not independence at the point of source. What they do affects you directly, whether you want it to or not.

    That's something to think about if sovereignty is a concern.

    Same issue with pi hole, email, VPN on VPS etc etc.

    One thing I think would have helped would have been to indicate that your topic is AI-focused. For me, I went into the reading with the impression that you were talking about self-hosting in general.

    It's not (just) about AI. It's the same pipeline. Frontier lab to local LLM. Upstream (Google) to downstream (SearXNG).

    In both cases you're running your own endpoint against infrastructure you didn't build, can't audit and can't influence.

    Self-hosting the bottom of the stack doesn't change what's at the top of it, and that's exactly the problem....because the top directly influences the bottom.

    The dependency just sits further back in the chain.

    The chains bottom out at the same chokepoints - a handful of labs, a handful of infrastructure providers, a handful of index owners. No man is an island.

    Anyway, I didn't really want to pre-digest it this much, so I framed the post to allow out loud thinking in which ever direction it goes. This was not meant to be an exercise in "here's what I think, fite me", it was an invitation to think out loud together.

  • "vast majority don't want AI anything" is doing a lot of work there. Do they not want AI autocomplete in the IDE? AI-assisted translation? AI-generated test cases? Because if the line is "any AI involvement," the tag eats almost everything. If it's something narrower, we're back to: define the threshold.

    This is a question about trust. That's a hard problem because it assumes X is innocent, Y is guilty. I'm saying X and Y are both equally guilty (or innocent) until proven otherwise and Z (slop) can be summarily executed.

  • Treating a category of content as inherently suspect based on how it was made, rather than whether it's any good. Having one tag [AI] puts a giant target on the post.

    Thing is, the tag isn't neutral metadata, it's a flag.

    And if 97% of projects have touched AI tooling in some form (who knows how deeply), you're not tagging outliers anymore, you're tagging the norm and implying everything untagged is the clean option.

    That's not curation, that's a vibe-based blacklist.

    I'm for "trust, but verify" - tagged or not. And the tagging won't work because 1) what is AI coded any more 2) do you need the tag to spot slop (which is what I think people mean by [AI])

  • Fair. So we're talking about slop - and to that I agree.

    Next question then becomes: does [AI] meta-tag in any way help you discern slop from non slop? There are comments and proposals in favour of it.

    The counter argument is - slop is obvious...and even if it isn't (and you're going stick the thing on your own rig), you should probably do your due diligence first...which will uncover issues.

    At which point, a scarlett letter isn't going to do anything useful, and may unfairly tarnish projects.

    That 97% stat was from 2 years ago. It's surely higher now.

    I don't think [AI] tag works, for a number of reasons, as others have identified. But the topic keeps popping up here and there, so it's worth mulling over.

  • The post was fodder to stimulate discussion, but to make it clearer -

    [1] Self-hosting gives you real but bounded sovereignty.

    [2] You control your stack, but not the foundations it runs on.

    [3] Even the most committed local-AI person is downstream of decisions made by a handful of people in boardrooms they'll never enter.

    [4] "Fuck you, I won't do what you told me" is worth defending, but it has a ceiling, and that ceiling is getting lower as AI consolidates upstream.

    [5] That holds for self hosting anything else.

    [6] The community sometimes talks about sovereignty like it's binary, but it's a dial, and we should be thinking harder about who's turning it.

    [7] Finally, i am pro self hosted AI. I am also an AI critic.

    Clearer?