1. VM running on a proxmox host. Tips: make sure you know your backups are in a state you can restore data from them.
2. Nightly backup via proxmox to Hetzner Storage box with 2 day retention. I’d like a local copy too but I don’t currently have hardware for it.
3. Don’t know. Personally I have a DNAT rule on firewall and my instance is directly open to the internet. You might not want that and I might not recommend it, but right now, for me, it works. I’d need to look in a VPN solution for android I could replace the current ‘open for all’ situation.

Actual shortage. Performance drops significantly when zfs doesn’t have enough memory. It might have been an option to tweak configuration for zfs pools, add SSD for caching and so on, but I needed to change drive configurations anyways for other reasons so for me it was easier to drop zfs and switch to software raid.

How much RAM your system has? Zfs is pretty hungry for memory and if you don’t have enough it’ll have quite significant impact on performance. My proxmox had 7x4TB drives on zfs pool and with 32 gigs of RAM there was practically nothing left for the VMs under heavy i/o load.

I switched the whole setup to software raid, but it’s not offically supported by proxmox and thus managing it is not quite trivial.

I mostly use battlestar galactica ship names for my own hardware, but it’s been mixed with boring ‘<function>.mydomain.foo’ names as well. I should rename a bunch of stuff around and include them in my DNS.

The exchanged mails between the IMAP host and the MTA need a unique identifier to organize contents of the DB, and this would not be possible or automatic if your switched the upstream MTA.

It sure is possible. I’ve copied maildirs over different software, different servers, local copies back to the server and so on. Also if you just rely on your own IMAP server the upstream doesn’t matter as fetchmail (or whatever you choose to use) anyways communicates between hosts on their preferred protocols.

Obviously there’s a tradeoff since now you’re responsible for your backups and maintaining your server, but it can sit nicely on your private LAN with access only locally or via VPN without direct access to the internet. And you don’t need MTA to run IMAP server in the first place.

You can run a dovecot (or any IMAP server) where ever you want and use fetchmail to pull data from POP-server into it. There’s plenty of discussion and instructions around the web so I won’t copy’n’paste them here, search for ‘fetchmail dovecot’ or something similar.

Can you switch to console? Try ctrl+alt+F2 when the system is booted up and log in to that.

I suppose some package update was interrupted or crashed. You can attempt to re-run what’s missing with ‘sudo apt-get install’ and ‘sudo dpkg-reconfigure -a’. And, assuming your console access works, you can at least check log files on what’s wrong, but for that I don’t think any generic ‘read /var/log/syslog’ file is too helpful as there’s a ton of stuff and with things like journalctl it’s pretty difficult to navigate around if you don’t know what you’re looking for.

And also, more details would be helpful. What you mean by ‘enters a loop’, what it actually says that went wrong and so on.

Dammit, my organic memory failed yet again. It’s been a while since I’ve seen that prompt (and I have agreed to that as well at least few times).

Does anyone sell ‘Yes, Do As I Say!’ stickers?

You could possibly recover from that on console, just install few metapackages. And have backups.

I meant that the technology itself is reliable. And you can do self hosting just fine too, I’ve been doing it since 2010 or so, but running a local smarthost which sends messages via reputable SMTP provider works just fine too. Or even directly interacting with the SMTP provider from all the applications you’re running.

Advertising spam.

Commodore 64 is a home computer released at 1982. Modern expansions for it allows the thing to actually have tcp/ip stack and it can run things like telnet, but your single mastodon server, in comparison of what was available in 1980s, is pretty much equal of the whole bandwidth and storage of the internet (or arpanet, depending on how you want to time things).

Mastodon server requires (roughly) at least 2 gigabytes of memory and 20 gigabytes of storage. And with that it needs at least dual core 2GHz CPU to run it.

Commodore 64 had 1Mhz. A million hertz sounds like a big number, but we’re talking (at minimum) of two processor cores running with 2000 million hertz. Also, C=64 had 64 000 bytes of memory while the absolute minimum to run mastodon instance is 2 000 000 000 bytes.

And then there’s the storage. Your minimum mastodon instance should have at least 20GB of storage. 1541 used 5,25" floppy disks which could store up to 170 kilobytes. So you’d need someone to change disks as needed on a over 400 meter tall tower of floppy disks.

So, please tell me again where to get disk images to run mastodon server on a C=64 and how you just know that plain old email is garbage and old people just don’t know what they’re talking about.

you very much can not run mastodon server on a Commodore 64.

You absolutely can.

Ok. Send me the link of disk image of that. I have C64 laying around with 1541 disk drive. I’ll set up a public mastodon instance running on a C64 with a webcam stream of the setup.

I have no idea what any of that means…

That checks out. You conveniently skipped the part where I requested a single messaging solution which works with either modern android/ios devices or with anything you’ll find in your dad’s(or grandads I guess) drawer, can manage multiple recipients, escalations to sms/home automation bells, works reliably even if the uplink goes down for few hours and so on.

And no, you very much can not run mastodon server on a Commodore 64.

But you seem like a young and enthustiatic individual. I was one “a few” years ago. Keep it going, but that arrogant attitude won’t get you anywhere. Email has been a thing since the 1970s and there’s a reason why it’s still going strong. Things like XMPP has been around for a good while and there’s a reason why they’re not even close of overtaking email as a primary communication technology around.

