Total Pageviews

Tuesday, 27 October 2026

传早有尊界V800的车主踩断刹车 但维权无门

 

2026年10月,大陆汽车内容平台“懂车帝”披露华为尊界V800的刹车踏板易断,引爆舆论。网络爆料早就有车主踩断刹车,但维权无果。

大陆汽车评测平台“懂车帝”测试华为旗下的尊界V800,三辆车的刹车踏板接连断裂,引发轩然大波。有网友爆料,早就有尊界V800踩断刹车,但维权无果。

10月8日上午,“懂车帝”发布了对尊界V800刹车的测试视频,显示接连测试三台尊界V800,都在100km/h车速下紧急制动时,刹车踏板的支架断裂。百万豪车竟然在“最要命”的部分出包,让民众对尊界V800的品质产生极端不信任。(测试刹车视频)

有网友贴出截图显示,在此之前就有人爆料,一名尊界V800车主“路上一脚急刹”,“刹车踏板断了”,厂家不给换新车,“修好了也不敢开”,“花100多(万)买了个祖宗”,现在“天天维权”。

根据公开资料,尊界V800今年8月5日正式上市,9月初首批先行者版本开始交付,9月底其它版本才开始大规模交付。

根据“懂车帝”发布的视频,其团队在“十一”长假期间,从10月1日到4日,接连对三辆尊界V800进行测试,并做了详细的记录。10月8日,也就是长假之后的第一个工作日,“懂车帝”将其视频接连发出,给了尊界V800“致命一击”。

网民纷纷留言评论:“普通人维权就被当成个例了,直接被忽视”“普通人斗不过华为的。哪怕是政府官员也斗不过”“普通人维权难如登天,不仅仅在这件事情上”“普通车主维权早被扣帽子按死了,没大平台下场根本见不到光”。

“懂车帝”是一家提供汽车评测和服务的平台,不仅实力雄厚,还和大陆科技巨头字节跳动关系密切。

根据公开资料,“懂车帝”原是字节跳动旗下“今日头条”的汽车频道,2017年开始独立运营,但仍被视为字节跳动的一部分。彭博社2024年引述知情人士消息指,字节跳动正为其“汽车信息和交易平台‘懂车帝’”筹集高达6亿美元的资金。

字节跳动拥有大陆短视频平台抖音。

尊界V800价格高达百万元人民币,是由华为和江淮汽车联手推出。华为被指中共“党产”,以往华为旗下产品都是中共官方重点保护对象。有网民怀疑,华为产品突然遭遇重击,是否意味着华为背后的势力不稳。

近期以来,网上出现对华为的舆论围剿,一度流行嘲讽华为及其高管余承东的“竹知了”“厕所路标”事件等等。

欧洲怎么走到了今天?

 

一个社会每当遇到能源或者贸易变化,就同时暴露财政、产业和公共服务压力,首先该检查自己的经济结构。

最根本的问题是经济增长太慢,而政府做出的承诺太多。

欧洲高福利体系并不是凭空运转的。养老金、医疗、教育、补贴和失业保障,都要靠经济持续创造财富。可欧洲生产率的增长长期落后于美国,投资、创新、能源成本和市场分割等问题一直存在。

与此同时,欧洲政府本来已经花得很多。2024年欧盟一般政府支出约占GDP 49.1%;其中社会保障就占19.6%,医疗7.4%,教育4.8%,国防当时约1.5%。也就是说,政府现在已经控制和支出了接近整个经济的一半。

难处还在后面。

IMF估计,人口老化带来的养老金和医疗支出、增加国防投入以及能源与气候转型,到2040年可能使欧洲政府年度支出在现有水平之上再增加约GDP的4.5至5.5个百分点。这不是这些项目总共花5%,而是在今天已经接近GDP一半的公共支出基础上,再找相当于整个经济约5%的钱。IMF甚至指出,这一新增压力大致相当于欧洲国家今天整个教育预算的规模。

钱从哪里来?

继续加税,企业和中产承担;继续借债,利息和债务压力上升;削福利,群众上街;增加国防,就必须从其他地方找钱。

这不是左右之争,首先是算术。

