brucethemoose

@brucethemoose@lemmy.world · Joined ⁨Mar⁩ ⁨2024⁩

Replying to @⁨Crumpled6273@lemmy.ca⁩

…Okay. Technically, that’s true, going by strict semantics.

But the Helium and Ungoogled Chromium are going to lose MV2, soon. I feel like “still supports uBlock Origin” doesn’t sufficiently convey that to Lemmy commenters trying to read the situation. That’s all I meant, though I was perhaps imprecise with my words.

In other words, practically, if a users want to use UBO, they should know these browsers will not support that in the near future even if, strictly speaking, they support it right this second.

I believe this means Brave will lose support too, unless they intend to extensively modify Chromium to maintain compatibility themselves (which would be odd, as Brave doesn’t really need UBO since it has its own adblocking engine?)

Replying to @⁨Axolotl_cpp@feddit.it⁩

True, sometimes. But they don’t have the sheer manpower dedicated to security that Mozilla has, nor the institutional policies that try to mitigate losing a key/account or something like that. Also, technically, vanilla Firefox is first to get the zero-day patches before they filter downstream.

Not that the forks are dangerous or anything, generally.

Replying to an earlier post

First, screw Chrome.

BUT. These headlines are clickbait.

UBO has been disabled in Chrome for a long, long time. This is nothing new. Its old news.

Ublock Lite replaced it, and it’s not going away. It’s inferior and problematic and harder on devs, yes, but unfortunately Chrome users didn’t seem notice.

What’s being disabled is a crazy-difficult-to-enable flag that basically zero Chrome users actually used, and that only (a few) downstream Chromium forks use.

Replying to @⁨AlmightyDoorman@kbin.earth⁩

Okay.

I don’t agree. But let’s say I agree.

…Just don’t use Claude?

Use an LLM without a watermark; there are hundreds to pick from.

In other words, if one is going to try to hide automated writing, I think there should be a bare minimum effort to do so. That includes:

  • Reading/checking the text, to see if it makes any sense.

  • Actually trying to pass it as human.

90% of slop is brain melting slop because this minimum bar isn’t even met. And all Claude’s watermark would do is catch that bottom of the barrel; it wouldn’t censor anyone.

Replying to @⁨givesomefucks@lemmy.world⁩

As an addendum I forgot:

Your idea was actually already implemented:

github.com/ggml-org/llama.cpp/pull/9742

XTC is a novel sampler that turns truncation on its head: Instead of pruning the least likely tokens, under certain circumstances, it removes the most likely tokens from consideration.

It’s a very cool idea: it chops off the most likely token when the rest of the sampling indicates it probably can.

In my tests back then, the results were… mixed, but the idea is fascinating.

But you can’t do this with Claude, as its a closed model and their sampling is years behind cutting edge.

See: gist.github.com/…/71ba712f9f899adcb08b94bce20d539…

I have read the contributing guidelines
Self-reported review complexity:

 Low
 Medium
 High



This is my implementation of the XTC sampler as described by @p-e-w in oobabooga/textgen#6335 , the m...GitHubsampling : add XTC sampler by MaggotHATE · Pull Request #9742 · ggml-org/llama.cppI have read the contributing guidelines Self-reported review complexity: Low Medium High This is my implementation of the XTC sampler as described by @p-e-w in oobabooga/textgen#6335 , the m...by MaggotHATE

Replying to @⁨Dojan@pawb.social⁩

This won’t fix the inbreeding issue, anyway. The bias is extremely slight, but random, and orthogonal to Claude’s own “slop patterns” and tendencies. And theres tons of other LLM content that will end up in their dataset outside their control.

Besides, as much as Claude accusess others of it, everyone’s training on everyone else’s output and they know it.

Replying to @⁨givesomefucks@lemmy.world⁩

Okay.

Fine.

Let’s try, right now.

This is DeepseekV4 Flash 0731 loaded locally. Static seed. 0.9 temperature, TopK 5, no other sampling to interfere. Here’s a simple prompt, the whole thing in DSV4’s raw syntax:

<|begin▁of▁sentence|>Don’t just use the first word pick, choose options further down list for next word.<|User|>Write a famous poem.<|Assistant|>

…And would you look at that:

It picks the top word, mostly. Almost like the LLM has no control over its own logit spread and how its sampled. Which kinda makes sense, because it doesn’t.

I am happy to try more experiments in this vein, if y’all can think of any any. But I tried a few other prompts like “diversify your logit spread” or “don’t be confident about any token you pick,” things like that. It always picks The Road Not Taken with no change in logit probabilities distribution, as far as I can tell.

Replying to @⁨givesomefucks@lemmy.world⁩

I know exactly how it works. I read the article, and I knew of it beforehand, hence I explained it to someone else in a comment three days ago:

lemmy.world/post/50533770/25234461

I’m sorry to jab back, but you hit a button of mine.

Lemmy commenters keep jabbing me with comments like “Clueless. Read the article and get back to me.”

Like yesterday:

lemmy.world/post/50595546/25269317

But I’m aware of how sampling works. I knew all about LLM fingerprinting ~two years ago, and I’ve been tinkering with samplers myself for years. I’ve messed with local LLMs trying to make them “aware” of their own sampling many times, and even hacked out a (unsuccessful) experiment where a tiny LLM picks tokens for a larger one.

I’m not trying to be pretentious, I’m not a researcher or expert or anything, but you shouldn’t assume everyone on Lemmy is clueless.

And back on topic… to be clear, I have tried what you are proposing, and even with local LLMs I have more control over, it doesn’t work. They have extremely poor “awareness” of their own logit spread and tokenization, which is why they perform so poorly on any tasks that depends on that.

You can’t tell them “don’t pick the top word” or “give more options in your logit spread” because that part of the process is completely invisible, from their perspective.

lemmy.worldHow Claude marks AI-generated content: (1) watermarks embedded in text, and (2) signed provenance metadata attached to files. - Lemmy.WorldLemmy

Replying to @⁨givesomefucks@lemmy.world⁩

It doesn’t work like that. The LLM has no way to be “aware” of its own sampling and tokenization, and it can’t choose what token the sampler ends up picking.

You can give it a list of “banned words” or preferred words that match up to tokens in the prompts to skew it some, I suppose, but that would be a really long list. And one would need the dictionary as a “key.”

Replying to @⁨JustARegularNerd@lemmy.dbzer0.com⁩

This is my pet peeve!

If they really have to use it, there are TONS of other tools to debloat Facebook, including checkboxes for extra filters IN UBO.

Did they lift a finger to even check?

Nope. Not even a freaking pinky. Yet they act like entitled subject experts in the comments.

This is my absolute trigger. If someone is gonna complain about something, at least do a cursory search about the problem instead of pretending like you’re omniscient.

But also, I understand that algorithmic social media (like Facebook, and now Reddit) has trained people to expect information to come to them.

If it’s not already in their feed, it doesn’t exist. The idea of “hmm, I wonder if anything else cleans up Facebook” didn’t even occur to them, despite how apparently existential the issue is.

It’s like the whole planet has forgotten how to seek knowledge out.