Same. It’s a very useful trick for scuba diving.

I have that with my thumb. A very useful QOL mutation when it comes to pushing on things

For most hobby projects I just try to stay within the jlcpcb smt assembly parts library these days. For some reason it has actually gotten harder to get parts locally over the years as a consumer.

That has actually lowered the bar for small prototypes/projects enough that I’m using it for some company projects (PCB design isn’t something we normally do but it can be very useful at times).

Also you need to pay (18k/year iirc) in addition to that as well. Next to the fact that matter itself is quite convoluted from an implementation standpoint.

It’s really not made with things like startups or niche products in mind. It’s really a standard by and for the big companies

If you have a surround setup, try boosting only the center speaker. Dialog is usually played through that.

Someone else mentioned a compressor. If your tv/hifi has a night mode, it’s doing that exact thing.

If it’s only you (or your household) that is accessing the services then something like hosting a tailscale VPN is a relatively user friendly and safe way to set-up remote access.

If not, then you’d probably want to either use the aforementioned Cloudflare tunnels, or set up a reverse proxy container (nginx proxy manager is quite nice for this as it also handles certs and stuff for you). Then port forward ports 80 and 443 to the server (or container if you give it a separate IP). This can be done in your router.

In terms of domain set-up. I’ve always found subdomains (homeassistant.domain.com) to be way less of a hassle compared to directories (domain.com/homeassistant) since the latter may need additional config on the application end.

Get a cheap domain at like Cloudflare and use CNAME records that point domain.com and *.domain.com to your dyndns host. Iirc there’s also some routers/containers that can do ddns with Cloudflare directly, so that might be worth a quick check too.

Kinda the same thing as winrar. They rather have consumers get used to it so the companies they work at have a higher chance of buying licenses. That’s where the real money is.

There’s a couple SD-WAN solutions out there that you can do this with. Essentially route all your traffic through one or more VPSes while still keeping things like port forwards and STUN working properly.

I’ve had to use it to enable proper video feeds to and from people that had Spectrum as their ISP.

HEVC actually requires a $1 license you can get from the ms store. It’s a royalty thing. OEMs often ship PCs with that license already enabled.

There are more applications than just windows Media Player that won’t play hevc files/streams without that license installed.

VLC doesn’t really seem to care about those things though and it’s better than the default anyways.

A lot of sensors/gauges in industrial applications are retrofitted with lorawan or similar remote readout capabilities right now. Battery life for these devices is already a big design consideration, especially since not all locations are easily accessible.

With a power source like this you would essentially charge a capacitor, use the stored charge to do a sensor read and short data burst, and then wait for the next charge.

It does exist, its called 801.11ah or wifi HaLow

That standard is mainly designed for things like IOT and wireless security cameras, but nothing stops you from getting an HaLow access point and network adapter.

https://www.youtube.com/watch?v=qF0BHnmi9j8

People have done it on M1’s at least. You’ll need a well equipped rework station to do it though, especially since the NAND is essentially glued to the motherboard in addition to solder.

Nog defending this practice at all, but a fun little fact is that if you get a Mac instance on AWS (and other cloud providers) It’s literally a normal mac mini in a rack enclosure.

They did have some programs to try and push more apps, but dropped the ball far too quickly for it to gain traction.

Microsoft essentially shipped free phones out to everyone that wanted to make or port a windows phone app. Heck, I got one just to port over the schedule app I made for my small high school at the time and had maybe 300 installs.

The dev environment was actually a lot nicer to work with than the android one at the time as well.

What kind of storage usage can I expect from running this? I would also assume that the database would heavily prefer solid state storage?

Edit: the author answered that question here already: https://lemmy.world/comment/4148270

You essentially pay for convenience. If there was a streaming service that had everything I would gladly pay good money for it, since there isn’t, I have to curate my own library instead.

Having good indexers/Usenet providers and automations takes away a lot, if not all the time needed to hunt down good releases. That saved time and hassle is what’s worth the ~100/year for me.

Doesn’t steam allow you to pick a specific update for your game?

Between power, hardware depreciation, Usenet/indexer fees and VPN I probably pay somewhere like €50/month to curate my own media collection.

I’d be happy to pay the same for a legal platform that has all the content I want in the same place, like Spotify for music (which I use and pay for).

Right now the piracy experience for movies/series is simply superior to the legal experience , so there is absolutely no incentive for me to switch things up.

I definitely rely on documentation more than copilot, since I’ve noticed that the code it writes is only ever as good as your own codebase.

Most of the stuff I code is API wrappers to get arbitrary data into a format our broadcast graphics system can understand. Once all the data structures are properly defined copilot is extremely useful in populating all the API endpoints.

The actual problem solving is getting the data in the first place and morphing it into the correct format.

I’m very much a novice coder, but I often find myself doing the opposite. Write a good comment and let copilot write the actual code.