KeitIG

Maybe a good opportunity to remember what is the main mission of Signal/Open Whisper Systems: they realized at the time that it was extremely complicated for non-technical people to use tools secure enough and respecting your privacy (PGP...), and that the tools used by everyone (Whatsapp, Messenger...) were popular because they were fun and easy to use.

They believed that everyone should be able to have an easy way to communicate with everyone, with a nice UI/UX, AND have an app secure and respectful of your privacy. And this, leaded to the Signal protocal and the Signal app .

I love to see these small improvements added to React.

Everything is not perfect though, some issues have been here for a looong time. At the moment, my biggest problem is the non-support of passive events [0]. And today, some browsers are starting to make some events passive by default (`touchmove` on Chrome for example), it is quietly starting to become a serious problem for developers to get things working fine cross-browser without anti-patterns.

[0] https://github.com/facebook/react/issues/6436

TL,DR: "it’s a single page app written in React and built on Git"

I am really curious to see how it can scale with a loooot of content.

A good occasion to watch Gary Bernhardt's talk "The Birth & Death of JavaScript" [0] again, where he talks about the precursor of WebAssembly: asm.js and the future implication it "could" have in the future in a really humorous way. A few years old but still relevant.

You want Gimp for Windows running in Firefox for Linux running in Chrome for Mac? Yeah sure.

[0] https://www.destroyallsoftware.com/talks/the-birth-and-death...

So, fingerprints are not "secure", face recognition is not "secure"... Are passwords/double authentication the only way to keep things private and secure these days? Are there any serious alternative?

I imagine Mr Good Guy at OVH telling some others:

"guys we have a single point of failure in our architecture with SBG, maybe we should...

- naaah it's fine, we do not have time nor resources"

Then shit happens.

edit: I have no idea what is happening exactly, but OVH being what it is, it seems extremely weird that all datacenters "can" get down at the same time, and it looks like a serious architecture problem to me (or backup systems, like generators, not being correctly tested... whatever). I am really curious about the future explanation with what happened exactly

edit2: Why all the downvotes? Even the status page of OVH is down, do not tell me it is good design. We are not here to be charitable, but realist.

"There are two kind of programming languages: the ones everybody hates and the ones nobody use."

MDN? [1] If you want something more official, here is the W3C doc [2]

[1] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Fo...

[2] https://www.w3.org/wiki/HTML/Elements/input/text

Talking from the developer point of view here, not the user's: I'm expecting things to be working the same way they are documented in the manual.

The changes some browsers have made to autoplay videos or alerts do not contradict what is in the manual.

You are right, but my personal problem here is autocomplete is automatically applied where it should not be. [1]

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=587466...

> they made all top-level event listeners passive by default. They call it “an intervention”.

This is my very problem with Chrome/Chromium right now. The Chrome team does assumption on how things "should" be (in a highly subjective way) and breaks the web.

Another example: they decided to ignore the value of `autocomplete` attributes on `<form>` tags [1], because:

> The tricky part here is that somewhere along the journey of the web autocomplete=off become a default for many form fields, without any real thought being given as to whether or not that was good for users. This doesn't mean there aren't very valid cases where you don't want the browser autofilling data (e.g. on CRM systems), but by and large, we see those as the minority cases. And as a result, we started ignoring autocomplete=off for Chrome Autofill data.

Problem: Chrome now auto-fills wrong parts of forms with username/passwords and this breaks forms that get unexpected data when submitted. And now, they opened an issue on their tracker [2] to track "Valid use cases for autocomplete=off".

This is insane to think that the developer is wrong to use some attributes values, and to assume how a page should behave, ignoring devs intentions and Web standards.

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=468153...

[2] https://bugs.chromium.org/p/chromium/issues/detail?id=587466

Kind of unrelated, but I was thinking about these companies making SaaS as browsers extensions for a living.

I mean, when you see the whole add-ons system from Firefox being reforged, it just feels extremely unstable to build a business on this. What if tomorrow, a new browser arrives, get a huge part in market shares but has no extension system so you can edit the content/DOM of pages as much as you want... You are screwed.

More a controversy than a disaster. The last commits [0] are only about governance model, discord link... There are some rebase but that's it. Nothing will probably come from this fork.

[0] https://github.com/ayojs/ayo/commits/master

There is an issue on Github with the idea of creating a runtime for Electron: you would only need to package your apps and a shared Electron runtime would execute the different app you have installed on your OS, a la Adobe Air.

https://github.com/electron/electron/issues/673