Ask me how I know this? Most (99.999999%) people in China do not have the freedom to express themselves online safely. You meet them and ask them personally to know this kind of thing exists. Then you check the statistics from Chinese government about pension distribution, retired people with rural Hukou get the most discrimination from the government.

[1] https://statmodeling.stat.columbia.edu/2026/08/27/258

P.S. I saw keming and my mind went blank for a little while.

The 996 working culture in this page is actually *996.ICU*. "Work by '996', sick in ICU", an ironic saying among Chinese developers, which means that by following the "996" work schedule (9 am to 9 pm, six days a week), you are risking yourself getting into the ICU (Intensive Care Unit). [1]

Take a step further, do you want to overwork to death if you have other choices? One of the reasons behind 277k stars in 996.icu repo is that 996 working culture literally takes over every single corporations in China. With the downturn of China economy and the selective execution of Chinese labor law, in recent years, 996 becomes even harsher to labor force in China because there are more than overwork now, e.g. low salary and low human rights. When you say 'make the average consumer better off', you conveniently ignore the tears, sweets, and blood behind the facade of neijuan.

[1] https://github.com/996icu/996.ICU

> I asked when the first prompt had been sent by them. This question was not answered directly by OpenAI for some time. Eventually it was agreed that it had been sent in the past few days, after information about our work had reached OpenAI.

> I asked whether the model had been trained on, or had access to, our sessions in Codex, into which we had been putting all our drafts for the whole of this project. I was told the model did not look up user data. I asked again, about training, and I did not get an answer.

> Two proposals were offered to me. The first was that we post our Euler result, and that OpenAI post its Navier-Stokes result the next day. The second was that, after posting Euler, I alone write a paper presenting the Navier-Stokes result, acknowledging that an internal OpenAI model had resolved it. Sebastien twice asserted that he wanted Levent removed from authorship, and said it would all be simple if only it were not the case that, and it was so annoying that, Levent works at Anthropic. It was also said that if OpenAI posted after us, they would say that we deserved the Clay Prize, and that we were the “closest humans to the problem”. I declined both offers.

> I said that if OpenAI released its result in the way proposed I would go public with what happened. The reply was, “Why would you ruin your career?” I replied that I am an academic, and asked why he thought going public would ruin my career. The reply was, “If you don’t want me to be nice, then I don’t have to be nice.”

Wow, that's some VERY friendly communication. Besides, will the career of the person be ruined because of “Why would you ruin your career?” came out of his or her own mouth?

Performance-wise, I don't think diffusion decoding should be much worse than autoregressive decoding, see https://arxiv.org/html/2604.11035 .

As a local LLM user, I really want to see more small diffusion LLM/VLMs with decent performance coming.

Compared to closed weight (especially unreleased and access-limited) and open weight/source large sparse MoE LLMs/VLMs, open weight/source small dense models benefits public the most because they just reaches more people.

Compared to Qwen 3.6, 3.8's thinking style changed drastically. With xhigh budget, it thinks a lot MORE, and longer thinking session directly translates to better performance. This tradeoff between performance and computation, memory, etc. is meaningful to me.

However, because Qwen 3.6 and 3.8 share the same architecture, with 32GB vram, llama.cpp, IQ4_XS model, MTP and FP16 mmproj, I can only get 200k context, which is not good compared to 640k context of muse glimmer. Hopefully this problem will be solved in Qwen 4.0 release.

Now open weight LLMs/VLMs/LMMs are becoming even larger to the extent that consumer-grade hardware are no longer able to run these models. In contrast, quantization and pruning make the model better at the size-performance pareto and provide people with strictly more possibilities.

---

Whistleblower Yang Hai already reported Yang Youlin for his economic misconduct in July 2008. The whistleblower was detained because of the report at Nov 21st, 2008.

---

People's comment on this matter around March, 2009:

哇塞！终于有人敢动杨友林啦，杨海好样的。杨友林此人早该除无奈碍于他的势力。除掉杨友林大快人心。Wow! Finally, someone dares to take action against Yang Youlin. Good job, Yang Hai. That guy should have been dealt with long ago, but we were stuck with his influence. Getting rid of him is incredibly satisfying.

