Ultimately I am the one paying the bill currently so if I die nobody elses credit card is being charged.

In terms of other admins, this is actually happening. Some smaller instances like mine are in the process of setting up a sharing admin work between instances so that if someone is on holiday, the instance still has an admin who can login. This was only just started and is in the process. We have to create a lot of documentation and basic stuff to get it fully functional where another admin can login and fix something. Its not at that stage yet and will be a couple more weeks before it is. We did a test last night where another instance admin (boulder.ly) could connect to my instance via ssh but without documentation on what to do and check anything more than the basics of rebooting or restarting something isnt going to happen. Eventually we will get it to what to do if site has a critical vulnerability or is being attacked but not ready yet. Its a work in progress unfortunately.

P

I think without some kind of "incorporation" (or whatever the tech/FOSS equivalent of that is), most of these kinds of thing will be vulnerable to issues with the owner's payment methods failing. Even with donation options available it's almost always still being used to pay to the server owner in parallel to them paying server / domain costs out of pocket (and then reimbursing themselves with the donations)

That said, I have to assume there's some way to set up some kind of automated payment option where community donations actually fill a fund that is used to pay costs directly in case the maintainer drops off the face of the earth.

Do we know what happened with vlemmy?