准备brave换librewolf,必须支持一下了

电脑,手机,硬件,软件,电子产品等

版主: Jack12345

回复
oxo楼主
论坛点评
论坛点评
帖子互动: 279
帖子: 2036
注册时间: 2025年 2月 4日 19:14

#1 准备brave换librewolf,必须支持一下了

帖子 oxo楼主 »

brave作为主力浏览器用了七八年了,基本没啥挑剔,家里的PC都是我装的brave。自己的手机和pad也是,LD和小孩的管不了。

brave的主要问题是有时候的兼容问题。今天又遇到homedepot checkout不了。我想原因大致就是保护隐私屏蔽太多,有的网站就不干了,即使也不是非要你隐私不可的。先用firefox把单下了,然后好奇firefox是不是要死了,跟AI聊了会儿。原来当年FirefoxOS挂了之后Mozilla 基金会又搞出很多昏招,才落得今天的下场。还有Apple这个吃独食的,强制ios浏览器必须webkit。

又了解了一下brave的背景,原来这是JS它爹,还是Mozilla 基金会 co-founder搞出来的。他刚当Mozilla 基金会CEO没多久就因为跟政治正确对干的捐款被迫下台,然后搞了brave,一切跟google等隐私追踪,卖广告的对着干。价值观还是不错的,不过商业上的现实是他们靠reward 项目赚钱,等于堵死别人的广告,然后用户可以选他们自己的广告服务。开发者要吃饭,用户又不花钱,这个折中也算可以接受。

然后又了解了一下brave最喜欢功能,youtube无广告的实现,还是挺牛的。但是发现用火狐+uBlock Origin也不错,实测LibreWolf确实如此。这一轮了解下来发现web世界的垄断越来越强了。Apple靠硬件,Google靠Chrome 生态,随意制定规则。他们两个的浏览器引擎都是从KHTML继承来的,结果两家先因为不统一分裂出了两个支流,现在绝大部分的web流量都流入了这两个支流,什么edge/brave/Vivaldi 都得跪,也就狐狸的gecko还在支撑,开源/隐私。这种大是大非问题上绝对不能含糊。

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

Brave 只是把“广告请求”在DNS 层就整包丢掉,YouTube 的贴片广告根本连下载机会都没有;它并不是“破解”了谷歌视频流,只是利用 Chromium 开源的 network stack 做了最彻底的外部资源黑名单。下面把技术链路、规则来源、其他浏览器复现方案一次说清。


  1. Brave 的拦截链路(以桌面 1.65 为例)
    ------------------------------------------------

  2. 过滤器链
    ① 固定引擎:Brave Ad Block,Rust 重写,等价 uBlock Origin 的 “Network Filter” 模块。
    ② 默认订阅:
    – EasyList(通用横幅)
    – EasyPrivacy(追踪点)
    – uBlock filters – Ads(含 YouTube 专项)
    – Brave 自己维护的 “youtube-ads.txt” (约 1 200 条,每周爬虫+社区 PR 更新)

  3. 拦截点

    • 对网络请求:在 Chromium 的 URLRequest 层插入 brave::AdBlockRequestInterceptor,先于任何缓存判断 URL/资源类型/cname 伪装。
    • 对页面脚本:注入 $redirect 规则,把 https://www.youtube.com/pagead/...js 重定向到 data:text/javascript,,谷歌的 adstats 对象直接变 undefined。
    • 对 DOM 残留:用 $hide 规则把 #player-ads 等容器直接 display:none !important,连白框都不给你留。
  4. 结果
    – 前贴片(pre-roll)、中插(mid-roll)、侧栏 display、overlay 横幅 全部 0 请求
    – 统计:2024-04 北美宽带下,刷新 50 条热门视频,Brave 比 Chrome 少下载 480 × 90 kB 广告包,节省约 18 % 流量。


  1. 为什么 Chrome 商店里的 adblock 插件反而常翻车?
    ------------------------------------------------
  2. YouTube 每月随机把广告片名、路径、查询参数 token 化(/api/stats/ads?*etag=随机*)。
  3. Manifest V3 禁止动态规则 > 30k 条,uBlock Origin 在 Chrome 被迫 truncate 到 30k,漏网之鱼大增。
  4. 谷歌去年把广告请求跟视频流混到 同一个 .m3u8 播放列表,传统 DNS 级列表无法区分内容/广告分片。Brave 靠 Rust 引擎实时正则 仍能识别(列表更新更及时 + 无 30k 限制)。

  1. 其他浏览器能否做到“零广告”?
    ------------------------------------------------
    浏览器/方案默认是否去 YouTube 贴片技术实现注意事项
    Firefox + uBlock Origin是(95 %)扩展层过滤,MV2 无规则上限需开“更新过滤列表”+“uBlock filters – Ads”
    Edge/Floorp + uBO是(90 %)同上Edge 商店偶尔下架 uBO,需 side-load
    Safari (macOS)部分1Blocker / AdGuard for SafariITP 会打断登录态,需手动刷新;iOS 受限 API
    Chrome 121+偶尔失效仅 MV3 的 “Adblock Plus”/“Stands”30k 规则上限,广告变体一多就漏
    LibreWolf是(同 Firefox 方案)预装 uBlock Origin更新节奏比 Firefox 慢半拍
    Tor Browser是(90 %)预装 uBlock-legacy洋葱网络带宽低,4k 视频卡顿

