UNIVERSAL WEB

| WHITEPAPER (OUTDATED) |

UW://

RE-IMAGINE|REMAKE|REBUILD - THE WEB

| LEAD DEV TWITTER |

ATTENTION

Are you a dev? Want to go against the grain? Don't like ICANN, IETF, TCP, HTTP, bureaucratic committees and or the WWW? Then join the imperium today!

To help just submit code or star this repo! All are welcome to the New Web Order.

Perspective

The World Wide Web has evolved for decades but its general design, limitations, & components have largely remained. Our needs & desires have rapidly outgrown the initial design & purpose of the Web. What if the Web was re-imagined today?

Goals

The objective of the Universal Web is to create a viable modern replacement for the Web today.

Is it Web3?

Not exactly. If the definition of Web3 is a fully decentralized Web then The Universal Web is not Web3. If Web3 is the World Wide Web plus some decentralized apps then the UW is not Web3. If Web3 is just the general idea of mixing something like the Web with optional and or native integration of decentralized parts then it’s much closer to what the UW is.

Where's the name from?

The Universal Web's name was chosen because of its natural evolution of the name The World Wide Web.

Internet vs Web

The Web is all the software bits that sits on-top of the Internet. The Universal Web at least for now is only concerned with software no special hardware is required. Users just need software to access the Universal Web and Servers just need software to setup a Universal Web server.

SUMMARY

• UDSP MODULE (CONTAINS SERVER&CLIENT MODULE)
• SERVER MODULE (CHECK THE UDSP FOLDER & IMPORTS FOR FULL CODE)
• CLIENT MODULE (CHECK THE UDSP FOLDER & IMPORTS FOR FULL CODE)
• BROWSER (ourdated)
• EXAMPLE APP (npm run server)
• BUILD DOMAIN&IDENTITY CERTIFICATES THAT ARE ALSO VIAT WALLETS (npm run certificates)
• SIMULATE CLIENT REQUEST (npm run simc) (ONLY RUN WHEN DEMO IN A STABLE COMMIT NOT LATEST UNLESS SPECIFIED)
• VARIOUS HELPER SCRIPTS

NPM SCRIPTS

• NPM start script builds/starts the Universal Web Browser
• Components must also be compiled for the front-end library
• Root is used to generate root certificates only
• Includes Identity Certificate generation examples
• EXAMPLE APPS
• UDSP
• UW URI (HIGHER ABSTRACTION PROTOCOL OVER UDSP)
• VARIOUS HELPER SCRIPTS

FULL LIST OF COMMANDS CAN BE FOUND IN THE project.json

REQUIREMENTS

Development is done on Mac&Linux.

• NODEJS
• NPM
• NODEMON
• ESLINT
• VSCODE

BROAD CODE OBJECTIVES

• UW UDP Based Protocol
• UW Browser (Electron)
• New UW Language(s)
• Unique UW UI
• UW Server
• UW Client
• UW DNS (DIS)
• Multi-OS Support
• Multi-Device Support

Questions

Is the UW's DIS and the WWW's DNS the same?

The WWW has the Domain Name System, Web3 has Decentralized DNS, & the UW has a similar component called the DIS(Domain Information System). Where DNS * Decentralized DNS takes a hostname and spits out an IP the DIS returns a cryptographic certificate related to the hostname. It plays a similar role but has greater functionality, works differently, has similar syntax, contains important connection information, distributes only cryptographic certificates, is designed with all other components in mind (something we believe is vital), and most notably is merely a single component in a much larger system (The Universal Web). When browsing the UW all domain lookups would go to the DIS. The DIS doesn't share any domains or rules with the Web's Domain system.

It's crazy to rebuild the Web why not improve it?

By that standard we wouldn't have many of the nice things we have today like the Web itself. Why is a question with a never ending answer. The only viable answer to "why" is the only thing that can end a never ending paradox consisting of "but why" and that's also a never ending paradox, "Why not?". The Web was only meant to go so far instead of trying to push the same tech by adding technology we should focus on replacing technology.