User agent strings are an outdated discriminatory concept. Browsers should be specifying supported JavaScript, HTML, and CSS versions instead.

That’s a lovely desktop picture.

Why are these voices a feature of the browser instead of the OS?

Would it be completely new and different? The only thing that changes is the rendering engine. The UI/windowing stays the same as the other iOS app. And the rendering engine has already been built for MacOS, so it’s not like they have to start from scratch — it’s the same base platform.

Oh? On another thread I was told Mozilla was a poor nonprofit that doesn’t have the resources to work on any additional browser builds. 😆

It’s disingenuous to act like this is some huge burden. You ship two browsers — one for the EU and one for other markets. Firefox already ships on a number of different platforms. Adding one branch isn’t going to kill them.

Or if it’s such a pain, you don’t bother and just ship the WebKit version everywhere.

Maybe that’s the problem though. W3C and their ilk needs to define which markup and features are part of a specific html version (5.0, 5.1, etc.) or CSS or JavaScript release. Lock that down and move to the next version. Declare your supported version in the agent string instead of wanting a specific browser engine like Chrome. Relying on Chrome is like the Internet Explorer debacle all over again.

If the app doesn’t the render the declared version properly, then that’s on the app. If the dev uses out of spec or experimental features, that’s on the dev.

I’d much rather see an alert that says “This site requires HTML 5.0.1 or higher” than “This site doesn’t work in Firefox.”

It’s time to get rid of the part of user-agent strings that identifies which browser you’re using. It should only include things like mobile/desktop, version of html supported, and JavaScript version supported.

I love the look and idea of Kavita, but I wish it was written in something like node.js instead of .net. It requires a handful of shared libraries on non-windows platforms, and I can rarely get it to work.

Xbox sucks as a streaming box, especially with Plex. If you try to choose something from the watchlist, it can’t send a url to the related streaming app.

Isn’t Firefox that browser that insists on rolling their own UI instead of using native controls on each platform?

Broken webpages might be a good thing. There are too many browsers that aren’t adhering to standards. Stop coding around it and start publicly shaming these megacorps.

It’s time to get rid of user-agent strings that declare anything other than desktop, mobile, or html version.

Try installing the Plex app on both your phone and your computer. Run the Plex server on the computer, then control it from the plex app on your phone.

https://support.plex.tv/articles/categories/features/casting-flinging-remote-control/

That should be possible. There was an old security cam app for the iMac built in camera that would do this. There was no motion sensor — you just stepped out of frame to take a “still” image and then the app would monitor for changes compared to it.

Didn’t Mozilla try this years ago and it turned out to be a flop?

I just wish there was a way to turn off logging. It really seems like unnecessary spam stealing processor power and disk writes unless you’re troubleshooting.

Ok, so the green screen background of the Technology Connections set was awesome.

Go watch some price is right episodes on YouTube — one from each year of the 1970s. It’s astounding how much the prices drastically change on automobiles and food just over a year or two.

Strangely, basic clothes washers, dryers, refrigerators, and stoves seem have the same pricing as today.

Randomly stabbing things at a microscopic level doesn’t sound like a good idea.