Browser curiosity

For these times that you want to have super-privacy enabled. GridnetOS within GridnetOS. Some stuff works fine, some buttons cause refresh of the browser. Still interesting.

Definitely, the glossy looks is interesting to me :laughing:

@vega4 and @CodesInChaos have been working like a lot on the reverse CORS proxy apparatus, maybe they would have something to say (…)

In any case I was unable to reproduce the issue.

It was not a bug, I deliberately used Browser to go to and it worked. So Gridnet within Gridnet worked fine, except for button response that caused website reload. Just a curio.

and so I’ve been told you oftentimes happen to have out-of-the-box ideas :laughing:

Such usage (…) such usage is one of the things (…) we’ve been tacking (…) and researching for quite some time:)

It boils down to having the proxy service facilitate a decentralized onion-routing later atop of the HTTP -protocol alone.

1 Like

Because you see, first implementations of the Onion Routing protocol,- these relied on multiple TCP streams.

Later this turned out to be inefficient and we’ve implemented the so called ‘tunnel-extension’ mechanics so that the tunnel was to extended in a telescopic manner, as it was being created, similarly to how one builds underground tunnels these days. All happening from within of a single TCP stream. With multiple requests all packed into a single data-stream through control packets.

Now surely we are on uncharted territories. Facing upon, new never seen before possibilities.

Imagine portions of a single website being onion routed through multiple peers. As I see it, taking into account what we’ve already got - it’s perfectly feasible.

Compromising end-to-end encryption, between client and target web-server of course.

All in all, I would deem it as an inefficient though interesting thought experiment.

Of course, I’m always open to the subject. It’s extremely interesting.

If, we can chain requests through multiple peers right now, that means anonymous Web requests for/to any centralized service etc.

Still, that very thought experiment might lead to making the Decentralized UI accessible through a multi-hop connection. As I see it, all it takes is to ensure the proxy service is transparent to requests.

@CodesInChaos the major update , you were working on, which I saw on Twitter which was supposed to go trough last Monday/Tuesday was not published yet, correct?

The update to the crypto-incentivized reverse CORS proxy apparatus went LIVE today.

Check it out below:

Anonymous Google

Anonymous Wikipedia


(…) seemingly we’ve indeed gained a significant improvement in performance. Nice work.