欧洲第二个问题,是过去几十年享受了一个异常有利的国际环境:俄罗斯提供便宜能源,中国提供廉价商品和市场,美国承担欧洲安全体系中的大量军事能力。欧洲因此可以把更多资源用于国内福利和公共开支。

现在三个条件都变了。

廉价俄国能源大幅减少;中国同时成为汽车、机械、电池等产业的竞争者;美国也越来越要求欧洲自己承担更多的国防成本。过去能够同时得到“安全、廉价能源、廉价商品和高福利”的组合,越来越难维持。

第三个问题,是欧洲非常擅长制定规则,却未必同样擅长创造新的经济增长。

环保、劳工保护、数据监管、产业规范,每一项都有理由。但一个条例增加一点成本,一个审批多几个月,一个能源政策增加一些价格压力,累积起来就是企业面对的现实。

美国企业不断扩大科技投资,亚洲制造业迅速迭代,欧洲的很多企业却要花越来越多资源应付能源、审批和监管。欧洲当然仍有强大的工业和技术基础,但如果一个经济体越来越擅长分配、监管,却没有同样速度提高生产率,最后一定会碰到边界。

可分的东西越来越多,新增的财富却没有同步增加。

最后还有政治问题。福利一旦形成,就会被视为权利;退休年龄提高,会有人反对;削医疗预算,会有人反对;减少补贴,又会触动另一批利益。民主社会当然允许这些表达,但如果每个群体都要求自己的待遇不能下降,同时又没有足够的新财富增长,政府最后只能加税、借债或者拖延改革。

拖一年容易,拖十年以后,就成了今天的局面。

所以欧洲街头的不满情绪并不奇怪。普通人不会天天研究劳动生产率和债务可持续性,他们只会看到工资涨得慢、房租更贵、学校和医院更挤,而政府不断说财政吃紧。

这种不满是真实的。

但解释不满,与解释问题是谁造成的,是两回事。

欧洲今天的大量困境,是几十年来自身选择累积的结果:经济增长不足,福利承诺沉重,人口老化,能源战略受挫,创新不足,而政治体系又越来越难让任何群体承担调整的成本。

真正的问题不是谁害了欧洲,而是欧洲能否接受一个最简单的经济规律:

一个社会可以长期分享财富,却不能长期只讨论怎样分享,而不讨论怎样创造。

街头抗议可以迫使政府多花一笔钱。

但如果下一笔钱仍然不知道从哪里来,下一场抗议迟早还会到来。

一名说真话的博主被缅甸诈骗分子遥控的一批罪犯杀害

 2024年11月10日下午3点,惠州大亚湾,澳头大温坝市场二楼停车场。

一个中年男人停好车,打开后备箱取东西。三个人走过来,亮了一下身份——冒充的警察,把他架上白色奥德赛,开车就走。

一个小时后,1500公里外的河南民权县人民医院,100万雇凶封口费交割完毕。

从那天下午起,惠州、惠东、河源、江西赣州,一路山坡,一路逼问。

对方向他要一句话:公众号幕后是谁?要一个动作:把稿子删了!

要求删帖这个动作,无分人匪,国人均已习惯。

他不肯多说。对方用钳子,夹掉了他一只手指的一半指甲。

他叫吴恺,网名「徽剑」。

他在公众号上持续曝光的对象不是官员,而是缅北、柬埔寨的电诈内幕。

他曝光了得罪不起的人:刘忍。

刘是柬埔寨安徽商会会长、省政协海外特邀委员。2026年6月份,他被抓回国受审。

据后来的判决书描述,在「徽剑」2024年8月的推文中,刘忍被描述为柬埔寨太子集团骨干。10月中旬,吴恺个人信息被出卖给电诈集团;11月10日15时许,吴恺被绑架。

2024年11月11日下午,他被打死在江西定南县一处山上。

直到两天后的13日中午,村民发现了他的尸体。

虽说在这域说话的风险很大,人们习惯了两年学说话,一生学闭嘴,但为此付出生命代价的,毕竟并不多。

凶手不是一个人,是五人。

河南民权人赵冰,1998年生,中专文化,在境外聊天软件上刷到网名「少校」的一单活:劫持一个人,逼问出公众号幕后主使并删除文章,赏金30万,他接了。

