I received the same error, but it was followed by this line in the logs, which might explain the lack of inference requests assume there is actual demand...

WARN STT backend failed health check — model will NOT be advertised

I disabled the audio model (had to remove it, it was so buggy) and then started up with a text only model. Serving started without error. The system simply has no requests. The economics seem like a mirage anyway.

I love how 'Music 80s' is channel 29, which was MTV on cable when I was growing up in the tri-state area in the 80s ;)

lol, I can't tell if you are serious or not, but it's a recreation in HTML/CSS.

I just assumed it was wasm

This is wonderful. Great job.

The single username and password fields usually allow the site to determine whether some sort of federated login is in place for your domain.

'What is a TV channel?' (said by my daughter to me recently)

In conjunction with Pirate Weather, to consume/visualize the data I've been using:

https://merrysky.net/

and

https://briefsky.app/

On android I use NativeAlpha for setting up Briefsky as "app" that opens in its own Android Webview "app" rather than a browser. It's almost like DarkSky minus the notifications.

https://github.com/cylonid/NativeAlphaForAndroid

Coming from Ruby and Python, I also prefer class components to hooks. I had to deal with hooks enough in Drupal/PHP which is in the process of deprecating them in favor of Symfony classes.

Drupal hooks have nothing to do with React hooks except sharing a name. What would cause you to compare the two?

Drupal hooks are a functional approach to design compared to the OOP approach of Symfony components. As in you use functions to modify/extend existing code instead of inheritance. That's the context of the discussion, not whether they are otherwise similar to React hooks. Anyway, I just tend to think more in terms of making things with classes/objects than with functions.

Sharing the same name, I presume.

No

Browser consistency for print styles is like building websites in the late 90s. Chrome, Firefox, Safari all handle margins, page breaks differently. Not to mention setting page/paper size...

If anyone enjoys this topic, I would recommend reading "A Thread Across the Ocean: The Heroic Story of the Transatlantic Cable" by John Steele Gordon.