I don’t think you know what communism is.

I think you might be misunderstanding the role of a firewall.

Put your camera in another subnet, add rules at the convergence point (the router, in this case), done.

That is effectively what you’re doing with VLANs anyway.

or ones proxmox could make

In proxmox, ACME is a service for the root CA of the cluster. It does use letsencrypt, but it does not provide certs for clients.

Sounds like you are probably conflating DNS and PKI certificates.

Oops, you’re right. Still the QuickShnc GPU doing the detector work, though.

https://docs.frigate.video/frigate/hardware/

QuickSync is the GPU hardware used to infer from vino models.

https://docs.frigate.video/configuration/hardware_acceleration_video/#via-quicksync

Inference from GPU, even QuickSync, is better now than what TensorFlow was able to do on a Google Coral TPU.

Plus, the Coral drivers are untouched for the last 4 years.

It just previously avoided the bad optics of pulling a gun at their head, just so most people don’t know they’re hostages.

No, we all knew. And the optics were bad.

I use a local ntfy server and uptimekuma, which has built-in support for a ton of notification services, including ntfy.

You can also use the public ntfy server and create a topic there.

Finally, a correct take on Opus. Thank you.

With multiple DNS servers and zone transfers.

Yep.

There has grown a new class or worker, a class that goes to business school, and a class that understands neither the craft they manage, nor the leadership they serve.

Already a bunch of really good answers here, but I’ll add that I’ve wrestled with getting DBs to work well over NFS, and it’s doable, but you really, really have to know the particulars of sync on NFS and block settings on the filesystems and the db client/server at each end.

You know keepass is a local keystore, right? There is no “them”.

No? Most app versions of web frontends are a wrapper for a pwa (teams, zoom).

Ff dumped pwa support a while back, and it has only just come back.

That is an unrelated issue, clearly.

THEY ALREADY HAD THE MONEY FROM GOOGLE.

I see a lot of people shit on Firefox for integrating LLM-related features. What the blog post points out and people fail to recognize is that if Mozilla stopped maintaining Firefox, almost all of its forks would die.

You’re misreading why people are shitting on FF. It would have been nice if Firefox had actually worked on literally any other features in the last decade, like not trashing support for PWAs. Instead, we got nothing but stupid partnerships with companies for features not one wanted, and a succession of failures in the CEO seat of Firefox.

So, yeah, I guess I don’t think it"s realistic for Firefox to have ignored the LLM craze entirely, but man, they could have managed that Google money better.

I think you should look up the definition of “rube”.

I collect GPS tracks (whenever I go somewhere I haven’t been, hiking included), and I also use wanderer for basic editing.

However, Wanderer has been trouble to upgrade and recently I’ve decided to just back up my Comaps tracks and export individual ones for editing on something like https://gpx.studio/. What I really need is a local version of comaps for big-screen visualization and planning.

How is Wanderer helping you?

Classless interdomain routing is not the point of this post, but basically we started giving people more options for network sizes, and while complex in implementation, it was philosophically virtually uncontroversial.

You’re talking about 2 different things here. Bit masking part of what is now CIDR was implementable since the mid 90s on network segments, it’s the logic to route packets based on CIDR that was integrated into RIP, GRIP, and BGP.

Also, CIDR can’t alleviate multi-hop routing address exhaustion.