imagicthecat / bitsea-alexandria Goto Github PK

• Extension to convert BitSea URIs to the local web server ?
• Use iframes to create a web interface instead of getting raw HTTP resources ?

Because data from BitSea can be acquired from different seaways, it has different contexts from public to critical regarding privacy.

One could use an anonymity specialized seaway to share critical information, which will probably be less efficient at transferring large amount of data. On the other hand, a public seaway would be more suited if anonymity is not required.

When data is accessed or produced, it could be bound to a specific browsing environment to prevent the sharing of that data on an insecure seaway.

• Main seaway: network with a DHT to record which nodes has a specific data object or topic. Each node is an HTTP server receiving data object or topic requests.
• Proxy seaway: request to a proxy node through HTTP with proxy support, like Tor. Alternative when being a server is too complicated (NAT, UDP is blocked, etc.) or when anonymity is required.