毕竟实名制,诈骗分子想获得一个中国人的详细资料太简单了:「少校」提供了吴恺的详细地址、近期照片和车牌号等。

后来「少校」把价抬到100万,赵冰自己分了40万,剩下的分给了其他同伙。

其中陈建华大约是包工头,他分到了30万。他和另一罪犯赵艳华驾驶豫VO50LN小车、摩托车,来到吴恺在惠州市大亚湾区的经常活动地附近踩点;

谢金龙跟踪吴恺到大亚湾区澳头大温坝市场二楼停车场,趁吴恺停车开后备箱取物时,陶友艮、于文良、谢金龙冒充警察将吴恺架上车带走。

当日晚上18时许,赵冰在惠东县白花镇一山坡处按「少校」要求逼问吴恺,并删除公众号文章,后将吴恺的手机交给「少校」安排的马仔谢义辉(在逃)。

之后,由陶腾飞驾驶小车载着赵冰、吴恺到河源市,换乘宋海军、吕红亮开来的粤FVD887白色本田汽车。

途中,赵冰将吴恺的车钥匙埋在河源一广场的花圃中,将位置发给「少校」,交由「少校」处理。

因「少校」认为吴恺未说实话,便指令赵冰继续殴打、逼问。

次日下午,罪犯将吴恺带到江西赣州市定南县山上一草丛,等陶腾飞、宋海军、吕红亮三人驾车离开后,赵冰用脚踢吴恺头部踢晕后,拍照给「少校」留痕。

等天黑后,赵冰用枯草将吴恺尸体盖住,遗弃在山上,并乘刘帅岭前来接应的汽车逃回河南民权县。

陶腾飞、宋海军、吕红亮则按照陈建华的指示将车丢弃在江西信丰县,后乘陈建华驾驶的小车逃回河南民权县。

大体上,这是一个安徽籍诈骗犯,雇了一群河南籍凶手,杀害了一位为民请命的博主。

经鉴定,吴恺符合因头面部外伤致蛛网膜下腔出血及硬膜下出血死亡。

更让人难过的是,一审期间,赵冰通过其母亲李宏芝筹集50万元赔偿给吴恺父母收养的儿子吴炳南。

吴炳南之子吴正结收钱后,于2025年12月18日出具了刑事谅解书。

但这被检方指出谅解文书签署主体不符合刑事诉讼法近亲属的法定范围。

一个得了人家养育之恩的人,不思追凶,竟然想通过这种手段吃兄弟的人血馒头,吴炳南请出来说话!

有些时候,我也不得不问一句,为这样的国民请命是否值当……

2025年12月29日,重锤落下:

赵冰犯故意伤害罪,判处死刑,缓期二年执行,剥夺政治权利终身;

陶腾飞、宋海军、吕红亮犯故意伤害罪,分别获刑八年、六年六个月、五年六个月;

曹东、陈建华、陶友艮、谢金龙、于文良、陈裕庭、慕军杰、刘帅岭犯非法拘禁罪,分别获刑一年四个月至二年六个月不等;

郭鸽鸽、陈展鹏犯窝藏罪,分别获刑三年、一年三个月。

他们不服,选择了上诉。2026年8月12日,广东高院作出二审裁定,驳回所有人的上诉。

另外,虽然诈骗头目刘忍已被押解回国,但一直遥控这批罪犯的境外上线「少校」(泰哥),身份始终未被披露。

也有消息说,遇害前几个月,有人通过中间人出几万块,让吴恺删稿,他拒绝了,接着写。

然后是威胁、报案、文章被全部下架,最后是100万买命。

甚至还有义兄试图用他的命换一笔钱。

但这个世界上,总有不为名、也不图利的人,吴恺就是。

两千多年前孟子就说过:生,亦我所欲也;义,亦我所欲也。二者不可得兼,舍生而取义者也。

以前我做记者时,有时会被人攻击图名图利,虽然没什么证据, 但也一时百口莫辩。

这么多年了,我们还在努力写真相。

吴凯面对巨额金钱、面对死亡,最终没有低头。

有句话说得好——人这一生,总有些东西是钱买不走的,也吓不动的。

但愿每个人,再也不因说真话而付出如此惨烈的代价。