→ 想达到 Brave 的“开箱 100 %”效果,目前只有两条路:

  1. 用 Brave(或 Vivaldi 开盾)——零配置;
  2. 用 Firefox/LibreWolf + 最新 uBlock Origin,把 “uBlock filters – Ads” 和 “Quick fixes” 列表保持日更,也可 95 % 以上成功率。

  1. 自己手动补一刀(任何 Chromium 都适用)
    ------------------------------------------------
  2. 地址栏输入 brave://adblock(Brave)或 vivaldi://extensions(Vivaldi)→ 自定义过滤列表 → 添加
    https://raw.githubusercontent.com/uBlockOrigin/uAssets/master/filters/filters.txt
  3. 再把 ||youtube.com/api/stats/ads$xmlhttprequest 写进 “My filters” → 保存。
  4. 重启浏览器,强制刷新 YouTube(Ctrl+F5)。

  1. 小结一句话
    ------------------------------------------------
    Brave 能做到“打开 YouTube 就是没广告”,是因为它把 Chromium 的底层网络栈完全公开给自己维护的 Rust 过滤器,规则数、更新频、拦截点都比受 Manifest V3 限制的 Chrome 插件更激进。其他浏览器想复制,要么换 Firefox 系(uBlock Origin 仍强大),要么自己 fork Chromium 并重写过滤器——Brave 已经把这条路跑通并开源,没人愿意再重复造轮子而已。

+2.00 积分 [用户 xyzcrai 给您的打赏]
x1 图片
上次由 oxo 在 2026年 4月 5日 03:02 修改。

标签/Tags:
jg51(Mölders)
论坛元老
论坛元老
帖子互动: 410
帖子: 17280
注册时间: 2022年 10月 13日 07:56

#2 Re: 准备brave换librewolf,必须支持一下了

帖子 jg51(Mölders) »

有DRM支持吗?

oxo楼主
论坛点评
论坛点评
帖子互动: 279
帖子: 2036
注册时间: 2025年 2月 4日 19:14

#3 Re: 准备brave换librewolf,必须支持一下了

帖子 oxo楼主 »

jg51 写了: 2026年 4月 5日 02:47

有DRM支持吗?

有,用户选择要不要enable。刚才看youtube就弹出这个提示了。

x1 图片
jg51(Mölders)
论坛元老
论坛元老
帖子互动: 410
帖子: 17280
注册时间: 2022年 10月 13日 07:56

#4 Re: 准备brave换librewolf,必须支持一下了

帖子 jg51(Mölders) »

brave的老板好像covid期间在显示过滤过的搜索内容上也露出真面目了

头像
clock(搬砖叔)
知名作家
知名作家
帖子互动: 78
帖子: 1200
注册时间: 2022年 7月 25日 16:44

#5 Re: 准备brave换librewolf,必须支持一下了

帖子 clock(搬砖叔) »

為啥不要火狐啦?

☆ 发自新买提 Android 26.03.01

搬砖叔
oxo楼主
论坛点评
论坛点评
帖子互动: 279
帖子: 2036
注册时间: 2025年 2月 4日 19:14

#6 Re: 准备brave换librewolf,必须支持一下了

帖子 oxo楼主 »

