https://youtu.be/EBb1bYakqMw?t=11m55s

“Even the hands?!”

If you haven’t seen Detroiters, do yourself a favor, and go binge it.

Well, actually… it’s ground into a powder, rather than the byproduct of sawing. I don’t think it counts.

What would you do if he wasn’t your dad? You mentioned you took full blame, almost as if you felt like you were covering for him, but I think even if it wasn’t your dad, you’re responsible for anyone you bring in, and the work they do, so taking the blame should be universal. And going forward, I’d expect a similar, universal approach. You could choose to not mention it but also not employ that person any more, mention it before the next job and ask them to be extra careful, change procedures to guarantee it doesn’t happen again…

I don’t think him being your dad should necessarily afford him special treatment.

Seizing “office property” isn’t going to disrupt customers in the same way as seizing a plane, and again, no one is saying don’t seize a plane, or don’t punish Ryanair - just don’t seize a plane with passengers already on it (at least without going through a process that includes a threat and a deadline, so the customers can, theoretically, be spared).

The logic you’re applying here would have all accounts frozen at a bank when a single customer disputes a charge, all parcels held when a carrier misdelivers a single item, grocery stores unable to sell food when one customer should have been refunded.

No one is siding with Ryanair here. But laws can be enforced and justice can be carried out, without disrupting the lives of everyone else. There were likely on the order 200 people on that flight who would have been caught in the crossfire of a dispute they have no part in.

What would the alternative course of action be? Seize the plane immediately, kick off all the passengers, and screw over a whole new set of people? The sticker may seem toothless, but it’s the court going through the (predefined) process. As long as they continue that process, there’s no reason to be upset at the court, yet. (If they don’t follow through, then perhaps it’s pitchfork time.)

This isn’t newsworthy. I’m not a fan of Vance at all, but his comments here aren’t even bad. If you read the article, the comments boil down to: “I believe this, I wish she did too, it’s fine if she never does, I love her regardless.” It’s honestly pretty healthy to be able to have that in a relationship.

This is practically at the level of criticizing Obama’s tan suit, and is just noise and distraction in a news cycle filled with actually bad things (multiple wars, the government shutdown, measles outbreaks, a hurricane, etc). Don’t spread this nonsense. It’s fodder for the other side to call people out for being focused on ridiculous, unfounded slights, and allows them to not pay attention to real issues. Make noise about things that matter.

Are you sure it’s not ukulele?

I don’t have as much experience with HASS, but I did use Mycroft for quite a while (stopped only because I had multiple big moves, and ended up in a place small enough voice control didn’t really make sense any more). There were a few intent parsers used with/made for that:

https://github.com/MycroftAI/adapt https://github.com/MycroftAI/padatious https://github.com/MycroftAI/padaos

In my experience, Adapt was far and away the most reliable. If you go the route of rolling your own solution, I’d recommend checking that out, and using the absolute minimum number of words to design your intents. E.g. require “off” and an entity, and nothing else, so that “AC off,” “turn off the AC,” and “turn the AC off” all work. This reduces the number of words your STT has to transcribe correctly, and allows flexibility in command phrasing.

If you borrow a little more from Mycroft, they had “fallback” skills that were triggered when an intent couldn’t be matched. You could use the same idea, and use https://github.com/seatgeek/thefuzz to fuzzy match entities and keywords, to try to handle remaining cases where STT fails. I believe that is what this community made skill attempted to do: https://github.com/MycroftAI/skill-homeassistant (I think there were more than one HASS skill implementations, so I could be conflating this with another).

Another comment mentioned OVOS/Neon - those forked off of Mycroft, so you may see overlap if you investigate those as well.

Chest compressions, chest compressions, chest compressions.

It can create a hard place. If the current government is a rock, these late night hosts can create a hard place, to catch the network between. The network cares about money - if the government starts taking away licenses, they can’t make money, so they’ll roll over (as they have done). But they can’t make money without their talent either, so the hosts can push back from the other side to maintain their platform/voice.

Will it work? Maybe not. Will giving up? Definitely not.

Silencing themselves is counter productive. They need to do the opposite. They need to use their platform to make as much noise as possible.

They can and should protest in other ways, but to sit out is to give the other side what they want, and to squander their ability to affect change.

*An official letter, signed by at least three colleagues.

What bugs me the most is I’ve pointed it out to people in conversations that basically go like this:

Me: You used it for X and caught mistakes - why are you trusting it for Y? Them: That’s a good point.

And then they keep doing it anyway.

I’m not an AI hater at all - it can be a great way to accelerate work you are capable of doing on your own. But using it for things you don’t understand, and/or not double checking its work is insanity.

I hate to bring up AI, but this is exactly what I keep trying to explain to people - when you ask any of these bots questions about things you’re an expert in, you see all the flaws. The trouble is people tend not to ask questions about things they already know…

I used Windows growing up, switched to Linux in highschool on my personal machines, and was forced to use Mac for nearly 10 years at work. In my experience, they all have problems, and the worst part is always early on. After you’ve used them for a while and have gotten familiar/comfortable, the problems get easier to deal with, and switching back (or on to something new) becomes more daunting/uncomfortable than dealing with what you have. So in that sense, yes, it will get easier.

Also, as hardware ages, you often see better support (though laptops can be tricky, as they are not standardized).

Keep in mind, when you use Windows or Mac, you’re using a machine built for that OS and (presumably) supported by the manufacturer for that OS (especially with custom drivers). If you give Linux the same advantage (buy a machine with Linux pre-installed, or with Linux “officially supported”), you’re much more likely to have a similar, stable experience.

Also, I’ve had better stability with stock Ubuntu than its derivatives (Pop!_OS and Mint). It might be worth trying an upstream distro, to see if you have better stability.

Go see a show at The Comedy Cellar. Book it in advance if you can. If it’s “sold out,” you can still show up and wait before showtime - I think they only sell about half the seats online, so if you show up 30-60 minutes before the show, you can probably get in.

The gang must have let Charlie make the sign again.

They updated the ride after the movies, so… It’s kind of circular at this point.

Raster images do not need to be rendered - see Rendering:

Rendering is the process of generating a photorealistic or non-photorealistic image from input data such as 3D models…Today, to “render” commonly means to generate an image or video from a precise description (often created by an artist) using a computer program.

Note that “render” is a fairly generic term, and it is sometimes used like “render to the screen,” to just mean to display something. Rasterisation may be a better term to use here, since it only applies to vector graphics, and is the part of the process I am referring to.

In any case, except for possibly reading fewer bytes from disk, the vector case includes all the same compute and memory cost as the raster image - it just has added overhead to compute the bitmap. On modern hardware, this doesn’t take terribly long, but it does mean we’re using more compute just to launch/load things.