3 ms·

I saw that you updated the readme to include that it is based on other browsers, great! The feature list still seems intact though, so if that is intended to r

I saw that you updated the readme to include that it is based on other browsers, great! The feature list still seems intact though, so if that is intended to represent the current state perhaps you can help me understand these points (And please forgive me if you just intended to update it later): --- > It uses trust-based Peers to share the local cache. Peers can receive, interchange, and synchronize their downloaded media What is a trusted peer? How is trust established? > It is peer-to-peer and always uses the most efficient way to share resources and to reduce bandwidth, which means downloaded websites are readable even when being completely offline. What P2P tech is used here? Again, how is trust handled for resources downloaded over P2P networks? > The Browser is completely free-of-DOM Is createElement, appendChild and similar other methods used here not part of the DOM? https://github.com/tholian-network/stealth/blob/1efe80f8baf6 https://github.com/tholian-network/stealth/blob/1efe80f8baf6... --- I'm saying that if you make extraordinary claims you will need extraordinary evidence. Or say that they are ambitions until you can produce that evidence, which is completely fine!

cookiengineer 6y ago
> How is trust established? By default, stealth trusts nothing. If you want to browse a website you have to configure the level of "trust" you expect the website to have. A news website, for example, should serve text and images, not sound or video (unless you expect it to). Trust on websites is based on media types (in the iana sense) and so called site modes that can be applied to all URLs. Trust on peers is established with a currently manual handshake which leads to an availability query to the requested peer, and its available internet connection bandwidth (to not drain peers with cellular internet and save bandwidth). You want to use a peers resources? You have to add it first, in the browser settings. This is the current workflow until peer discovery (and a UI for that) is implemented. > The Browser is completely free-of-DOM Please note that the Browser UI is nothing more than a websocket client, and therefore remote controls the locally running stealth/source/Browser.mjs instance. This is why the browser/source folder contains only so few implementations, because it doesn't need more. > What P2P tech is used here? Currently, there is no way to discover peers automatically. Peer discovery will be available once radar gets online and is integrated. But protocol wise, all protocols (except dns tunnel due to not being ready yet) can be used in a peer to peer manner, you can use a stealth instance in the same LAN for example as a socks proxy, or as an http/s proxy, or as a ws/s proxy. Primarily, the officially supported API will probably be the websocket api because it will be easier to implement for potential third parties. Regarding evidence: Take a look at covert, the testrunner, which also is testing peer to peer scenarios end-to-end.

cookiengineer 6y ago

> How is trust established? By default, stealth trusts nothing. If you want to browse a website you have to configure the level of "trust" you expect the website to have. A news website, for example, should serve text and images, not sound or video (unless you expect it to). Trust on websites is based on media types (in the iana sense) and so called site modes that can be applied to all URLs. Trust on peers is established with a currently manual handshake which leads to an availability query to the requested peer, and its available internet connection bandwidth (to not drain peers with cellular internet and save bandwidth). You want to use a peers resources? You have to add it first, in the browser settings. This is the current workflow until peer discovery (and a UI for that) is implemented. > The Browser is completely free-of-DOM Please note that the Browser UI is nothing more than a websocket client, and therefore remote controls the locally running stealth/source/Browser.mjs instance. This is why the browser/source folder contains only so few implementations, because it doesn't need more. > What P2P tech is used here? Currently, there is no way to discover peers automatically. Peer discovery will be available once radar gets online and is integrated. But protocol wise, all protocols (except dns tunnel due to not being ready yet) can be used in a peer to peer manner, you can use a stealth instance in the same LAN for example as a socks proxy, or as an http/s proxy, or as a ws/s proxy. Primarily, the officially supported API will probably be the websocket api because it will be easier to implement for potential third parties. Regarding evidence: Take a look at covert, the testrunner, which also is testing peer to peer scenarios end-to-end.