BrowserID 目前使用 Javascript shim，而浏览器仍在（希望）开发对其的支持。不运行 javascript 的客户端是否可以使用 BrowserID？
我可以读取600行JS shim，并找出navigator.id.getVerifiedEmail的用途，然后将其复制到服务器上，但我希望有一个更简单的方法。即使那样，我也不认为它真的有效。
好吧，再深入一点，这似乎与 BrowserID 的用途无关，并且可能需要某种自定义 BrowserID 验证器，但我希望有一种更简单的方法。
BrowserID currently uses a Javascript shim, while browsers are still (hopefully) developing support for it. Is it possible to use BrowserID for clients that don't run javascript?
I could read the 600 line JS shim, and figure out what navigator.id.getVerifiedEmail is meant to do, then replicate it on a server, but I was hoping there's an easier way. And even then, I don't think it would really work.
OK, digging a bit deeper, this seems to be peripheral to what BrowserID is meant to do, and might require some kind custom BrowserID validator, but I'm hoping there's an easier way.
发布评论
评论（3）
python 中的“服务器端”BrowserID 或任何其设计不可能实现的内容。仔细阅读 BrowserID 工作原理页面，特别注意“证书配置”部分和第 3 步流程描述。它确实需要客户端浏览器支持 BrowserID 和 javascript，因为 BrowserID 技术需要在证书配置步骤期间在客户端浏览器中运行一些代码。
"Server-side" BrowserID in python or whatever is impossible by its design. Read carefully the How BrowserID works page, especially pay attention to section 'Certificate Provisioning' and step 3 in the flow description. It does require support for BrowserID and javascript from the client's browser, because BrowserID technology requires some code to be run in the client browser during Certificate Provisioning step.
Javascript shim 的存在是为了解决浏览器中缺少本机支持的问题，因此在可预见的未来将需要它：
https://developer.mozilla.org/en-US/docs/Persona/FAQ#Why_does_Persona_require_JavaScript.3F
The Javascript shim exists to work around missing native support in browsers, so it will be required for the foreseeable future:
https://developer.mozilla.org/en-US/docs/Persona/FAQ#Why_does_Persona_require_JavaScript.3F
一种解决方案是使用 OpenID 或手卷电子邮件验证，但我有两个问题。 :(
One solution, use OpenID or hand-rolled email verification, but then I have 2 problems. :(