#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
6) Pop up closes

7) you are sent to a new page which triggers the login and now the logged in version of the site loads (Multiple page loads here)
Let’s compare this with Universal sign-on

1) You load up the site. The End.

On the UW sign on happens at a lower layer and is done automatically all the data required for it is neatly packaged in a single packet. No usernames, emails, or passwords. Only hardened cryptography.
Talk about #ecofriendly the Universal Web axes so many processes that would suck up more electricity Web wide. Imagine the cost savings for not just the planet but companies too.
It also cuts down dev time, cuts down page load times for users, saves users on the bandwidth bill, increases user retention, & cuts down on potential profit loss due to slow page loads like the @amazon 100ms delay 1% loss study showed us.
This is but a fraction of the new world the #UniversalWeb could bring. Take a moment to fully conceptualize the #UW & imagine how different the world would be because of it. Imagine folks walking around with protected RFID devices or even have it embedded in your hand.
On that notion we have a safe #RFID under the skin embedded design (popular in #biohacking/tech world) that is protected from scanning & can be accessed only during direct or close contact with the reader. This is just a small drop of how far we are thinking & testing.
Any UW RFID login could be protected with a pass key/phrase, #biometrics, #ble, #patternrecognition, #AI, #ML, & or a cryptographic process. It’s perfect for #government/#private locations looking for a basic to robust physical #accesscontrol system.
You get all of that with Universal Sign-on. The Universal Web marks the World Wide Web as a to be deprecated dependency for humanity.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Thomas Marchi 🐙

Thomas Marchi 🐙 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @tommarchi

4 Nov 19
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.
Read 17 tweets
16 Oct 19
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 username and password was never sent. Next to no login middleware is required to do your typical user authentication procedure. Avoiding potentially a good amount of typical security protocols.
Read 8 tweets
15 Oct 19
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.
I look under and see that my @netflix & #DcUniverse subscriptions were recently billed. Which I’ll be renewing as I rather enjoyed the new season of Titans. I see that they used again centralized services to get instant billing which I had initially agreed to.
Read 14 tweets
7 Oct 19
“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.
“Does this put companies like Cisco our of business”
Nope. It would open them up to new markets and new unique technology offerings. Same situation with HTTP3.
Read 7 tweets
29 Sep 19
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.
The Domain Information Service is designed to be smart, lean, flexible, and robust. There is so much power in DNS as a service that would fix a plethora of issues on the web.
Read 8 tweets
24 Aug 19
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.
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!