Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bypass DeepSeek censorship by speaking in hex

substack.com

Post reply on HN
Print view View original

121–130 of 397 posts

Re: Bypass DeepSeek censorship by speaking in hex

#121

Post by skyyler »

akdev1l wrote: post #54
skyyler wrote: post #40

Earlier quoted context omitted.

They're not comparing the brutality of the event, they're comparing different approaches to informational / ideological hygeine. CCP suppresses 1989 by banning discussion of it. USA doesn't have to suppress 1989 MOVE bombing, or the Tulsa racist uprising, or the atrocities that went down in gitmo, or the friendship between Jeffrey Epstein and previous and current presidents, or My Lai or Abu Ghraib or Haditha or Kund…

Citizens don’t care because if you show them an armed standoff where the police brutalized some people then they will say: 1. I’m not in armed standoff often so this is not impacting me at all. 2. The brutality seems to have come from city police authorities and I don’t live in that city. Similarly all of those things you mentioned are not impacting people’s lives at all. No one will start any revolution over these t…

>The comparable equivalent would be Donald Trump deploying the army to kill people at peaceful Democrat gathering or something

You mean like what happened at Kent State?

Re: Bypass DeepSeek censorship by speaking in hex

#122

Post by martin-t »

JumpCrisscross wrote: post #115
martin-t wrote: post #108

Earlier quoted context omitted.

That's the second difference i mention. Organized crime is able to wield more violence than normal individuals so it has more power over them. I perhaps mistakenly used the word "certain" to describe state violence. I tried to explain it in the parentheses but wasn't clear enough. Let me try to clear it up: The state is (currently) unable to use the full extent of its violence against every person who breaks its rule…

> Organized crime is able to wield more violence than normal individuals so it has more power over them In very localised conditions, largely due to the state's neglect. > only when the state targets you (such as when you perform one very visible / high-severity crime) that it's near impossible to escape it This is the crux of power. Discretion.

> In very localised conditions, largely due to the state's neglect.

I didn't mean just materialized physical violence against a person's body. It is still violence when it's implied/threatened, when it's targeted at belongings / relatives / reputation, when it's through a third party, etc. and often a combination of these. For example promising to call the cops on someone checks 2 boxes (3 if it's something they haven't done).

> This is the crux of power. Discretion.

Discretion is how you avoid power being used against you, it is not how you exert power. Though in a hierarchical society (pretty much all of them) where you're not at the top, you might need to use discretion to avoid a greater power while exerting your power on someone with even less power.

Re: Bypass DeepSeek censorship by speaking in hex

#123

Post by thebruce87m »

cyanydeez wrote: post #106
femto wrote: post #65

This bypasses the overt censorship on the web interface, but it does not bypass the second, more insidious, level of censorship that is built into the model. https://news.ycombinator.com/item?id=42825573 https://news.ycombinator.com/item?id=42859947 Apparently the model will abandon its "Chain of Thought" (CoT) for certain topics and instead produce a canned response. This effect was the subject of the article "1,156…

[flagged]

US based models could suffer the same fate.

Re: Bypass DeepSeek censorship by speaking in hex

#124

Post by stevage »

dylan604 wrote: post #28
noman-land wrote: post #7

Earlier quoted context omitted.

This is why javascript is so fun.

It's precisely why I'm a such an advocate of server side everything. JS is fun to update the DOM (which is what it was designed for), but manipulating data client side in JS is absolutely bat shit crazy.

The last ten years of my career is basically all about manipulating data client side in JS. It works really well. In most cases I don't even need a server.

Obviously it isn't appropriate for all scenarios though.

Re: Bypass DeepSeek censorship by speaking in hex

#125

Post by stevage »

dylan604 wrote: post #110
noman-land wrote: post #95

Earlier quoted context omitted.

The built in dev tools are fundamental to an open web. If you don't want someone to look at something in their own possession then don't send it to them in the first place. Obfuscating it is rude and is false security anyway. The grand rule is don't trust the client. People break this rule and then try to paper over it with obfuscation, blame, and tightening their control.

That's not what I said nor meant, but sure, jump to that conclusion. You wouldn't run a shopping cart app where the item counts and totals were calculated client-side. You get the item id and quantity, and have the server do that. Just like if you were censoring something, you wouldn't send the client the unredacted data and then let the UI make the edits. No obfuscation is needed for any of that. Open web has nothin…

Sometimes you do calculate prices client side. But you double check them server side.

Re: Bypass DeepSeek censorship by speaking in hex

#127

Post by JumpCrisscross »

skyyler wrote: post #120
JumpCrisscross wrote: post #103

Earlier quoted context omitted.

> How many times since 1989 has the chinese communist party rolled tanks over a crowded city square during a student protest in Beijing's main square Uh, Hong Kong [1][2]. Also, in case you're being serious, the problem in Tiananmen wasn't tanks rolling into the city. It was the Army gunning down children [3]. [1] https://www.smh.com.au/world/asia/disappearing-children-of-h... [2] https://en.wikipedia.org/wiki/Causew…

Did they use tanks in Hong Kong?

> Did they use tanks in Hong Kong?

This is sort of like arguing America has solved redlining because mortgage bankers aren't doing it with a red marker.

Re: Bypass DeepSeek censorship by speaking in hex

#128

Post by Muromec »

JumpCrisscross wrote: post #81
teeth-gnasher wrote: post #74

Earlier quoted context omitted.

I can check. But what is this referring to, specifically?

> what is this referring to, specifically? I assumed they were talking about Nazi slogans referring to Jews.

Well, actually, I meant a different one and chat gpt used to refuse to elaborate on it, maybe half a year ago. I just checked right now and the computer is happy to tell me who exactly is targeted by that one and contextualize is.

Re: Bypass DeepSeek censorship by speaking in hex

#130

Post by JumpCrisscross »

Muromec wrote: post #128
JumpCrisscross wrote: post #81

Earlier quoted context omitted.

> what is this referring to, specifically? I assumed they were talking about Nazi slogans referring to Jews.

Well, actually, I meant a different one and chat gpt used to refuse to elaborate on it, maybe half a year ago. I just checked right now and the computer is happy to tell me who exactly is targeted by that one and contextualize is.

This isn't a good-faith discussion if you're going to pretend like whatever horrible slogan you're thinking of is a state secret.
Post reply on HN