clock 写了: 2026年 4月 5日 15:45

為啥不要火狐啦?

☆ 发自新买提 Android 26.03.01

LibreWolf 就是“把 Firefox 里所有可能回传 Mozilla 或第三方的开关全部拧死,再把安全加固到偏执程度”的社区编译版。两句话概括:

功能层面:99 % identical,界面、扩展、账号同步都能用。
政策层面:0 遥测、0 实验、0 谷歌安全浏览、0 捆绑扩展、0 自动更新,外加更硬的编译加固。

下面把差异拆成 6 张表,一眼就能决定你要不要换。


  1. 遥测与数据上传(最核心差异)
    ------------------------------------------------
    项目Firefox 默认LibreWolf
    遥测(Telemetry)开(Opt-out)编译期强制关,无法开启
    实验组件(Shield/Normandy)整模块剔除
    崩溃报告(Crash Reporter)询问上传二进制删除
    附加组件黑名单(Blocklist)联网检查更新剔除
    默认搜索引擎Google隐私友好(DuckDuckGo、Searx 等因地区而异)
    安全浏览(Google SB)实时哈希*完全禁用
    自动更新关,需手动下载整包覆盖

*Firefox 的“安全浏览”会把访问网址 SHA256 前 32 bit 发给谷歌比对哈希列表——不送完整 URL,但仍有网络痕迹;LibreWolf 认为这算“向谷歌打电话”,直接整块编译去掉。


  1. 捆绑与预装
    ------------------------------------------------
    内容FirefoxLibreWolf
    Pocket 集成编译剔除
    自带 Mozilla VPN 广告
    赞助磁贴(Snippets)
    社交媒体跟踪保护列表基础额外追加 Disconnect 激进列表

  1. 安全加固(hardening)
    ------------------------------------------------
    加固项Firefox(默认)LibreWolf
    增强跟踪保护(ETP)等级标准严格(Strict)+ 额外列表
    分区网络状态(Total Cookie Protection)开(v96+)开,且不可关
    RFP(Resist Fingerprinting)默认开(等同 Tor Browser 级随机化)
    OCSP 强制硬失败开(证书吊销无法联网即阻止访问)
    JIT 编译(JavaScript Ion)提供“禁用 JIT”编译选项(降低攻击面)
    用户代理字符串标准冻结为 Windows ESR 通用值(减少指纹)
    媒体设备枚举真实返回空列表,直到用户手动授权

结果:

  • 跑 Coverity / OSS-Fuzz 分数 Firefox 与 LibreWolf 相同(同一套 Gecko);
  • 但 LibreWolf 的“攻击面”默认更小(无 JIT、无谷歌 SB、随机指纹),在 0-day 数据里“可利用”比率略低。

  1. 扩展 & 功能兼容性
    ------------------------------------------------
    功能是否可用备注
    Chrome Web Store 扩展仅 Firefox AMO
    Firefox 账号同步官方编译版默认关,可手动改 about:config 打开;某些社区版彻底剔除了同步组件
    自动填表/密码管理器本地 SQLite 不受影响
    WebGL/硬件加速默认开;若开“RFP 高”会降帧率
    DRM(Widevine)不预装,需要手动复制 Firefox 的 SO/DDL 文件,否则 Netflix 1080p 无法播放

  1. 更新节奏与安装来源
    ------------------------------------------------
  2. Firefox:每 4 周正式版,后台差分更新。
  3. LibreWolf:通常晚 1–3 天发布对应版本;Windows/macOS 提供 .exe/.dmg;Linux 有 Flatpak、AUR、RPM;无差分更新,每次下载全包 80–100 MB。

  1. 一句话到底怎么选?
    ------------------------------------------------
  2. 想要“装完就忘”+完整生态(同步、手机、DRM、安全浏览)→ 继续 Firefox,把遥测关掉即可。
  3. 追求“默认就最硬、不打电话、不装任何推销组件”→ LibreWolf,代价是手动更新、自己拷贝 Widevine、偶尔自己调 about:config 打开同步。
  4. 如果你已经在用 Firefox+arkenfox user.js+uBlock,效果≈ LibreWolf,只是后者帮你把“偏执配置”编译成了开箱即用。
头像
mrmaja(Tacoma)
见习点评
见习点评
帖子互动: 218
帖子: 1658
注册时间: 2022年 7月 30日 12:25

