posted in Technology

eicker@eicker@lemmy.world

Alibaba’s AI model Qwen3.8-Max made widely accessible ahead of open-weights release: Flagship 2.4 trillion parameter model highlights native multimodal capabilities and ... agentic tasks.

www.scmp.com/tech/article/3362738/alibabas-ai-model-qwen38-max-made-widely-accessible-ahead-open-weights-release
South China Morning PostAlibaba’s AI model Qwen3.8-Max widely accessible ahead of open-weights releaseFlagship 2.4 trillion parameter model highlights native multimodal capabilities and the ability to carry out long-horizon agentic tasks.
cenariodantesco@cenariodantesco@lemmy.world

Replying to @⁨darkevilmac@lemmy.zip⁩

sharing is caring No Ollama man

Friends Don't Let Friends Use OllamaSleeping RobotsFriends Don't Let Friends Use Ollama | Sleeping RobotsOllama gained traction by being the first easy llama.cpp wrapper, then spent years dodging attribution, misleading users, and pivoting to cloud, all while riding VC money earned on someone else's engine. Here's the full history, and why the alternatives are better.
urushitan 漆たん@urushitan@kakera.kintsugi.moe
edited

Replying to @⁨elucubra@sopuli.xyz⁩

Lol I’ve been running linguistic research and it’s funny when they just combine two scripts together into one word

● The trigger is identified, and it’s specific.

agent_1.md:31 src: “Name the trade-off.” → 명取捨之名。 agent_2:32 src: “Name the regime.” → 명regime——名其regime。

The English imperative “Name the X.” And the corpus renders it correctly 16 other times — 名之 ×11, 名其 ×5, 命名 once.

명 is the Sino-Korean reading of 名. Same morpheme, wrong script.

And agent_2:32 is the cleanest evidence I’ve seen for 絡繰’s mechanism: the model wrote 명regime——名其regime — the wrong script and the correct one, eight characters apart, in the same clause. It isn’t ignorant of 名. It produced 名其 immediately after. The meaning resolved correctly both times; the script attribute resolved wrongly the first time and correctly the second.

That’s exactly what работ法 showed — correct semantics (work), broken script and morphology — and it’s the third confirmed instance of the class, now with a reproducible trigger rather than a one-off.

It also explains the Russian cases retroactively. document → документ, everything → всё, “correct” → правильно: in each, the meaning landed and the script didn’t. And it predicts why no CJK-native concept ever drifts — there’s no competing script for a morpheme the model only knows in Han.

Meron35@Meron35@lemmy.world

Replying to @⁨PetteriPano@lemmy.world⁩

Chinese being more token efficient is a myth, and seems to stem from the superficial fact that characters are only visually more space efficient.

The fact that each Chinese character takes up 3 bytes (as opposed to 1 byte of English), words in Chinese typically require compounds of several characters, and that tokenizers have a limited vocabulary limited to mostly English means that Chinese is actually token inefficient.

No, Chinese Is Not More Token-Efficient Than English for LLMs | markhuang.ai - markhuang.ai/blog/chinese-token-myth

markhuang.aimarkhuang.aiNo, Chinese Is Not More Token-Efficient Than English for LLMsA native Mandarin speaker tests the popular claim that Chinese characters save tokens when interacting with LLMs. Across six tokenizers — including Chinese-first models like Qwen, GLM, and DeepSeek — English uses fewer tokens every time. The data, the BPE mechanics, and why character count has nothing to do with token count.
PetteriPano@PetteriPano@lemmy.world

Replying to @⁨Meron35@lemmy.world⁩

I didn’t say it’s more token efficient. I said training multiple languages improves reasoning.

arXiv logoarXiv.orgBeyond English-Centric Training: How Reinforcement Learning Improves Cross-Lingual Reasoning in LLMsEnhancing the complex reasoning capabilities of Large Language Models (LLMs) attracts widespread attention. While reinforcement learning (RL) has shown superior performance for improving complex reasoning, its impact on cross-lingual generalization compared to Supervised Fine-Tuning (SFT) remains unexplored. We present the first systematic investigation into cross-lingual reasoning generalization of RL and SFT. Using Qwen2.5-3B-Base as our foundation model, we conduct experiments on diverse multilingual reasoning benchmarks, including math reasoning, commonsense reasoning, and scientific reasoning. Our investigation yields two significant findings: (1) Tuning with RL not only achieves higher accuracy but also demonstrates substantially stronger cross-lingual generalization capabilities compared to SFT. (2) RL training on non-English data yields better overall performance and generalization than training on English data, which is not observed with SFT. Furthermore, through comprehensive
unglueclass23@unglueclass23@programming.dev
edited

Replying to @⁨ComradePenguin@lemmy.ml⁩

This looks promising ! I am currently paying 10$ / month for this other service that is basically a front-end for openrouter. Was searching to switch since :

  1. Don’t like the founder and his braindead push for LLM’s.
  2. Everything is hosted in the US.
  3. I have cut back on my LLM usage by a lot, to the point that I don’t think I spend 10$ worth of tokens. GPT 20B , Gemma 4 27B and DeepSeek v4 flash end up being like 90% of my usage and I try to use them sparingly, keep answers, conversations short.

I do wonder what to do about the frontend? My mentioned service has a pretty good web app with decent UI and it worked on mobile as well without much problems. I actually end up using LLM’s quite often on mobile as I read a lot on it.