Star Trek is more real sci-fi.
You owe me a new keyboard.
Put all your mail on an imap server. You'll be able to access it with any mail client. Set up the imap server as the archive destination for TBird. Now all your mail is archived in the imap server and is accessible.
You don't trust your email host? That's fair. Run your own imap server on your NAS or even your desktop machine. Everything stays right there on your own media and is still future-proof with regard to changing clients. If you need to change servers you just use your favorite email client to transfer mail from one to another.
I have everything online at my email provider. In my case, "everything" goes back to the mid-90s. I recently switched hosting providers and did just as I described: Set up separate accounts in TBird with the old and new providers. Select all in a folder on the old provider, drag to a folder on the new provider. (Well, actually I had to do it in chunks of under 5000 messages or TBird would get all crashy on me. But you get the idea.) It was kind of tedious to move hundreds of thousands of messages, but it was merely tedious. It wasn't problematic.
First, I don't believe anything I read at Indiegogo.
Second, if this is on the up-and-up... Cat's out of the bag, I guess. If this guy can do it so can any number of other guys, including your favorite bad guys. Quit talking about how to prevent it and start talking about how to cope with it.
Thank you. I've been saying this for years. I'm glad someone else can see that the Emperor has no clothes.
SQL sucks. Not the concept of a relational database; that's something that's pretty cool. But the so-called "Structured Query Language" used to interact with the database is the worst affront to programming ever(*). It's not bad for user interaction, and I know it was an easy path to hacking in database support for languages that didn't have it. But for crying out loud, continuing to use it is just like passing a single string to the shell for execution. You never do that, you use execv() or whatever your language has for a wrapper around it. At the very least you should be able to do the same damned thing for your database!
(* One could argue that PHP or AppleScript are worse. I won't quibble.)
I tried to go all high-tech this year. What a disaster! First, let me tell you that when the manual for the revivification table says it needs a bolt of lightning, you can't just substitute wall current. You need real lightning or you don't jump-start the corpse, you just end up charring the internal organs. Right away that puts a requirement on the weather and limits you to working during thunderstorms. And you don't want to deal with a thunderstorm on Halloween night. That keeps all the trick-or-treaters home. It's getting harder and harder these days to lure kids into your basement. Halloween's the one time of year when kids are *supposed* to accept candy from creepy guys in poorly-lit houses! You don't want a little thing like the weather screwing up that chance or you might not harvest enough test subjects to last through the year.
Next year I'm going back to good old-fashioned necromancy, just like we did when I was a kid. Sure, it takes a little longer and the entrails really make a mess, but you know you're going to get an unliving minion out of it instead of just a charred corpse that's too burned even to bother to eat. With necromancy, even if the ritual goes wrong the worst that could happen is you'll end up with an unholy abomination that will try to turn on its creator. Anyone who can't handle that once in a while doesn't deserve to call himself "mad".
If you are smart enough to know that you're not smart enough to be an Engineer, then you're in Business.