4 ms·
Can you link to your source code? Have you given any thought to using the GNU Naming System to smooth over some of the usability problems with public keys? Are
by spaceheeder 13y ago
Can you link to your source code? Have you given any thought to using the GNU Naming System to smooth over some of the usability problems with public keys? Are you familiar with unhosted.org, and their use of Oasis.js to partially solve the problem of running untrusted js in the browser?
- staltz 13y agoWe haven't released any source code yet because we first want to make sure our protocol designs are correct. Unhosted is a familiar project and we are currently evaluating multiple options to run unsecure code.
- spaceheeder 13y agoGoing on a slight tangent off of jude-'s question, will there be any social or economic incentive for making one's bridge persistent, or capable of holding more data? Or will this rely on volunteer participation, like tor/freenet/etc?
- staltz 13y agoAt first it's volunteer but we do realize that incentives are needed and we're working on different models. The long-term goal, which depends on WebRTC maturity, is to have no need for Bridges, because that code would be in the browser OS.
- spaceheeder 13y agoIf the storage _wasn't_ separate from the client, wouldn't access time performance top out around the same levels as, e.g., Freenet?