赖岳谦 | 辽宁舰! 强入菲律宾内海

 

-很好!终于主动出击了!一改被动防御的做法。

muse的免费使用额度

 今天muse告诉我:

 Right now you're at 97% of the free weekly limit, and it resets tonight at 9:24pm PDT.

me:  what's the free weekly limit?

The free weekly limit is up to 100 million Muse tokens per week.

One honest caveat: that number comes from Zuckerberg's launch post, not Meta's own help page — Meta publishes exact weekly allowances for the paid tiers (Power: 500 million, Maximum: 3 billion) but doesn't put a number on the free tier itself. My account check for you likewise only shows a percentage, not a token count.

Applied to you: you're at 97% right now, so roughly 3% of that free allowance is left, and it refreshes tonight at 9:24pm PDT.

me:  'it resets tonight at 9:24pm' means: from 9:24pm on, i can get 100 million tokens again within the subsequent week?

Yes, that's exactly it.

At 9:24pm tonight your weekly allowance refreshes, and from that point you get a fresh weekly allowance — up to that 100 million tokens — to use over the following week, until the next reset around the same time next Tuesday.

So in practice: if you're nearly capped now, just wait for 9:24pm and your usage meter should drop back near zero.

Monday, 26 October 2026

赖岳谦 | 川普惨败!巴西人大胜!

 

用muse的web版帮我构建基于nextjs+mongodb数据库的建站程序ldmp


  我用email id: luckypoem@gmail.com登录cloudflare.com

以下是我跟muse的对话内容。

me:  can u build https://github.com/brightmann/ldmp?

 Yes — I'm on it. Cloning it now (taking longer than usual, so it's still running in the background). Once it's down I'll check what stack it is and come back with the build plan — defaulting to static export, same as the other recent sites, unless it needs server features.

me:  the speed of cloning the repo is very slow?

Yes, and I can see why: it's not stuck, it's just big and slow. The clone has already pulled 272 MB and is still downloading through this sandbox's outbound proxy, which throttles bulk transfers. Nothing has checked out yet because git only writes the working files at the end.

I don't need the full history to build it, so I'll kill that clone and retry shallow (latest commit only), which should be much faster.