You’ll live and learn. My guess is that when you reach my age, email is still working just fine and majority of the hot stuff which is around right now has faded to the history.

aren’t reliant on any particular company or service, and are easier to run and manage without requiring approval from your ISP

What other than email provides that? Browser notifications generally don’t work on mobile. Most of the common instant messengers rely on a single instance running the thing if you’re not suggesting sending messages via IRC or XMPP (or matrix or…) which have their own problems. App notifications require that you have the thing which app is running to be available and online and they more often that not require some spesific device. Also even if you had linux desktop “app” it requires that the software is running.

Also I have not met an ISP which would block sending email via gmail/amazon/protonmail/whoever. Sure, my current ISP blocks tcp/25 to the world by default, but you can request to open that too if you really want to and ports 587 and 465 are open, so you can work around that if you don’t want a smarthost for some reason.

With other options you wouldn’t need to because they already provide the features you’re looking for in those apps.

Which other protocol allows notifications at the same time on all the mobile devices, all the workstations and allow easy way to send the very same message to arbitary amount of recipients to all of their devices? I had email on a palm pilot device at 2001 or so, over mobile data with IRDA and you can read email even with Commodore 64 if you really want to (well, to be more spesific, use C=64 as an terminal for *nix server to access email, I think there’s no actual IMAP/POP client for it). There’s just no way for any other modern service to even try to compete with versatility with email.

And then there’s the more sopisthicated approaches like pushing email trough however complex procmail/perl/python/whatever scripting you like where you can develop quite literally whatever you can imagine. Set up a old fire alarm bell, hook it up to your home automation, process incoming emails and if it’s severe enough turn the bell on. Sure, at least a some of that is possible via instant messengers too, but with email I can be pretty sure that if I write a script today for it it’ll still run quite happily for the next 10-15 years.

Please do tell me which of the modern messaging alternatives offer all of that.

It just boggles my mind that we haven’t moved away from this archaic technology.

None of the alternatives are as standardized as plain old email. You can use whatever you like to read them, you don’t have to rely on a single company like Meta with WhatsApp for communication, it’s easy to use, pretty damn reliable and fault resistant and just ticks all the boxes you’ll ever need for a simple message delivery.

Personally I would absolutely hate if software started to offer notifications only on slack or signal or whatever. Just let me have my email and I can then read it with a browser in library, on my cellphone, on my desktop and laptop and on pretty much every other internet connected device on the planet. And if I want, I can pass that trough to teams, sms, all the messaging platforms and even straight to my printer should I need to. With other message delivery options that’s often either pretty difficult or straight up impossible.

You only need SMTP server, so the inbox size doesn’t matter (assuming you have another email where you want to receive those notifications). And even if you have separate inbox for alerts it’s quite unlikely that you get hundreds of megabytes worth of alerts every day and they’re pretty much useless after a day or two so there’s no need to keep them around.

In here ISPs commonly have SMTP service included on their service, so that’s worth checking. Beyond than that, any at least somewhat reputable provider will do as long as they provide traditional SMTP service. One option is to use a relay host on local network which sends mail trough a smart host so you can just use local unauthenticated SMTP server for all the things you run and that one service will then push the messages to the internet.

Yes. Their law doesn’t allow elections when martial law is in effect and it also states that the current president will hold office as long as the successor has been chosen. Plus, if I’m not mistaken, it was Ukrainian parliament (or whatever they’re called) who decided to not run elections, not Zelensky himself.

Also that 4% approval is complete bullshit, as the article states. If something Zelensky has a bit higher approval than before.

We’ve all been there. If you do this stuff for a living, you’ve done that way more than once.

You’d think you’d learn from your mistakes

Yes, that what you’d think. And then you’ll sit with a blank terminal once again when you did some trivial mistake yet again.

A friend of mine developed a habit (working on a decent sized ISP 20+ years ago) to set up a scheduled reboot for everything in 30 minutes no matter what you’re going to do. The hardware back then (I think it was mostly cisco) had a ‘running conrfig’ and ‘stored config’ which were two separate instances. Log in, set up scheduled reboot, do whatever you’re planning to do and if you mess up and lock yourself out the system will restore to previous config in a while and then you can avoid the previous mistake. Rinse and repeat.

And, personally, I think that’s the one of the best ways to differentiate actual professionals from ‘move fast and break things’ group. Once you’ve locked yourself out of the system literally half way across the globe too many times you’ll eventually learn to think about the next step and failovers. I’m not that much of a network guy, but I have shot myself in the foot enough that whenever there’s dd, mkfs or something similar on the root shell I automatically pause for a second to confirm the command before hitting enter.

And while you gain experience you also know how to avoid the pitfalls, the more important part (at least for myself) is to think ahead. The constant mindset of thinking about processes, connectivity, what you can actually do if you fuck up and so on becomes a part of your workflow. Accidents will happen, no matter how much experience you have. The really good admins just know that something will go wrong at some point in the process and build stuff to guarantee that when you fuck things up you still have availability to fix it instead of calling someone 6 timezones away in the middle of the night to clean up your mess.