Jellyfin didn’t have an app for my then 3-year old LG WebOS TV so, unfortunately, I couldn’t use it.
I know people are going to say I should just use a smart box connected to my TV instead of my TV’s smart features, but there’s a difference in usability that they’re not acknowledging.
I know this reference
I’ve heard that exact sound used on some computers (lottery maybe?) in gas stations in the US. I’m not sure why they picked that exact sound, but it’s definitely distinct and recognizable.
Uh oh
Completely true. And I would dictate my driving characteristics based on that fact.
I would drive at a speed and in a manner that would allow me to not almost crash into things. But especially trains.
In what way is it not ready to use?
To me it seems you just spent three paragraphs answering your own question.
can’t even see 50 meters ahead
didn’t understand what it was and how to react to it
FSD is not a finished product. It’s under development
doesn’t mean it’s obvious to the AI
If I couldn’t trust a system not to drive into a train, I don’t feel like I would trust it to do even the most common tasks. I would drive the car like a fully attentive human and not delude myself into thinking the car is driving me with “FSD.”
I’ve never hit a train. And I’ve also never almost hit a train. I think I could go my entire life never almost hitting trains and I would still consider that the bare minimum for a mammal with two eyes and a brain.
It’s unreasonable for FSD to see a train? … that’s 20ft tall and a mile long? Am I understanding you correctly?
Foolproof would be great, but I think most people would set the bar at least as high as not getting killed by a train.
Was the next Dropbox breach due already? I forgot to set a reminder.
I should have been more specific. I was hoping this fixes an issue with LO not scaling correctly when using multiple screens with different scaling factors. Unfortunately this is still an issue.
deleted by creator
Please tell me it fixes scaling issues on Wayland.
I used BlueProximity for a number of years and it was great.
It eventually became defunct, but that link appears to be a fork to bring it somewhat up to date. I have not tested this new version though since I work from home now.
This is disingenuous at best and incorrect at worst. The mute button on the Echo is just that, a button; it is not a switch. It is software-controlled and pushing it just sends a signal to the microcontroller to take some action. For instance, one action is to turn on the red indicator light; that’s definitely not physically connected to the mute button.
Maybe another response of pushing the button is to disable the transistor used for the microphone, but it’s more likely that it just sets a software flag for the algorithm to stop its processing of the microphone input signal. Regardless of which method it uses, the microcontroller could undoubtedly just decide to revert that and listen in, either disabling or not disabling the red light at the same time.
But I personally don’t think it listens in when muted. I don’t think it spies on us to target ads based on what we say around it. I’m not worried that the mic mute function doesn’t work as intended.
But I fully understand that it is fully capable of it, technically speaking.
For most utilities (water, electricity), there’s a relatively linear relationship between the tangible value provided (energy used, water dispensed) and the cost to provide it (coal burned, water sourced/treated). Even for wind- or hydro-powered electricity, the amount that everybody uses has a proportional amount of wear on the system and consequent required maintenance.
But not so much for ISPs. Instead, you’re basically paying for a “fictional” amount (speed) of a non-tangible product. Granted, there is a linear relationship to the amount of electricity the ISP uses to provide each bit, but it’s negligible.
Instead, what you’re paying for with internet is essentially to recoup the fixed costs of the provider’s equipment. They do need to upgrade every so often to accommodate more capacity and faster speeds, but this is proportional to speeds provided and not data volume used.
*edit: replied to wrong comment
I just checked again and you’re right! The app seems to now be available for older versions of WebOS whereas it wasn’t a year ago or so.
Thanks for the heads up!