Who gets to be the judge of speech liberties? Perhaps we need a bureau of the government to act in this manner, perhaps a ministry, who's mission is to determine whether words and opinions are true or not.
I wrote a chess game using StockFish, and had it play against another computer player that only made random choices. And what surprised me is how long it would take StockFish to beat the random player.
> Login management should be built into the browsers instead.
I would go even further than this, and say that a cryptocurrency might be among the best ways to build a universal login system. Imagine an Ethereum-like coin where the wallet is the username, and you spend the coins while authenticating, gaining privileges, and the blockchain stores your public info like a username and avatar that you can bring to any website.
I tried using this one time but unfortunately found it didn't work when I wore my reading glasses. The screen reflection off my glasses just whites out both eyes.
The web browser extension would communicate with the electron app server, NodeJS would not be needed in that scenario (the electron app includes the nodejs server code). You can write your web voice app with static client-side JavaScript which communicates with the Electron server through the browser extension.
Web Page <-> Bumblebee JS API <-> Bumblebee Extension <-> Bumblebee Electron App (DeepSpeech)
DeepSpeech with the pretrained english model is enormous (1.4GB) it's not feasible to load it into a web worker. It can run in a server, but then every website would have to run its own server side speech recognition servers which is difficult and expensive to scale.
Although the first release is not officially out yet, the NodeJS code is working and you can install the development version of the app server and try out the hello world app locally.
The solution involves running Mozilla DeepSpeech inside an Electron desktop application with a websocket server and client API that NodeJS scripts can interact with, to receive speech recognition results, utilize "alexa" style hotword commands, and text-to-speech. The electron app handles all the heavy stuff, and you just use a simple API.
A web browser extension can also make use of this API to bring these capabilities to web sites, but that part isn't finished yet.
The Electron version numbers are essentially meaningless now. I have no idea what even changed between Electron 4 and 8, the changelogs are all just bug fixes that didn't necessitate so many major version releases.
Also there are some NPM packages that have to create builds for specific versions of Electron, and those builds come out after Electron does, so I'm always 1 or 2 versions behind on Electron which leads into dependency hell situations.
This is turning out to be a bad decision because there's been 5 major version bumps in the past year, yet the functionality in Electron hasn't materially changed very much, mostly bug fixes and minor changes.
Anyone recall how fast the G4 chips got phased out once Apple switched to Intel? It was pretty fast. Granted, they were a much smaller company at that time.
I've been using DeepSpeech to learn to build voice controls for all sorts of things in JavaScript. And I've got a way to connect it to the web so you'll be able write speech recognition enabled web pages using client side JavaScript.