@DontKnowCrypto @raste_ej @BaronTelcoin @3RMAC @CryptoMomUSA1 @at00344 Sure I’ll jump in. It’s actually quite well written and explained already in voice, video, and text but I’ll bite.

Starting the thread here read below. @DontKnowCrypto @raste_ej @BaronTelcoin @3RMAC @CryptoMomUSA1 @at00344 To summarize things first let’s split it into four main sections.

Create a foundation for & incentive adoption of a new technology.

The technology required to solve Web related issues.

Where the world is heading.

Avert a proven & largely unknown “Web apocalypse”.

Our 2nd recent breakthrough a shared browser cache pool designed to speed up static asset downloads. Imagine you visit a site that has a specific Javascript library like Jquery. It’ll store that file separately from the URL/request and identify it by its checksum. When you visit a new site that’s also using the same library it’ll check the cache pool for a matching checksum of the required static asset. If it finds it it’ll automatically complete the request even if it’s part of another request from a different URL or domain.

We had a recent breakthrough for the UW and specifically UDSP. It allows the server to essentially blast packets to a client with minimal state updates, sending dramatically less data that’s used to keep track of chunks, & can be paused or even recovered even after disconnection. It also can have multiple servers or a decentralized pool of clients that can send specific portions of a file. The client can receive packets out of order and even fill in missing segments even after total disconnect.

A plethora of Network commits started hitting the public git stable branch yesterday & more are on their way out. Will mark UDSPs Release candidate 1 & allow anyone to throw up their own DIS/UW server with minimal config. github.com/universalweb/N… There are major changes in Alpha RC 1 that makes the docs on the SNTVT domain outdated but the Whitepaper is accurate.

#Universal Sign-on #VS #Single Sign-on: Imagine logging into an app.

1) First you load the site

1.5) Load the login page or locate the sign in forum

2) Then you click single sign-on with examples: @apple @google or @microsoft @facebook @twitter

3) A pop up window loads 4) In that pop up you have to either login again but to a different service or if you’re lucky already signed in

5) Grant access to the site to one of your above accounts FYI @apple has great privacy email options now

There are many projects looking to build a “replacement” for the Web. Not including those simply offering a decentralized version alongside the Web I see such projects as far more sane and rational. Projects that believe a decentralized and blockchain based web would ever replace the web we have today is either intellectually dishonest or don’t actually understand the nature of the Web and decentralized systems.

For the #web #developers out there. Imagine this. The first packet a client sends to a service is encrypted already with an AEAD algo. With this single packet the user is able to establish a real time bidirectional socket to the server. During the handshake process the server automatically logs the user in using their identity certificate which holds their public key. The certificate is signed and verifiably authentic.

A Story from the future. I look to my dock and see the UW Browser bouncing to call my attention. I click and see that over the Viat wallet icon on the top right side of the browser there’s a 1 indicating unread wallet activity. I read the most recent one. It’s from @MattKarasiewicz paying me back for getting him a coffee the other day (I don’t drink coffee). I can see that he paid a little extra to use some of the centralized services to guarantee instant delivery and he sent it a few hrs ago.

“Will current hardware be compatible.
Yes. No new hardware would be needed to support the Universal Web. All existing hardware works perfectly fine. “How do people gain access to the new web”
Simply support it via a module/library like we do now with HTTP and quick. UDP is already supported. We are providing a browser with built-in support via electron which is chrome + Nodejs. This is why we have a client module.

Technically any Universal Web server can run on any port and won’t be an issue for the client. Due to the client getting the certificate from the DIS which specifies port. A client could request a hostname and the DIS would respond with a default certificate for that specific hostname. Meaning a port isn’t a required property for the request object sent to the DIS.

It is possible for BTC and other projects using (HTTP or TCP) to swap their data transport protocol out for a specifically tailored version of UDSP. It will drastically speed up network related communications and in-turn speed up the network as a whole. Further more operations on the data itself could also be quicker in some cases that would require JSON and base64ed data. As our latest packet design doesn’t require that binary data be converted to base64 while also being inside objects.