Another open problem: Is a pure-javascript 402Receipts client possible?

The basic idea is that a "trusted" party would host the javascript, and _that_ js, served at _that_ address, would have access to its own secure user-data no matter which site it was requested from.

Depending how dynamic Wallets end up being, maybe the only thing that would need to be stored in that "database" would be credentials for connecting to the Wallet. But I think it'll be better for the wallet to be flatter than the client.

· · Web · 0 · 0 · 0
Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!