It's not a single tense (would have - past conditional, had to - past modal, have been - pluperfect), it's a hypothetical past state being caused by a hypothetical past event, but the trick here is that the "past state" is omitted because it's contextually read. If you were giving full context it'd read: "If it was spitting out sensitive information, it would have had to have been trained on it."
Take that, ESL learners!
This is the approach I use, not sure if it'll work for your use case but I can assure you it works for at least a few users. It's all sort of manual set up but from your comments it sounds like you're just doing this for friends and family and not on an enterprise level. I admire your efforts!
First off, I have a purelymail account on which I set up domains and accounts for each user. I have mine set up so user1@anydomain.com all goes to the user1 mailbox (and user2@anydomain.com goes to the user2 inbox regardless of domain, etc.) but you can set up some pretty complex routing if you want - and if you know a bit of sieve there's even that. Purelymail handles the actual email sending/receiving so I'm putting a lot of trust in them, but it seems like they have a good track record and I don't think I could do better on my own. Plus they're dirt cheap. My big concern with email is always deliverability. Anyway, you'll see this is all set up in such a way that I'm using purelymail now, but I'm not tied down to them.
Second, I use this image (linking to the repo and not the docker hub version so you can inspect the Docker file for opsec reasons. In my set up I build it from source because I have a couple modifications) which is a dovecot IMAP server + getmail. This is python getmail not go-getmail and not fetchmail. The repo itself has some pretty straightforward instructions but the way it works is basically that users inside the docker container each map to a mail directory. So each user's credentials is actually a Linux username and password within the container. I have mine set up so it's like user1, user2, etc. (which confused my users initially because automatic set up forms are never set up this way) but you could set it up however you need. Then, there's a Cron set up to run getmail which you have to configure yourself within a cron.d folder that you mount on the container. For mine I have it configured to use POP3 so that when it gets stuff off purelymail it's automatically deleted.
Finally, you just set up your mail clients to use this IMAP server and purelymail's SMTP but if you know how to set up a forwarder you can always have it relay through purelymail. Purelymail even has the ability to relay emails to your SMTP server.
I'm pretty sure if you double click a .deb it opens in Discover (or whatever the app store thing is called) and from there you can install it.
Any other heavy machinery generally needs a license and regular recertification that requires you to basically take the test again. And anywhere you'd be operating generally has other people who have also undergone their own safety trsining. But giant 1-ton metal machines that go on public roads co-occupied by random pedestrians? Just come round every so often so we can give you a new ID.
You could check out Frappe Drive (and Frappe, the framework it's built on, it's pretty awesome). They aren't accepting contributions at the moment but I'm sure that'll change once it's out of beta like with the other frappe apps. There's also Raven messenger also built on Frappe and you can use the two together (but without any real integration between the two yet, but that's on the roadmap on the Raven side).
I've spent a lot of time researching alternatives and NextCloud is the only one that does everything it does in one place. I've dug into the code a lot to find places to make it work faster and came out confused and mostly empty. It's also federated, and I think it's the only FOSS file sharing platform that is. It''s a very mature application so you'll be hard pressed to find features that are missing, but also to find things that could be further optimized without ripping out major chunks of the application which are likely interconnected with other major chunks of the application. For my personal use NextCloud instance I've resorted to just completely deleting the database and installing everything fresh between major versions, then just rescanning my local folder.
Well if you're not doing anything wrong why try to hide it at all?
/S
You also need an eye for the right aesthetics and some marketing savvy, there's lots of pretty girls who still don't meet the cut for "influencer". Granted, being pretty and having marketing savvy is a really good recipe for success, but it still makes no guarantees.
80 episodes an hour? That's gotta be a typo, right?
To some it comes easy. To others, the ways of the heart are an enigma.
That would work for my... Uhm... Purposes...