PulseAugur
实时 18:42:17
English(EN) Okay, I admit it. My problem with Xfinity yesterday was *most likely* entirely on my side. (Let me explain the "most likely" bit. I did tests before calling the

用户表达强烈的反AI和反LLM情绪

一位Mastodon用户对AI和LLM表达了强烈的负面情绪,称这项技术是一个愚蠢且有害的行业。用户还将自己与Xfinity客户服务部门的糟糕经历与AI系统的感知智能进行了比较,质疑人类客服是否和他们互动的AI一样愚蠢。 AI

排序理由 该集群包含社交媒体上的个人观点和抱怨,缺乏关于AI发展或行业趋势的任何可验证事实或新信息。

在 Mastodon — mastodon.social 阅读 →

AI 生成摘要 · Google Gemini · 来自 3 个来源。 我们如何撰写摘要 →

用户表达强烈的反AI和反LLM情绪

本文如何被排名

Signal score
0 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Meme
该集群包含社交媒体上的个人观点和抱怨,缺乏关于AI发展或行业趋势的任何可验证事实或新信息。
Source corroboration
3 independent sources
Multiple independent publishers reporting the same story raises confidence that it's real and newsworthy.
Topics
opinion
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
Standard
On-topic for AI-industry coverage; kept in the public index.
Story freshness
105 days old
Aged out of breaking-news scoring windows; ranking reflects the durable signal from the full source set.

完整方法见我们的编辑标准

报道来源 [3]

  1. Mastodon — fosstodon.org TIER_1 English(EN) · [email protected] ·

    抱歉我的法语不好,但去他妈的#LLM,#AI以及那些在愚蠢、有害的生意背后的人。无论他们如何努力说服你,从那该死的

    Excuse my bad French, but Fck # LLM , # AI and those behind that stupid, pernicious business. For much they try to convince you, nothing good comes from that crap. # noAI

  2. Mastodon — fosstodon.org TIER_1 English(EN) · [email protected] ·

    抱歉我法语不好,但去他妈的 # LLM、# AI 以及所有支撑这种愚蠢、有害业务的东西。# noAI

    Excuse my bad French, but Fck # LLM , # AI and all that are behind that stupid, pernicious business. # noAI

  3. Mastodon — mastodon.social TIER_1 English(EN) · [email protected] ·

    好吧,我承认。我昨天在使用 Xfinity 时遇到的问题*很可能*完全是我这边的原因。(让我解释一下“很可能”这个说法。在打电话之前我做了测试

    Okay, I admit it. My problem with Xfinity yesterday was *most likely* entirely on my side. (Let me explain the "most likely" bit. I did tests before calling them. I found that port forwarding to two *different* internal servers did not work. So I put the blame on them. I found wh…