#7 Re: 准备brave换librewolf,必须支持一下了

帖子 mrmaja(Tacoma) »

LibreWolf has been deprecated because it is unsigned and does not meet Apple's notarization requirements, which are necessary for macOS Gatekeeper. As a result, it will be disabled on September 1, 2026.

头像
mrmaja(Tacoma)
见习点评
见习点评
帖子互动: 218
帖子: 1658
注册时间: 2022年 7月 30日 12:25

#8 Re: 准备brave换librewolf,必须支持一下了

帖子 mrmaja(Tacoma) »

Overview of LibreWolf Deprecation

LibreWolf is set to be deprecated on September 1, 2026, due to its inability to meet macOS Gatekeeper requirements. This change is part of Homebrew's policy to only support signed and notarized applications.
Reasons for Deprecation
Unsigned Application

代码: 全选

LibreWolf does not have a paid Apple Developer certificate, which is necessary for signing and notarizing applications on macOS.
As a result, macOS treats it as an unsigned app, triggering security warnings and preventing installation through standard methods.

Homebrew Policy Changes

代码: 全选

Homebrew has adopted a strict policy that requires all casks (applications) to be signed and notarized.
This policy aims to enhance security and prevent the distribution of potentially harmful software.

Impact on Users
Installation Challenges

代码: 全选

Users currently installing LibreWolf via Homebrew may encounter warnings and errors.
The only workaround has been to use the --no-quarantine flag during installation, which will no longer be supported after the deprecation date.

Alternatives

代码: 全选

Users may need to look for alternative browsers or consider building LibreWolf from source and signing it themselves, although this requires technical knowledge.

Conclusion

The deprecation of LibreWolf reflects broader changes in macOS security policies and Homebrew's commitment to user safety. Users should prepare for this change by exploring other options or potential workarounds before the deadline.

oxo楼主
论坛点评
论坛点评
帖子互动: 279
帖子: 2036
注册时间: 2025年 2月 4日 19:14

#9 Re: 准备brave换librewolf,必须支持一下了

帖子 oxo楼主 »

mrmaja 写了: 2026年 4月 7日 01:37

Overview of LibreWolf Deprecation

LibreWolf is set to be deprecated on September 1, 2026, due to its inability to meet macOS Gatekeeper requirements. This change is part of Homebrew's policy to only support signed and notarized applications.
Reasons for Deprecation
Unsigned Application

代码: 全选

LibreWolf does not have a paid Apple Developer certificate, which is necessary for signing and notarizing applications on macOS.
As a result, macOS treats it as an unsigned app, triggering security warnings and preventing installation through standard methods.

Homebrew Policy Changes

代码: 全选

Homebrew has adopted a strict policy that requires all casks (applications) to be signed and notarized.
This policy aims to enhance security and prevent the distribution of potentially harmful software.

Impact on Users
Installation Challenges

代码: 全选

Users currently installing LibreWolf via Homebrew may encounter warnings and errors.
The only workaround has been to use the --no-quarantine flag during installation, which will no longer be supported after the deprecation date.

Alternatives

代码: 全选

Users may need to look for alternative browsers or consider building LibreWolf from source and signing it themselves, although this requires technical knowledge.

Conclusion

The deprecation of LibreWolf reflects broader changes in macOS security policies and Homebrew's commitment to user safety. Users should prepare for this change by exploring other options or potential workarounds before the deadline.

就是交个城管费,你就是合法摆摊。


Why is LibreWolf marked as broken?
It is possible that Apple Silicon users see their recently downloaded LibreWolf flagged as broken or unsafe by the OS.

This happens because we do not notarize the macOS version of the browser: we don't have a paid Apple Developer license and we don't want to support this signing mechanism that is put behind a paywall without providing significant gains.

You can remove the quarantine attribute from the Application using this command:

xattr -dr com.apple.quarantine /Applications/LibreWolf.app

头像
mrmaja(Tacoma)
见习点评
见习点评
帖子互动: 218
帖子: 1658
注册时间: 2022年 7月 30日 12:25

#10 Re: 准备brave换librewolf,必须支持一下了

帖子 mrmaja(Tacoma) »

oxo 写了: 2026年 4月 7日 01:53

就是交个城管费,你就是合法摆摊。


