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.
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.
Guess I’m a bit too young for that still lol. We got a pair of ISDN2 lines in 1994 (so technically also 256k lol) at home, but I was too young to remember that. With cable internet coming in 97, that was technically still slower than bonded isdn at the very start.
In a way I was very privileged growing up when it came to Internet. My dad’s company at the time paid good money to get all the latest (often testing phase) stuff to his house in return for being available 24/7.
Talking about Lan uplinks, in the early 2010’s I had the joy of working with a 20gb uplink at a small university LAN (the sysadmin got a good amount of free pizza and beers for that one). I spent a large amount of my savings on a 10gb NIC only to find out my hard drive couldn’t keep up lol.
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.
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.
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.
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.
For some reason every registrars dns panel has its own weird restrictions, bugs and interface quirks. Pointing the nameservers to Cloudflare at least makes for a consistent experience.
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.