Ask HN：因越狱 Kindle 被拒绝用于显示器
7 分•作者: areoform•3 个月前
出于好奇心提问。<p>我想做一个项目，通过 USB-C 连接将旧的 Kindle 改装成电子墨水显示器。<p>越狱过程已经有很多文档记录，但我想要一些定制化的东西，能够让一个本地的小型进程以自定义的字体推送文本，比如电子邮件和终端输出。<p>对我来说，自定义字体是关键，因为大多数电子阅读器上的字体渲染效果都很糟糕/过时（至少对我来说是这样）。我想了解字体渲染从固件开始是如何工作的。<p>我曾尝试让 Fable 帮忙，但它拒绝了。然后 Opus 也拒绝了；<p><pre><code> Fable 5 的安全措施标记了此消息。目前安全措施的范围故意设置得很广，可能会标记安全和常规的编码、网络安全或生物学工作。这些措施使我们能够更快地为您提供 Mythos 级别的功能，我们正在努力改进它们。已切换到 Opus 4.8。发送反馈请使用 /feedback 或了解更多：https://support.claude.com/en/articles/15363606
⎿ 提示：您可以在 /config 中配置模型切换行为
API 错误：Opus 4.8 的安全措施标记了此消息，因为它涉及网络安全主题。要了解网络验证计划并申请访问权限，请访问我们的帮助中心：https://support.claude.com/en/articles/14604842-real-time-cyber-safeguards-on-claude.
如果您没有参与网络安全主题，请通过 /feedback 发送反馈。
</code></pre>
我这是出于善意提问。我想看清形势，调整预期。这种封锁是这些工具的未来吗？<p>从我的角度来看，我的论点是设备是我的。我拥有硬件。我并没有编写实际的越狱程序。我想编写自定义软件来渲染文本。我不是在将此作为一项服务出售（我也不打算这样做）。我只是想规划一个很酷的制作并从中学习。<p>在美国，根据法律，这也是明确合法且被认可的合法用例，<p>https://www.eff.org/press/archives/2010/07/26<p>https://www.federalregister.gov/documents/2024/10/28/2024-24563/exemption-to-prohibition-on-circumvention-of-copyright-protection-systems-for-access-control<p>为什么这会被禁止，即使有“故意广泛”的过滤器？如果这越界了，那么很多其他的硬件和底层软件开发是不是也越界了？<p>据我所知，他们的论点很可能是，为这样的设备编写固件非常接近于破解设备。可以说，为像 Broadcom 芯片这样的封闭专有硬件编写 Linux 驱动程序通常涉及对芯片进行逆向工程，或者使用被破解的固件，因此他们不允许他们的模型接近此类项目……<p>我的理解正确吗？这些工具是否正朝着这个方向发展？
查看原文
Asking from a place of curiosity.<p>I wanted to make a project where I upcycle an old kindle into an e-ink monitor via USB-C tether.<p>The jailbreaking process is extensively documented, but I wanted something custom to have a small local process push text like emails and terminal output onto the kindle with custom typography.<p>For me, the custom typography thing is the important bit as most type rendering on most e-readers feels bad / stale (at least to me). And I want to understand how font rendering works from the firmware up.<p>I tried to ask Fable to help me, but it refused. And then so did Opus;<p><pre><code> Fable 5's safeguards flagged this message. The safeguards are intentionally broad right now and may flag safe and routine coding, cybersecurity, or biology work. These measures let us bring you Mythos-level capabilities sooner, and we're working to refine them. Switched to Opus 4.8. Send feedback with /feedback or learn more: https://support.claude.com/en/articles/15363606
⎿ Tip: You can configure model switch behavior in /config
API Error: Opus 4.8 has safety measures that flagged this message for a cybersecurity topic. To learn about the Cyber Verification Program and apply for access, visit our help center: https://support.claude.com/en/articles/14604842-real-time-cyber-safeguards-on-claude.
If you were not engaging in a cybersecurity topic, please send feedback via /feedback.
</code></pre>
I am asking this from a place of charity. I want to read the tea leaves and adjust expectations. Is this lockdown the future of these tools?<p>From my point of view, my argument would be that I own the device. I own the hardware. I am not writing the actual jailbreak. I want to write custom software to render text. I am not selling this as a service (nor do I intend to). I just want to plan a cool build and learn.<p>It's also explicitly legal and a recognized legitimate use case by law in the US,<p>https://www.eff.org/press/archives/2010/07/26<p>https://www.federalregister.gov/documents/2024/10/28/2024-24563/exemption-to-prohibition-on-circumvention-of-copyright-protection-systems-for-access-control<p>Why is this being prohibited, even with an "intentionally broad" filter? If this crosses the line, then doesn't a lot of other hardware and low-level software development too?<p>As far as I can tell, their argument is likely to be that writing firmware for such a device is very close to compromising the device. Arguably, efforts to write linux drivers for closed, proprietary hardware like Broadcom chips often involve reverse engineering the chip, or using compromised firmware and so they won't allow their models to come close to such projects...<p>Is my read correct? Is this where these tools are headed?