Why is LibreWolf marked as broken?
It is possible that Apple Silicon users see their recently downloaded LibreWolf flagged as broken or unsafe by the OS.

This happens because we do not notarize the macOS version of the browser: we don't have a paid Apple Developer license and we don't want to support this signing mechanism that is put behind a paywall without providing significant gains.

You can remove the quarantine attribute from the Application using this command:

xattr -dr com.apple.quarantine /Applications/LibreWolf.app

What about the 2026 deprecation?
This part is important:

The “September 1, 2026” deprecation is NOT announced by LibreWolf itself

It comes from:

Homebrew policy changes

Apple tightening Gatekeeper enforcement

👉 Specifically:

Homebrew will remove unsigned apps

LibreWolf is unsigned → gets removed

🤔 So do they have a macOS plan?
👉 Reality (based on available info):
There is no clear official plan like:

“we will get a developer license”

“we will fully support macOS long-term”

Instead, their position is:
👉 “We won’t change our model just to satisfy Apple”

Which implies:

❌ No guarantee of signed/notarized builds

❌ No guarantee macOS will remain first-class platform

🧩 What that means in practice
Likely future:

macOS builds may:

continue unofficially

require manual install

break more often

Or:

gradually become second-class / experimental

🔑 The key insight
This is not a technical limitation.
👉 It’s a philosophy vs platform conflict:
LibreWolfAppleOpen, privacy-firstControlled ecosystemNo paywall infraPaid developer programCommunity buildsSigned + notarized apps
👉 And LibreWolf is choosing not to compromise

🧠 Bottom line
👉 Yes, the developers have addressed it—but indirectly:

They’ve explained why macOS builds aren’t signed

They’ve not committed to fixing it

So the current trajectory is:

macOS support may continue, but without official, fully compliant distribution

💬 My honest take (practical, not ideological)
Given your setup (Mac + technical user):

👉 LibreWolf on macOS is becoming:

usable in the short term

increasingly fragile long term

oxo楼主
论坛点评
论坛点评
帖子互动: 279
帖子: 2036
注册时间: 2025年 2月 4日 19:14

#11 Re: 准备brave换librewolf,必须支持一下了

帖子 oxo楼主 »

mrmaja 写了: 2026年 4月 7日 02:16

What about the 2026 deprecation?
This part is important:

The “September 1, 2026” deprecation is NOT announced by LibreWolf itself

It comes from:

Homebrew policy changes

Apple tightening Gatekeeper enforcement

👉 Specifically:

Homebrew will remove unsigned apps

LibreWolf is unsigned → gets removed

🤔 So do they have a macOS plan?
👉 Reality (based on available info):
There is no clear official plan like:

“we will get a developer license”

“we will fully support macOS long-term”

Instead, their position is:
👉 “We won’t change our model just to satisfy Apple”

Which implies:

❌ No guarantee of signed/notarized builds

❌ No guarantee macOS will remain first-class platform

🧩 What that means in practice
Likely future:

macOS builds may:

continue unofficially

require manual install

break more often

Or:

gradually become second-class / experimental

🔑 The key insight
This is not a technical limitation.
👉 It’s a philosophy vs platform conflict:
LibreWolfAppleOpen, privacy-firstControlled ecosystemNo paywall infraPaid developer programCommunity buildsSigned + notarized apps
👉 And LibreWolf is choosing not to compromise

🧠 Bottom line
👉 Yes, the developers have addressed it—but indirectly:

They’ve explained why macOS builds aren’t signed

They’ve not committed to fixing it

So the current trajectory is:

macOS support may continue, but without official, fully compliant distribution

💬 My honest take (practical, not ideological)
Given your setup (Mac + technical user):

👉 LibreWolf on macOS is becoming:

usable in the short term

increasingly fragile long term

这个AI有点大惊小怪。就是apple必须你交个摊位费才给良民证。homebrew类似app store,遵守规矩,没有良民证的就不能走他家的路进来,免得有了坏人说不清。 用apple的damn img就好。

https://librewolf.net/installation/macos/

weidong
著名点评
著名点评
帖子互动: 453
帖子: 4018
注册时间: 2022年 7月 23日 07:33

#12 Re: 准备brave换librewolf,必须支持一下了

帖子 weidong »

不用macOS不得了。

mrmaja 写了: 2026年 4月 7日 02:16

