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.
It could also speed up data bases that rely on HTTP and JSON or BSON like MongoDB. Our packet design is meant to be space efficient while still meeting modern development needs for structured data.
A good amount of compute time/space is saved for those that required binary data but had to convert it to base64. Our packet design avoids having to convert to base64 etc to/from just to include binary data in a structured object.
Once decoded you have access to that binary data via a buffer. All the while your other data such as arrays, strings, and integers are accessible without having to also be displayed as a buffer. Complex types are easily digested without having to do any manual work or conversions
• • •
Missing some Tweet in this thread? You can try to
force a refresh
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”.
@DontKnowCrypto@raste_ej@BaronTelcoin@3RMAC@CryptoMomUSA1@at00344 You need a mechanism to incentivize technology adoption on a mass scale while also being in & of itself part of the future and the solution. That’s cryptocurrency. I stumbled upon it as a solution to a problem. I refused to get into crypto until it showed itself to be a solution.
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.
If verified but incomplete cache is found it’ll use its completed segments first then ask the server for only the missing segments of the file. This further cuts down bandwidth and server resources. It’s another revolutionary addition to browser cache.
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.
Another breakthrough was how UDSP handles files which allows you to download an item from a unique URL or even a separate domain to resume a download.
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.
Domains will then open up for purchase which some types for development will be free but with limited DIS features for example only one primary cert. Unlike the WWW developers will get free domains to test things out on the UW no need for local testing anymore.
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.
Those who have been around long enough knows that the developer space always flip-flops between centralized solutions and decentralized solutions. These are trends in the space fads that don’t last long until sanity balances things out again.