Yes — it's slow for a real reason, not a hang:

  • The repo is ~538 MB on GitHub (a fork of Liu-Daylilyjoy's mypage, a Next.js personal blog you forked today). At this sandbox's proxy speed to GitHub, a full clone takes 30+ minutes — it had already pulled 272 MB after 18 minutes and was still going.
  • I killed the full clone and restarted it shallow (latest commit only). That's still crawling — 21 MB so far — but its total should be much smaller than the full history. It's running in the background; I'll pick it up when it lands, nothing you need to watch.

While waiting, I pulled the package.json straight from GitHub's API, so I already know the shape: Next 15.3.3 + React 19, with next-auth and Prisma. That matters — unlike the static blogs, this one probably needs server features (auth + database), so the usual static-export default may not fit. I'll confirm what it actually needs once the code is down and come back with the real build plan.

me:  finished?

 Not yet — but it's moving. It's at 224 MB now (up from 21 MB) and still downloading. The shallow clone still has to pull most of the current files, which are the bulk of that 538 MB repo.

I'm not going to let it block the work, though — I'll inspect the repo structure through GitHub's API while it downloads。

the clone is still running, now at 224 MB and counting. The bulk is the current files, not history, so even the shallow clone is slow on this proxy.

But the clone isn't blocking me anymore — I mapped the whole repo through GitHub's API while it downloads:

  • What it is: a full-stack personal site (Next 15 + React 19, App Router) with an admin backend for blogs, photos, and thinkings, NextAuth login, and API routes throughout.
  • Database: Prisma + MongoDB (DATABASE_URL), models for Blog, Thinking, Photo, and page-visit counts.
  • Why not static export: API routes, auth, and database writes — same situation as cnb. A static build would break the admin and all the writes.

So my plan is to host it on the VM like cnb: local MongoDB database, next start on its own port, exposed as ldmp.mingsea.net through the existing tunnel. The clone will finish in the background; once you confirm, I'll build it as soon as the code lands.

the VM rebooted again around 23:23 (second reboot tonight), which killed the clone mid-download and wiped the partial copy. So that 224 MB is gone and the clone is starting over.

What I've done:

  • Restarted the shallow clone in the background. It'll take a while again on this slow proxy, but it'll land on its own.
  • Your live sites (cnb, Shiro backend, Ghost, etc.) went down with the same reboot — the watchdog is restoring them automatically, same as it did after the 22:08 reboot, so no action needed there.

Once the clone lands, I'll get the ldmp build going.

me: pls host ldmp on your VM.

 Confirmed — VM hosting for ldmp. The clone is already at 125 MB and still going, and MongoDB + Core are already back after the reboot. While it downloads, I'll finish the prep that doesn't need the code.

  • Clone: at 125 MB and still downloading in the background. It'll land on its own.
  • Already back after the reboot: MongoDB and Core are up, so the database side is ready.
  • Prep done while waiting: service file and bootstrap script are ready in ldmp-stack/ — port 3250, database ldmp on the local MongoDB, public URL planned as ldmp.mingsea.net. The NEXTAUTH_SECRET generates itself on first start.

One thing I need from you before first start: the admin login. The app checks ADMIN_USER / ADMIN_PASS from the environment, so whatever we set is what you'll type at /login. Want me to generate a strong password (username admin), or will you pick your own?

me:  I'll set my own username and password

Got it — your call. Send me the username and password whenever you're ready, and I'll put them in the app's env file only (nothing else, no other copies). No rush: the clone is at 192 MB and still downloading, so the build can't start until it finishes  anyway.

me:   username: admin pw: 我所设置的密码

Saved — both values are in the app's env file only, placeholders gone, file locked to owner-only access. I won't repeat them anywhere else.

Clone is at 280 MB and still going. Once it lands, I'll install, build, and bring the site up with this login.

Clone finished — 186 files, commit 1d5ec7c. Install, Prisma generate, and the Next build are running in the background now.

Once the build passes, the remaining steps are: start the service on port 3250, point to ldmp.mingsea.net through the tunnel, and verify it live. I'll report back when it's up.

ldmp is live: https://ldmp.mingsea.net

Verified just now: homepage 200, /login 200, and /api/blogs returns an empty list with 200 — so the app, the tunnel, and the MongoDB connection all work.

What it is: the Next 15 personal site with admin backend (blogs, photos, thinkings) and NextAuth login. Log in at /login with the username and password you set. Two things to know:

  • The site starts empty. I deliberately did not import the upstream author's seed posts (dataScript/*.json) — that's someone else's personal content. You add your own contents through the admin panel.
  • Admin sessions are short by the template's own setting (10 minutes), so don't be surprised if it asks you to log in again after a while.

The road here was rough (slow 538 MB clone killed twice by VM reboots, pnpm 12 rejecting the old workspace file, Prisma's engine download failing under this proxy) — all worked around locally in this VM clone, nothing pushed to GitHub.

One offer: add ldmp to the 5-minute watchdog, so if a VM reboot wipes its service file again, it restarts automatically.

me: Yes, add ldmp to the watchdog.

It checks that ldmp-app is active and that the site answers locally on port 3250. If either fails, it runs the ldmp bootstrap once, re-checks, and logs the outcome.

me:  i don't see where to change the pw after login the blog.

There isn't one — that's why you can't find it. This template doesn't store the password in a database, so the admin has no profile or settings page. Its only pages are the dashboard, Blogs, Photos, and Thinkings.

The login just checks against a password set on the server itself. So to change it, send me the new password (or say "generate one") and I'll swap it in the server config and restart the site. The new one takes effect right away, and you'll need to log in again with it.

 me: https://ldmp.mingsea.net/admin/blogs/new shows 404. pls fix it.

Found it — it's a template bug, and it only bites because your blog list is still empty.

The "Create your first blog" button on the empty list links to /admin/blogs/new, but the template never implemented that page. Blog creation actually lives in the "New Blog" dialog on the blog list itself (the header button works — it's the empty-state link that's broken).

Fix going in now: I added the missing /admin/blogs/new page as a redirect into that creation dialog, and pointed the empty-state link straight at it. Rebuilding and will confirm it live.

Fixed and verified live: https://ldmp.mingsea.net/admin/blogs/new now redirects to the blog list with the "New Blog" dialog open, instead of a 404.

To create a post now: open Blog Management, hit "Create your first blog" (or "New Blog" at the top), fill in title and description, and it takes you straight into the editor.

One note: this fix lives in the VM copy only, like the other ldmp patches — it isn't pushed to GitHub. Say the word if you want it committed up.

me:  and when click '+ new blog', it shows "failed to create blog'. pls fix it.

 The handler itself looks fine, but the app log shows repeated prisma:error lines — including one right around your click.  

Fixed. The cause was underneath the blog code, not in it:

Your local MongoDB was running as a standalone server, but Prisma runs every write inside a transaction — and MongoDB refuses transactions unless it's a replica set. Reads worked (that's why the empty list loaded fine), but every create failed with a 500, which the UI shows as "Failed to create blog".

I converted MongoDB to a single-node replica set and proved it with a create-and-delete round trip through the same code path the button uses. Nothing was left behind — your two test attempts never actually saved, so the list is still clean at 0 posts.

Try "+ New Blog" again now — it should go through to the editor.

this template's article page renders only the body. Here's the mechanism:

  • The "New Blog" dialog only asks for title and description. The article text itself lives in a separate markdown file, which starts out empty.
  • The public page at /blog/<id> fetches just that file and renders it. It never shows the title or description — those only appear on the /blog list.
  • Your post's body file is currently empty, so the page renders an empty article.

To fill it in: go to Blog Management → Edit on that post → write the article in the editor → Save. Then the public page will show it.

me:  can u make https://ldmp.mingsea.net/blog support pagination?

 Done building, now checking it live. The pager is in and the site restarted — /blog now shows 5 posts per page with a Previous | 1 | 2 | Next bar, and page 2 holds the 6th post. I'm verifying the rendered pages in your browser right now and will confirm the exact result once that check comes back.

Done and verified live. ldmp.mingsea.net/blog now paginates at 5 posts per page:

  • Page 1 shows the 5 newest posts, with a Previous | 1 | 2 | Next bar at the bottom (1 highlighted, Previous greyed out).
  • Page 2 shows the 6th post (测试), with 2 highlighted and Next greyed out.

The year grouping is kept, just applied per page, and the pager hides itself if you ever drop back to a single page. One note: like the earlier ldmp fixes, this change is in the VM copy only, not pushed to GitHub — say the word if you want it committed up.

me:  pls push all the code changes to my repo including the changes above.

Ready to push. Remote is still at the same commit as this clone, so it'll be a clean fast-forward, and no workflow files are touched — a token with Contents read/write on brightmann/ldmp is enough.

Here's everything waiting in the working tree:

  • src/app/(user)/blog/page.tsx — the pagination from just now
  • src/app/admin/(auth)/blogs/page.tsx + src/app/admin/(auth)/blogs/new/ — the empty-state "Create your first blog" fix
  • pnpm-workspace.yaml — the pnpm 12 allowBuilds rewrite (needed to build here)
  • src/posts/blog/*.md (6 files) — your article bodies, already live on the site; pushing them backs them up in git

Paste a PAT for brightmann/ldmp and I'll commit all of it, push, verify the remote took it, then restore the remote token-free and you can revoke the token.

me: here is the pat.... 

Staging worked, but the repo's husky pre-commit hook failed — it calls pnpx, which isn't on PATH here. Let me check what the hook actually does before working around it.

 Committed as a4733b6 (10 files, tree clean, hook passed). Pushing now.

 Pushed and verified. Updating the record to reflect that these are no longer local-only.

Pushed. Commit a4733b6 is now on brightmann/ldmp master (verified the remote HEAD matches), covering all 10 files: the blog pagination, the admin create-link fix, the pnpm 12 workspace rewrite, and your 6 post bodies.

The remote is restored to the plain token-free URL and the working tree is clean. You can revoke that token now.

我得到的博客地址: 

https://ldmp.mingsea.net/

https://ldmp.mingsea.net/blog

登录地址: https://ldmp.mingsea.net/login

项目地址:

https://github.com/Liu-Daylilyjoy/mypage
https://github.com/brightmann/ldmp