I make podcasts when I’m not doing this.
Myths and Legends: www.mythpodcast.com
Mastodon: weiser.social/@jason
GPG: keyoxide.org/[email protected]
openpgp4fpr:A825533E6C2A1055CE5FB8D13016FA1937B4D948
Definitely a trade off between energy and security. I have PBS running on an old laptop backed up to Backblaze and wouldn’t change it for anything, though. Proxmox backups are flawless and have saved me so many times. But yeah, 16GB of RAM with that processor is overkill for PBS and will probably consume more energy than is needed.
If everything is Dockerized anyway, you could just skip the step where you backup to PBS and use something like Kopia to backup your Docker volumes to a network share or offsite, rebuilding with compose or whatever if you have an issue.
I think it’s possible to have false-positives. Like [email protected] said above, do a clear and scrub to see if that helps. It happened to me last month after some really intensive disk i/o and AI stuff and I did that and the drive hasn’t had an issue since.
Additionally, I plugged in one of my old, supposedly faulted drives from last year as an external drive on my desktop to test it out, and it is still working fine months later, so yeah, it appears that there is some possibility for false-positives.
Like another person said, make sure you have good backups and that the other drives are solid, but I’d take a wait-and-see approach.
Kids growing up today will never know the pure awe of going in a Blockbuster Video and playing Mario64 on a Nintendo 64 store demo for the first time. It was absolutely amazing.
I’m an older millennial and I’ve played a lot of cool games. Nothing comes close to that, though.
You can use sendgrid to send your emails. That gets around the port 25 problem, but everyone is right - you’ll have a difficult time getting through spam filters even with them.
I selfhost my own email mainly so I don’t have to go through the Google unsecured apps rigamarole every time I want to set up smtp for one of my services, but no one except protonmail gets it reliably.
Threads to reportedly allow account migration *from* Threads
The head of Instagram apparently says it’ll be possible to migrate accounts from Threads, retaining at least that part of the ActivityPub protocol. > Meta plans to eventually hook Threads into ActivityPub, the decentralized social media protocol that also powers Mastodon. That integration isn’t ready at launch, though, as I previously reported. When it’s enabled, Threads users will be able to interact with Mastodon users and take their accounts with them to other clients that support the ActivityPub standard. >As Mosseri puts it, this is a move designed to appease creators who have grown increasingly wary of relying on the whims of centralized social media companies. “I think we might be a more compelling platform for creators, particularly for the newer creators who are more and more savvy, if we are a place where you don’t have to feel like you have to trust us forever,” he says. If true, it seems like a positive development. This is a Mastodon (and Calckey and Misskey and everyone else, of course) account tool that I thought there was no way they’d allow.
Tangentially-related, I’m actually really excited to use Threads’s federation with Mastodon to bring interested friends and family over to Mastodon. If you get all the same benefits (connection, more people) with none of the ads or privacy downsides, then it seems like a no-brainer to join Mastodon over Threads.
But to answer the question, no. I run my own Mastodon (and Lemmy) server. I’m kind of all-in on the fediverse.
Proxmox Backup Server. It’s life-changing. I back up every night and I can’t tell you the number of times I’ve completely messed something up only to revert it in a matter of minutes to the nightly backup. You need a separate machine running it–something that kept me from doing it for the longest time–but it is 100% worth it.
I back that up to Backblaze B2 (using Duplicati currently, but I’m going to switch to Kopia), but thankfully I haven’t had to use that, yet.
