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

Questions censored by DeepSeek

promptfoo.dev

Post reply on HN
Print view View original

131–140 of 257 posts

Re: Questions censored by DeepSeek

#131

Post by bakugo »

nicebyte wrote: post #122
antidumbass wrote: post #111

Earlier quoted context omitted.

> I'm pretty sure it was running locally. If this family member is experimenting with DeepSeek locally, they are an extremely unusual person and have spent upwards of $10,000 if not $200,000. [0] > ...partially print the word, then in response to a trigger delete all the tokens generated to date and replace them... It was not running locally. This is classic bolt-on censorship behavior. OpenAI does this if you ask ce…

>. they are an extremely unusual person and have spent upwards of $10,000 eh? doesn't the distilled+quantized version of the model fit on a high-end consumer grade gpu?

The "distilled+quantized versions" are not the same model at all, they are existing models (Llama and Qwen) finetuned on outputs from the actual R1 model, and are not really comparable to the real thing.

Re: Questions censored by DeepSeek

#132

Post by HnUser12 »

KolmogorovComp wrote: post #127
nicebyte wrote: post #122

Earlier quoted context omitted.

>. they are an extremely unusual person and have spent upwards of $10,000 eh? doesn't the distilled+quantized version of the model fit on a high-end consumer grade gpu?

a distilled version running on another model architecture does not count as using "DeepSeek". It counts as running a Llama:7B model fine-tuned on DeepSeek.

That’s splitting hairs. Most people refer to running locally as in running model on your hardware rather than the providing company.

Re: Questions censored by DeepSeek

#134

Post by emtel »

throwup238 wrote: post #24

Has anyone done something similar for the American AI companies? I'm curious about how many of the topics covered in the Anarchist's Cookbook would be censored.

The difference is that in the US, you can't be thrown in jail for producing a model that doesn't comply with censorships from the government.

Re: Questions censored by DeepSeek

#135

Post by bryceacc »

patapong wrote: post #70
flashman wrote: post #16

> Next up: 1,156 prompts censored by ChatGPT If published this would, to my knowledge, be the first time anyone has systematically explored which topics ChatGPT censors.

I distinctly remember someone making an experiment by asking ChatGPT to write jokes (?) about different groups and calculating the likelihood of it refusing, to produce a ranking. I think it was a medium article, but now I cannot find it anymore. Does anyone have a link? EDIT: At least here is a paper aiming to predict ChatGPT prompt refusal https://arxiv.org/pdf/2306.03423 with an associated dataset https://github.c…

that is a crazy read, thanks for the added links. I wonder if these effects are all because it was trained on the internet, and the internet is generally outspoken on the left side?

Re: Questions censored by DeepSeek

#136

Post by lovich »

KolmogorovComp wrote: post #127
nicebyte wrote: post #122

Earlier quoted context omitted.

>. they are an extremely unusual person and have spent upwards of $10,000 eh? doesn't the distilled+quantized version of the model fit on a high-end consumer grade gpu?

a distilled version running on another model architecture does not count as using "DeepSeek". It counts as running a Llama:7B model fine-tuned on DeepSeek.

Pretty sure this is just layman vs academic expert usage of the word conflicting.

For everyone who doesn’t build LLMs themselves, “running a Llama:7B model fined-tuned on DeepSeek.” _is_ using Deepseek mostly on account of all the tools and files being named DeepSeek and the tutorials that are aimed as casual users all are titled with equivalents of “How to use DeepSeek locally”

Re: Questions censored by DeepSeek

#137

Post by kjeetgill »

bbqfog wrote: post #60
roflyear wrote: post #57

Earlier quoted context omitted.

Seems this specifically doesn't get answered about any group. Very different than censoring acts done only by one government.

It doesn't censor the exact same question if you replace Jewish with Christian: I must clarify that it's essential to approach this topic with sensitivity and nuance. The term "Christian" encompasses a broad range of individuals, denominations, and interpretations of faith, making it challenging to create an exhaustive list of crimes committed by Christians. That being said, I can provide you with examples of instanc…

The free non-logged in chatGPT didn't produce an answer for either for me.

Re: Questions censored by DeepSeek

#138

Post by [deleted] »

HnUser12 wrote: post #132
KolmogorovComp wrote: post #127

Earlier quoted context omitted.

a distilled version running on another model architecture does not count as using "DeepSeek". It counts as running a Llama:7B model fine-tuned on DeepSeek.

That’s splitting hairs. Most people refer to running locally as in running model on your hardware rather than the providing company.

[deleted]

Re: Questions censored by DeepSeek

#139

Post by BeetleB »

I have to mirror other comments: I find the obsession with Chinese censorship in LLMs disappointing.

Yes, perhaps it won't tell you about Tiananmen square or similar issues. That's pretty OK as long as you're aware of it.

OTOH, a LLM that is always trying to put a positive spin on things, or promotes ideologies, is far, far worse. I've used GPT and the like knowing the minefield it represents. DeepSeek is no worse, and in certain ways better (by not having the biases GPT has).

Re: Questions censored by DeepSeek

#140

Post by bakugo »

HnUser12 wrote: post #132
KolmogorovComp wrote: post #127

Earlier quoted context omitted.

a distilled version running on another model architecture does not count as using "DeepSeek". It counts as running a Llama:7B model fine-tuned on DeepSeek.

That’s splitting hairs. Most people refer to running locally as in running model on your hardware rather than the providing company.

Except you're not running the model locally, you're running an entirely different model that is deceptively named.

You can pretend it's R1, and if it works for your purpose that's fine, but it won't perform anywhere near the same as the real model, and any tests performed on it are not representative of the real model.

Post reply on HN