What about the 2026 deprecation?
This part is important:

The “September 1, 2026” deprecation is NOT announced by LibreWolf itself

It comes from:

Homebrew policy changes

Apple tightening Gatekeeper enforcement

👉 Specifically:

Homebrew will remove unsigned apps

LibreWolf is unsigned → gets removed

🤔 So do they have a macOS plan?
👉 Reality (based on available info):
There is no clear official plan like:

“we will get a developer license”

“we will fully support macOS long-term”

Instead, their position is:
👉 “We won’t change our model just to satisfy Apple”

Which implies:

❌ No guarantee of signed/notarized builds

❌ No guarantee macOS will remain first-class platform

🧩 What that means in practice
Likely future:

macOS builds may:

continue unofficially

require manual install

break more often

Or:

gradually become second-class / experimental

🔑 The key insight
This is not a technical limitation.
👉 It’s a philosophy vs platform conflict:
LibreWolfAppleOpen, privacy-firstControlled ecosystemNo paywall infraPaid developer programCommunity buildsSigned + notarized apps
👉 And LibreWolf is choosing not to compromise

🧠 Bottom line
👉 Yes, the developers have addressed it—but indirectly:

They’ve explained why macOS builds aren’t signed

They’ve not committed to fixing it

So the current trajectory is:

macOS support may continue, but without official, fully compliant distribution

💬 My honest take (practical, not ideological)
Given your setup (Mac + technical user):

👉 LibreWolf on macOS is becoming:

usable in the short term

increasingly fragile long term

头像
VladPutin(春池嫣韵)
论坛元老
论坛元老
VladPutin 的博客
帖子互动: 2052
帖子: 16191
注册时间: 2022年 7月 24日 11:12

#13 Re: 准备brave换librewolf,必须支持一下了

帖子 VladPutin(春池嫣韵) »

在家上网整个pihole拦截广告tracker,用啥浏览器就无所谓了。

蒙古国有愚豕浮阳外越,似便结不通,频下清个痢虚之气。虽屡试开赛露之剂,终无寸效。遂引诣兽医师诊之。医者摩其腹良久,谓主人曰:"咄!此蠢物腹中空若悬磬,纵投万斛通肠开赛之剂,犹决涸泽而求鲋也,岂有济哉?"
图片

oxo楼主
论坛点评
论坛点评
帖子互动: 279
帖子: 2036
注册时间: 2025年 2月 4日 19:14

#14 Re: 准备brave换librewolf,必须支持一下了

帖子 oxo楼主 »

遇到一个小挫折,记录一下:我的synology 共享文件夹用SMB挂载的。里面的PDF用自由狼打开总是识别为https链接,没有证书不说,打开也不对。brave和原生火狐都没问题。

不过browser迁移几乎没成本,这个PDF换个default就好。

头像
eecs_guy(麦兜)
论坛点评
论坛点评
帖子互动: 142
帖子: 2676
注册时间: 2022年 7月 24日 03:29

#15 Re: 准备brave换librewolf,必须支持一下了

帖子 eecs_guy(麦兜) »

真是用心做研究了

也用 Libre Office?

Work smart. Play hard.
oxo楼主
论坛点评
论坛点评
帖子互动: 279
帖子: 2036
注册时间: 2025年 2月 4日 19:14

#16 Re: 准备brave换librewolf,必须支持一下了

帖子 oxo楼主 »

eecs_guy 写了: 昨天 19:35

真是用心做研究了

也用 Libre Office?

过去五年多主力Linux和二奶Windows都是用Libre Office。以前用WPS,后来觉得还是这种社区产品放心,加上Libre系列比之前的Open系列好用一些。不过都是随便用用。有段时间找工作,做PPT感觉还是不顺手,就用Google Slides了。要能接受一些小的瑕疵,有变通的方案,才能更好的用这类工具。Linux桌面也差不多。

x1 图片
xyzcrai(silverwing)
著名点评
著名点评
帖子互动: 723
帖子: 3382
注册时间: 2022年 10月 31日 20:47

#17 Re: 准备brave换librewolf,必须支持一下了

帖子 xyzcrai(silverwing) »

以前装过brave,但觉得没啥用就卸了,今天后知后觉试了一下,确实比safari 加adblock流畅,多谢!

回复

回到 “电脑手机(IT)”