For stuff like movies I simply use replication as my backup.
Since I share media with fruends/family, I act as the central repository and replicate to them on a schedule (Mom on Monday, Friend 1 on Tuesday, etc), so I have a few days to catch an error. It’s not perfect but I check those replication logs weekly.
I also have 2 local replicas of media, so I’m pretty safe.
You’re missing the point - he’s elevating cli above all else, which you don’t have on TV or mobile.
Yes, I know there are media clients, I’ve used them all. And that screenshot is hideous - compare it to Jellyfin on mobile, which looks just like Netflix used to.
Besides, he’s not doing anything different than running a “server stack” (which isn’t accurate, he’s still running a server, the device hosting the media services, even if they’re native to the OS).
Xerox Parc didn’t invest millions in the 60’s and 70’s because CLI was so great.
We don’t use CLI on our microwaves, toasters ovens, tv’s clocks, lights, etc, for a reason.
So, let me get this straight - you’re saying using command line to play video instead of a gui?
Tell me, how does one do this on a TV? On an iPad? Phone?
Your excitement for command line belies an experience of nothing but GUI, so it’s something of a novelty to use command line.
Dude, get ahold of yourself. I probably wrote more command line stuff before you were born than you’ve ever thought of - I’m not going backwards.
(As a clue, wrote my first Fortran program before PC’s were even a thought at IBM).
Fuck cli except for managing systems. Even then quite often gui is faster by orders of magnitude, mostly to kickoff scripts to do what I need. GUI was a godsend, and Xerox Parc’s efforts created a common GUI language for us, thankfully was embraced. I refuse to go backwards.
And forcibly teach non-technical people to use CLI?
You are exactly the type of person that Saturday Night Live lampooned decades ago.
Exactly, keeping components separated, especially the router.
Hardware routers “cost money because they save money” (Sorry, couldn’t resist that movie quote). A purpose-built router will just run and run. I have 20 year old consumer routers that still “just work”. Granted, they don’t have much in the way of capability, but they do provide a stable gateway.
I then use two separate mesh network tools, on multiple systems. The likelihood of both of those failing simultaneously is low. But I still have a single failure point in the router, which I accept - I’ve only had a couple outright fail over 25 years, so I figure it’s a low risk.
Separate devices provide reliability and supportability.
If your all-in-one device has issues, you can’t remote in to maintain it.
Take a look at what enterprises do: redundant external interfaces, redundant services internally. You don’t necessarily need all this, but it’s worth considering "how do I ensure uptime and enable supportability and reliability? ".
Also, we always ask “what happens if the lone SME (Subject Matter Expert) is hit by a bus?” (You are that Lone SME).
To be fair, the pro plan is for the non-local stuff, which is at least understandable as domains and resolution services are non-free.
Also ongoing development takes resources. Seems like a reasonable approach.
I say this as someone who absolutely despises subscriptions.
Is it?
Even if you own said lock?
Google has always been evil. Why else was their byline “Don’t be evil”?
If you have to make such a disclaimer…
So much this.
Why is Signal hosted in one location on AWS, for example? That’s the sort of thing that should be in multiple places around the world with automatic fail over.
Depends on who we’re talking about. Companies like finance orgs are all about legal contracts and would be able to hold their feet to the fire.
You don’t want to go to court against a finance company or any very large org where contract law is their bread and butter (basically any large/multinational corp).
Amazon’s not hosting just small operations.
Much of this stuff is automatic - I’ve worked with such contracted services where uptime is guaranteed. The contracts dictate the terms and conditions for refunds, we see them on a monthly basis when uptime is missed and it’s not done by a person.
I imagine many companies have already seen refunds for outage time, and Amazon scrambled to stop the automation around this.
They’ll have little to stand on in court for something this visible and extensive, and could easilyose their shirt with fines and penalties when a big company sues over breech when they choose to not renew.
Just cause they’re big doesn’t mean all their clients are small or don’t have legal teams of their own.
I just added a 30mm case fan to my SFF. I went with a compressor style given the space constraints and restrictions (they tend to draw more current because of the load).
It increased draw by <1 watt - it barely registers on the meter.
I don’t think fans really make much difference. My 120mm compressor is 4w on the label (which is peak load, like startup). It probably drops back to 1/2 W after startup. And that’s a huge fan in a compressor style, equivalent to a 200mm+ in a conventional fan.
Yea, it’s the end of the world with Signal.
Having such a dependcy just exposes yet another way their story doesn’t add up, like dropping SMS support because of engineering costs. Apparently, SMS is so hard to do there are free SMS apps.
I can’t trust them at this point.
And how does E2E require a middleman?
More like it’s their store-and-forward servers. Why that’s on AWS, or more importantly not distributed with auto fail over is a major fail, as in “get fired” failure.
Seems like firing a hacker is a dangerous move
Ffs Signal went down with AWS??
Fossify calendar can do this, but it’s manual. So you’d have to change the color for the event by editing the event.
Neat idea though, to color events by attendee, though that would only work for a single person, which is why it’s by calendar - the thinking being a calendar can be for a given subject.
I have calendars for myself, for household stuff, shared calendars get a unique color, etc. It’s pretty easy to move events to another calendar in Fossify. Just open the event and touch Calendar (near the bottom) and select the appropriate calendar. Or choose the correct calendar when setting up the event.
I have calendars on multiple services (approx 10 calendars) - yahoo (I know, right?) Gmail, mailbox, etc, with more than one calendar on each service. Colors work fine with DavX and Fossify, even with Thunderbird on my laptop.
Can you be more specific?
I first ran Proxmox on it (which ran fine, just overkill for my use-case).
Now it’s Windows server and anything I do on it is done in a VM via VMware Workstation (since it’s free). So the host os doesn’t see much change and any changes that break things can be rolled back via a VM snapshot. Proxmox ZFS would be better for this, but I don’t need it, yet.
You could run any Linux distro on it then use KVM for virtual machines and also docker for things like PiHole and Jellyfin.
There’s a million ways to skin a cat, though I like using VM’s so if I need to move a service I just copy the VM to a new box. Even my docker stuff is in a VM for just this reason.
I’ve run Proxmox on it, but it was overly complex and overkill for my use case.
Right now the host OS is Windows Server running VMware Workstation. Pihole runs in a VM (DietPi), which auto starts on reboot (as does my general purpose VM running Jellyfin). Fast setup, runs as my DC, VM’s as needed with enough performance (though not as much as I’d like for my virtualization goals).
Next box will be my own build since this one is limited on space.
For me Quicksync converts videos anywhere from 4x to 10x faster than using the GPU.
The only concern I see here is the external drive. My experience has been that powered off drives fail more often than constantly-on drives. So my external drives are always powered on, I just run a replication script to them on a schedule.
But you do have good coverage, so that’s a small risk.