Don’t worry, you aren’t missing much. That paragraph was kind of goofy anyway.

Think of a Seedbox as a cloud service provider with convenience features focused on enabling piracy, by keeping the hardware in a jurisdiction that doesn’t care what you pirate and giving you one-click easy installation methods for apps that make piracy simple. But without going so far as “Thank you for your payment, download these specific media files here.”

You debatably have to be a techie. But by techie standards it’s very easy to use.

If you really hate piracy, I suppose you could pay for one for a month, get the identity of who you paid, and use one of the apps to host a shell script that listens on one of the few public ports you have access to, that answers every incoming connection with “this is a seed box operated by ABC, with cards payments accepted by LMNOP Inc in Athens, Greece.”

But the most common usage is running packaged software they let you run (like BT clients you can remote-control, sickchill, radarr, sonarr, Plex, etc.) or remote desktops or shells. Usually implemented as docker containers.

Scrooge McDuck is an employee of his companies too.

BBS software. Nerds always find a way. I guess if I have to be a sysop now…

I feel like objecting to the “General advice about email is don’t” thing but I don’t know if I understand the objections well enough to refute them. I self host email for mspencer.net (meaning all requests including DNS are served from hardware in my living space) and I have literally zero spam and can’t remember the last time I had to intervene on my mail server.

On one hand: My emails are received without issue by major providers (outlook, gmail, etc) and I get nearly zero spam. (Two spam senders were using legitimate email services, I reported them, and got human-seeming replies from administrators saying they would take care of it.) And I get amusing pflogsumm (summarizes postfix logs) emails daily showing like 5 emails delivered, 45 rejected, with all of the things that were tried but didn’t work.

On the other: most of the spam prevention comes from greylist, making all new senders retry after a few minutes (because generally a legit MTA will retry while a spammer will not) and that delays most emails by a few minutes. And it was a bear to set up. I used a like 18 step walkthrough on linuxbabe dot com I think, but added some difficulty by storing some use and alias databases on OpenLDAP / slapd instead of in flat files.

But hey, unlimited mail aliases, and I’m thinking of configuring things so emails bounce if they seem to contain just a notification that terms and conditions are updated somewhere. I don’t know, cause some chaos I guess.

And I have no idea if my situation is persuasive for anyone because I don’t know what the general advice means. And I worry it’ll have the unfortunate side effect of making self hosting type nerds like me start forgetting how to run their own email, causing control of email to become more centralized. And I strongly dislike that.

Yep, mspencer dot net (what little of it is currently up, I suck at ops stuff) is 2012-vintage hardware, four boxes totaling 704 GB RAM, 8x10TB SAS disks, and a still-unused LTO-3 tape drive. I’ll upgrade further when I finally figure out how to make proper use of what I already have. Until then it’s all a fancy heated cat tree, more or less.