isomorphic-webcrypto VS dom-examples

End to end encryption, if possible: if your use cases allows it, try your best to implement end to end encryption. That means that, if the user uploads a file, it should be encrypted client side (in the browser) before uploading. You can derive the key from the user's password and/or security token (see below). Check here for some resources: https://www.w3.org/TR/WebCryptoAPI/.

https://en.wikipedia.org/wiki/Argon2

> There is no reason not to use Argon2

In this case, the reason for not using Argon2 is that it's not available: https://www.w3.org/TR/WebCryptoAPI/

> Well if this product isn't for mass-market

This is a demo for self-contained HTML encrypted secrets. Do with it what you want.

A TypeScript Hybrid Public Key Encryption (HPKE) implementation build on top of Web Cryptography API This module works on web browsers, Node.js, Deno and Cloudflare Workers

I haven’t used it, but https://github.com/kevlened/isomorphic-webcrypto might be more along the lines of what you’re after

Fonte: MDN web docs

References MDN Chrome Docs

> if writing a browser today is in fact easier than both writing AND maintaining a browser a decade back.

Probably not. Yeah we have web standards and some idea of how to architect it, but the total set of APIs and HTML/CSS/JS features a browser supports is probably changing faster than the Ladybird team can actively implement it. The API surface is just impossibly large compared to 10 or 15 years ago. Look at all of these: https://developer.mozilla.org/en-US/docs/Web/API

I added polyfills for the Web APIs used in the React code.

In addition to pure JavaScript, there are hundreds of Web APIs documented at MDN. These APIs cover everything from the DOM to Web Workers with great detail.

I'm reading MDN Web Docs on Web APIs. There are two basic sections, specifications and interfaces.

The biggest difference is usually found in what non-ECMAscript standard JS web apis or features are implemented in different browsers. Here's a list of typical web APIs, and for many of them there is a compatibility table at the bottom detailing which browser do or do not support it. https://developer.mozilla.org/en-US/docs/Web/API

Documentation of Web APIs and interfaces is located on the MDN (Mozilla Developer Network) website. The term "Web API" can refer to browser or server APIs. In this article, it refers to Browser APIs.

The second one was an afternoon of "boredom." I wanted to develop, but I was running out of ideas. So, I decided to explore something new. I navigated to the Web APIs page on MDN, and something caught my eye on the letter g: Gamepad API.