不杀此贪官，难平民愤。If you don't execute this corrupt official, you won't appease the public's anger.

江宁有一个传说，谁也动不了杨永林！There's a legend in Jiangning: nobody can touch Yang Youlin!

他的保护伞是谁？Who is protecting him?

希望引起中央的重视！I hope this gets the attention of the central government!

现在社会怎么啦？好多天了根本没人关注这件事？是上层没有看到？还是视而不见？还是怕牵连自己？What's going on with society lately? It's been days and no one is paying attention to this! Did the higher-ups miss it? Are they turning a blind eye? Or are they just afraid of getting dragged into it?

---

Since the report, there were several pieces of news about "the investigation about Yang Youlin is ongoing", but no real progress until 2023.

Basically, Microsoft logs things from windows users, including and not limiting to, the machine GDID, IPs that come with the GDID, and when and what exact URLs accessed. So for windows users, privacy, an important part of information security, is totally destroyed by these logs enforced on windows. Another important part of information security is bug fixing, and microsoft did make at least one security researcher angry [1].

And a simple solution to that problem is moving to linux. You save yourself a lot of time and energy for leaving the adversarial information security condition imposed by windows and microsoft.

P.S. You may consider debloating windows for a more information security friendly environment. However, that is nearly impossible, as long as you realize that windows is an OS composed of thousands of closed source softwares, and doing security audits on all of these will be costly.

[1] https://news.ycombinator.com/item?id=48315968

[1] https://searx.space

I won't say searxng can help you degoogle because metasearch engine calls other search engines, e.g., google, to collect results. However, if you try searxng, you can at least get rid of things like ai reviews in no time.

In the end, thank you people after searxng project and public instances.

[1] https://searx.space

[2] https://github.com/libredirect/browser_extension

[1] https://news.ycombinator.com/item?id=48067119

[2] https://news.ycombinator.com/item?id=48555244

Apparently this new swipe function is tied to FUTO keyboard. I don't use the FUTO keyboard as there is no support for the language I use intensively. Nevertheless, this line of work deserves more recognition.

If you want to strip some features from things we bought after the purchasing, you must ask me and every other customers for consents explicitly, with a reasonable explanation, and before the strip happens. If one of us show no consent, you cannot do that.

-------------

See the github issue [1]. @benkilpatrick found out the problem in April. There was absolutely no consent asking information transparency at all. There was inefficient to no information even for people willing to spend THEIR OWN TIME to solve the problem. After about two months of back and forth with motherboard manufacturer, @benkilpatrick found out the problem stems from some components inside the bios, and the components came from AMD. Another ~three weeks passed and no problem resolution at all. It was after things blow up AMD PR came out and said something about "valuable feedback".

Wait, what if there's no enough pushback? What if this github issue as well as the problem it raised is ignored by all? Just see this thread, that thread [2] and whatnot. Is your customers going to screw themselves and being stripped silently for being your customers and believing that new bios will solve their problems without causing shenanigans?

-------------

I won't upgrade bios without future third-party bios integrity checks showing the problem is solved properly.

[1] https://github.com/AMDESE/AMDSEV/issues/292

[2] https://news.ycombinator.com/item?id=48582320

Silent enshittification in the name of updates is getting out of hand. There are several evidences that downgrading BIOS/AGESA to below 1.2.7.0 to 1.2.0.3 brought back TSME for their AMD cpus.

I downgrade my bios as a price for my blind trust on AMD, and yes TSME is back.

You lost my trust AMD. The lesson learned is that if your PC with AMD cpu is stable, don't do any bios upgrade, as AGESA in the bios is adversarial to you, the users of AMD cpu.

Because of ungoogled-chromium, I'm used to manually update the browser. This time I won't update until MV2 problem is solved properly. I've already lost my extensions once by updating to 138 without checking google's adversarial move, and got the forbidden knowledge that I cannot manually downgrade chromium because it won't start.