If you’re going for reliability, and you just want things to be simple, you probably just want to spend the money on two cheap NAS boxes, honestly. There are some caveats that come with RPi’s, and you’re unfamiliar it’s: 1) going to cost about the same, 2) be simpler to manage and upgrade, and 3) be easier to repair disk columes when the time comes.
Even if you’re just looking to make these redundant to each other, just make it simple and easy.
I print a number of label sizes on a Brother Laser as well, and have zero issues. Most of the media size and handling is done by the printer itself, and the software has little to do with it…for the most part.
I think it’s more about closing a backdoor to free product that was generally out of reach for most people a few years. Free API access for devs has been a thing forever for the most part, but the barriers are now lower for people to abuse it.
Yes about profits in the sense they don’t want people getting free access to content, but I don’t think this is designed to net them a bunch of money or anything.
This is going to become more of a standard due to people vibecoding their own clients for every dumb thing.
HA is definitely the largest adopted. OpenHab is probably more geared for developers, but has a more concise and powerful automation system.
As for hardware to run it on: get a cheap n100 Minipc and be done with it. Uses 6-12W, and it’s going to miles.kore efficient for this use than a regular PC.
It’s not the CPU. All that will do is consume CPU and raise your energy bill.
In general, it’s not an out of control CPU that’s going to halt your machine, it’s memory loss. If you have an out of control process taking too much memory, it should get OOMkilled by the kernel, but if you don’t have proper swap configured, and not enough memory, it may not have time to successfully prevent the machine from running out of memory and halting.
This is just poor security. Not like in TV/Movies where an “AI” was found “breaking layers of firewalls and encryption” or whatever 🤣
Somebody fucked up. Plain and simple.
When talking about media streaming, there’s a number of other things that cause problems Bandwidth, meaning the total amount of information you can send overall, is less likely to be a problem versus jitter, packet loss, and latency spikes.
For this purpose, but OP would tune both the server and the clients to cache ahead more, or send in smaller packets, it could possibly be a good workaround.
Spending an insane amount of money putting what I’m guessing is illegally obtained content on a CDN distribution is crazypants.
Bandwidth does not degrade over distance. That’s not how that works…
Again, I’m confused on what you’re suggesting the actual issue is here.
Uplink is exactly the problem. Not sure why you think otherwise. The internet doesn’t work by multicast.
You’re describing a CDN. You can’t afford it.
I’d look more into boosting whatever your uplink is versus trying to distribute to localized users.
Mkay. So you’re just some person out here on the Internet who has zero concept of how this works as well I’m assuming?
Feel free to dispute any single point I’ve made.
Well, let me break it down for you since you don’t seem to work in this space:
A Roadmap is a strategic timeline of targeted goals that are estimated to be completed in a specific timeframe that is NOT nebulous. It’s done this way to provide consumers of a product some knowledge of where the product is going to entice them to buy-in to said product to allow them to estimate their own commitments to the project and adoption.
A backlog is NOT a Roadmap. I planned orchestration of tickets is a Roadmap. We create this to ensure users that problems they are experiencing will be resolved, and in what order to expect them to be resolved. This works for both for-profit engineering, and also FOSS projects. A great example of this is the Roadmaps provided by distros uses by Enterprise customers.
Your comment about “inflexible commitment” seems to say you don’t understand the above points. If you’re pushing a product which you want people to adopt, and you’re communicating to them why they should adopt it, the last thing you would want to do is say “Hey, we’re kiiiiinda going this way, but maybe not. We’ll see.”
Programming DOES work like an assembly in a sense. That’s why you have tickets, tags, classification, triage, status, and…backlog. What gets thrown in the floor is what I’m talking about.
Regardless of how you feel about the pace of the project, it’s absurd to throw out a bunch of ideas as tickets and expect them to all get done without a commitment. Or, dare I say, a roadmap.
Helm sucks. You don’t even need it for what you’re trying to do.
Mint is for desktops. Hands down.
Run something paired down for servers. Fedora Server, or plain Debian are fine. CoreOS or Talos if you’re trying out some k8s stuff.
Yes, it’s mostly just package selection, but you don’t need to sift through the cruft and clean up all the desktop shit running you don’t need.
It’s a wishlist of Open tickets. Wouldn’t necessarily even call this a commitment to a roadmap. 75% of Open tickets will never get resolved anyway.
Docs say you can choose what to sync, and disable syncing entirely where you don’t want it: https://docs.nextcloud.com/server/latest/user_manual/en/desktop/usage.html
Pretty sure you should have the ability to choose what to sync, either from the server, or the client. Seems kind of dumb for it to automatically assume you have the space on the client device to sync EVERYTHING.
When you go to print, just look for the link that sends out the print job to your system settings. That bypasses the browser print stack. Probably solves your issue right there.