Compared to the original claim that it was kernel level and spread across literally everything?

No, no its not as bad as it was originally claimed.

Is it bad? Yes. Is it kernel level bad? No. It can easily be mitigated before a fix is out by blocking 631 and dns-sd traffic. It is not as bad as it was claimed to be.

Neat project! I especially like that it goes for raw keycodes, real nice approach.

Unfortunately the Windows support is a hard requirement for me, but hopefully someone else sees and takes advantage

Well, spoke to soon. I was banned for being 'uncivil' on the .world vegan community for calling out this same behavior, and hoping the community ended up somewhere other than on that particular instance.

Sooo.... yeah I'm keeping the block. Maybe expanding to some mods there would be sensible.

Edit: There, all set now.

Ehh... not at first. That was a later release.

I'll have to unblock, so I can do that later on, sure. Working so not paying much attention to Lemmy at the moment.

Edit: Sorry, my mistake, not a mod. An admin on the instance recommended / linked to in the side bar.

Juuuust about ideal, definitely.

There was no proof it was him who made a threat - that's the point.

There are ways to take away weapons from people when a threat is credible, during the course of an investigation.

There should be more limits on access to guns regardless.

The constitution needs an update. For one, this was not the purpose of the second amendment, and two, its an amendment - just like every other aspect of the constitution, it can be changed.

There is no gun crime without guns. The idea that we need to look anywhere else is, to me, absolutely ludicrous and shameful.

Edit: Regarding the edit - the fact that there is no right to education is also a problem, albeit a different one.

The idea that the 2nd amendment exists but nothing regarding education does should not mean "Well fuck all these kids because 1 out of several hundred may have actually been a threat" is completely deranged to me. Sorry, but there is no world where you're going to convince me otherwise. The problem is the guns.

Putting up protections on a bike lane is drastically quicker, they are nowhere near the same time scale.

That's what I do, nieces and nephews. They are a bit older than my kids, and their parents are not tech savvy.

I basically have a kids library for anything under PG, and I grab common sense media ratings for a decent estimate on appropriate age, and let them go from there. Then I use tags for what we find appropriate for our kids.

Some of them still use other things I wouldn't go near (YouTube kids, ffs that place is wild and weird), but that's their decision not mine.

FWIW I run mine off an 8th gen Intel, igpu for transcoding (though mostly I don't need to transcoded), on a little lenovo tiny workstation I picked up on the cheap. Storage is on my NAS.

Sure

The biggest thing to me is don't share the Internet connection. Get a separate line turned up to handle the session, with a dedicated firewall (commercial grade, doesn't need to be a palo alto or anything, but a mikrotik, Cisco fp, etc is fine), connected to a switch for just the zoom machines. No meeting connector or any of those shenanigans - the throughput is dedicated to the session. If it's the kind of place that can't do that, get share the pathway as little as possible, and provide that client endpoint with the highest priority. This is, to me, the most important part.

Production Studio will get used, but it's not really doing any of the lift - it's a full production studio before it hits that machine (which has a matching spec machine right next to it in case of failure, turned on and ready to go as a co-host machine). All it's doing is allowing for some border content, some backgrounds for content, session wallpaper, etc. Glorified OBS at that point.

Feeding it is usually a Ross Carbonite or a Grass Valley, but I've also done it with a black magic atem, Roland, etc. At this point, all the production is outside of Zoom, so any lower thirds, virtual studio backgrounds, etc. are all handled there. This way, if there is any issue with the main Zoom Prod Studio machine, there's a second video feed to the backup (co-host) PC. That's the only advantage/reason why I even bother with Prod Studio over just tossing a zoom room on a PC and walking away.

All production hardware is on a segregated network, no outbound internet or routes, especially if using Dante/aes67, NDI, qlan, whatever. Stacked switches if more than one is needed, no simple uplinks (ie: bottlenecks).

At that point not much else matters, grab your shure lavs (if there is density, axient) and a few wires mic backups, cameras at your preference (honestly a lot of BM Ursa/Studio with good cine lenses, mostly primes), and good to go.

Couldn't tell you about Discord, sorry, don't really use it.

Just to mention, smaller scale production takes the same tactics, just without a GV/Ross/etc, more likely a BM ATEM or something. But I don't deal with that too much these days.

More often than not, I'm designing a studio which can also run webinars. For a presidential candidate, they probably did something similar, maybe making use of a few tools not public yet (though I wouldn't have risked it with an event like this).

Teams can be much more problematic, it's like a firehose of traffic, using whatever you give it. Looks good when you have the bandwidth, making the first statement - not sharing the connection - even more important. Zoom is heavy on the compression, but quite stable as a result.

Recordings should be local, with the session also recorded, so the session can be distributed with the local recording edited in for a better quality result. Remote participants, when I have to deal with that, get a full kit including a local recording system (aja mostly), so the drive can be shipped back with the kit for the finals edits.

Lawnchair hasn't had a new release in like 6 years.

Personally, I'm using Kvaesitso (available on fdroid). https://github.com/MM2-0/Kvaesitso

It's the best I've found for me post-nova

And the easiest way to handle blocking in many apps too, quick and easy peasy.