Well.. see y'all again in 2 yrs when they try to push it through under a new name
@feddit.de
There can be an infinite amount of certificates for a single domain.
When you setup a connection to a website you basically get a response back that has been signed with a certificate.
Your Browser / OS has a list of certification authorities that it deems trustworthy.
So when you get the response the browser checks if the certificate was issued by a trusted CA.
Now, if the EU forces browsers to trust their CA they can facilitate a man-in-the-middle attack.
In this instance they will intercept the TLS Handshake and give you back a response that was signed by their certificate. Your Browser deems the certificate valid and sets up a secure tunnel to the EUs Server.
From then on they can forward packets between you and the real website while being able to read everything in cleartext
On that note... Also take a look at DeArrow
Same dev as SponsorBlock, same concept, just for YT Titles and thumbnails.
Users can submit titles that better describe the contents and pick a neutral thumbnail.
Sounds like "Progressive Enhancement"
You can find this in many server side rendering frameworks where the Server will load the page as HTML first and then replace the DOM with JS-bound Elements.
If you are interested in the Topic I can highly recommend taking a look at Remix.run .
It has progressive enhancement at the core of its design. For example it uses the Forms API to send data. This way you can interact with the website with and without JS
thanks for using Leebra!
go to feed...