Raw files are uncompressed color and luminance channels, audio, and time codes. Photographers often want the raw data to post-process themselves before any editing.

The fact that your device produces these is usually sign of decent quality.

This is annoying, you don’t seem to understand what you’re being told.

Again, the SIM only grants token access, it has nothing to do with your phone’s localization. Your equipment needs to conform to local standards, and your LTE radio is likely locked to certain channels. For example:

These are the LTE bands for North America.

These are the LTE bands used in Asia.

They aren’t the same. If your phone is baseband-locked to the USA, you aren’t getting on certain LTE networks no matter what esim or SIM you have.

Because you bought your phone in the USA, and because “international” phones are not sold by USA carriers because that is how manufacturers create separate markets for smartphones and connected devices, you are very unlikely to have a phone that can work at all in Asia, Australia, half of Europe, South America, and Africa. There are even some incompatible bands between Canada and USA.

What people are trying to tell you is that unless you bought an explicitly “international” smartphone, your phone will be locked at the baseband level, meaning it won’t connect in the above mentions regions over LTE.

That means you’ll be likely restricted to WiFi only in those areas.

I agree. Are there inadequate sandboxing controls in AppImage? It works well on many platforms.

Thanks for the write up.

Lemmy prefers markdown, so you can make code blocks on Lemmy with backticks, this is inline code with single backticks at each end of the string, and this is a code block, with three backticks at each end in their own lines:

Block of code
2nd line
3rd line

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.

I would just say routing.

It’s most common to associate a vlan with a subnet for sanity, so i think “routing vlans” would be understood.

vlans don’t route to each other

Well, yeah. VLANs work at layer 2. What you are routing is the subnet you assigned to each one.

I just have never heard the term “cross routing” in my 30 years of networking.

What is “cross routing”?

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.