A backup is an emergency protection, not a primary plan. This attitude is dangerously close to making the backup a critical part of their uptime.
A backup is an emergency protection, not a primary plan. This attitude is dangerously close to making the backup a critical part of their uptime.
Well, with multiple users you’d need to decide what the use case is for the whole NAS and then work down from there.
Are you sharing everything in the NAS with everyone? In that case your NAS setup is fine, just a little permissive, because with RW to everything, the end users can break everything.
If it were me setting this up, I’d have different mount points for different users. 1 mount for each user that only they can read/write (not even you should be able to see it), and 1 mount that everyone can read/write, maybe if you want to go a little bonkers, 1 mount that everyone can read, but only you can write to.
Then you’d mount those three to separate mounts in your /media, and you can link them from your home directory for specific use cases.
Obviously this is completely overkill, but you can take the parts that sound appealing to you and ignore the rest.
How many users are there?
Is there a chance that the computer will boot without access to the NAS (aside from failure conditions).
Are you doing anything with ownership to prevent reading, or changing, sensitive files?
Legally, if I ask if you’re a cop, you have to answer truthfully.
0:36 Gaming.
4:38 Microsoft Office.
5:31 Photoshop.
7:15 Ecosystem of Linux.
9:39 Hardware compatibility.
Yup, in the same boat and that looks like a good plan.
You can tell qBittorrent to only use the VPN, and it kills any connection not using that tunnel.
I tested it with legal Linux isos and killed my VPN connection, and everything just stops.
So both the VPN service itself, and qBittorrent can be configured independently to protect you. Belt and suspenders.
It was a very old, unpatched Plex server running on hardware that had access to LastPass critical data.
If you ran very old FOSS with unpatched vulnerabilities, you’d have the same problem. It wasn’t Plex that did it, it was unmaintained self-hosting.
Plex has it’s problems, but this wasn’t one of them.
Careful, because 1337 had a recent scandal with Baldars Gate having a crypto malware in it and there was some involvement with the admins on that.
Seems fine with media, but careful using it for actual executables.
I know you said it was for movies, which I use them for as well, but there was a recent scandal with 1337 and malware in Baldars Gate 3.
Downloading movies is pretty safe, but if you decide to branch out, I’d be a little hesitant to use 1337 for anything else.
TL;DW - he needs reference screen grabs to make his screen accurate props, but lately in browser DRM has been making it harder and harder to take screenshots (specifically using a Mac on Amazon streaming service). So if he gets frustrated enough, he’ll just torrent a HQ copy and use that instead.
DRM is making it annoying for everyone, and you never own anything if you don’t have an unrestricted local copy.
(งツ)ว
But the music industry (mostly) figured it out. You can get the same song from a subscription to any number of services.
TV/Movies are still siloed. Once they figure out that it’s better to let you subscribe to one service and watch anything, that’s the day that most piracy will stop.
They don’t say why the US hasn’t paid out yet, and the way it’s stated in this article and the linked article inside implies that it’s a failing on the government side.
With the significant delays and attempts to bring in off shore labor, it’s much more likely that the factory hasn’t hit the targets needed to receive the subsidy.
The government is using the cash as an incentive to build the factory, not just handing out cash for no reason. Just like the Foxconn factory that failed in Wisconsin, they need to hit milestones to get the money, it doesn’t get handed out upfront, otherwise they’d risk a company just taking the money and running.