Time to announce this plan: I am working on a redesign of the joinmastodon.org server picker. I am also planning to switch out the data source from instances.social to my own API. The main reason for this is the addition of a new guarantee that I would be able to give when linking to servers from joinmastodon.org: That those servers would meet certain standards and enforce some basic rules of conduct.
Below is a screenshot with old, uncurated data as placeholder.
I will be taking submissions over e-mail at first (I do not expect a lot to come quickly).
If you are a server owner, and you have:
1) A server policy against racism, sexism and transphobia
2) Daily database backups
3) At least one other person with emergency access to server infrastructure
4) Commit to giving users at least 3 months advance warning before closing down your server
E-mail firstname.lastname@example.org with the subject "Server submission". I'll try to figure out the blurb/category
@Tyrent The crux is in the screenshot already. Some extras would be: Daily backups, at least one extra person with access to the infrastructure (bus factor), and a committment to announce server closure at least 3 months in advance (no overnight disappearance)
Both 2) and 4) are applied in Mastodon.
I have daily databases running in a remote server of everything both media and databases, It's a nightmare to run but I have it and it works (I tested it).
About four, obviously I will give time in advanced for people to move to a different hosting.
@Gargron These are not strict at all, IMHO. It is the base line for a reasonable and reliable Mastodon instance. I like it.
@Gargron I'm not sure if "at least one other person with emergency access to server infrastructure" is possible in my case, since nobody else in my house knows how to computer
@Gargron although people who meet the requirements to join my instance (living in the same basement as me) probably don't need to find out via a website
@ben Online friends? What happens if you go on vacation and have no ssh access and something bad happens on the server?
@Gargron one time the internet at my house went out for an entire week
and if I don't have SSH access, I also don't have email or phone access because all of those can be done via all of my devices.
Just my personal take on this, but home hosted devices, not because they are hosted at home, but because they are usually not properly secure (i.e. no security around 24/7) and as you mentioned no "guaranteed internet connection" (in worst case) will provide a bad experience in some cases and should rather not be added to this list.
Maybe @Gargron wants to extent the policy for that.
Please consider adjusting!
1) A server policy to recognize the inherent human dignity of every person.
Reason: history shows labels (e.g. homophobia) are misused, often thrown around recklessly against those of opposing political or religious beliefs.
2) through 4)
Overkill as a rule for startup and other small instances. Unenforceable. Better: require instances to *state* their policy for administration, backup and shutdown notice.
@gms It's not enforceable but it's not meant to be. If someone deliberately lies about having backups that's on them.
@Gargron On (2), is it vital that's it's daily? My DigitalOcean droplet does weekly backups, and I'm not sure if there's an easy way for me to up that frequency.
@Gargron As long as you can commit the money. Iirc the terms were kind of clear on instances going down if you stop paying for the service. (?)
@Gargron I noticed open registrations is not on that list. In the past, social.coop hasn't been eligible for joinmastodon.org because we have a sign up process. Am I understanding correctly that is no longer a barrier?
@datatitian I can put you in the database but to *show up* registration must be possible. Approval-mode is acceptable. I don't know if that would work for your coop.
@Gargron oh awesome I think that approval mode serves exactly what we were trying to do with our registration process.
@Gargron Those are very sensible requirements that I doubt most admins satisfy. Most users seem to be picking their admin solely on domain name funniness and that can't work long-term... Can't wait to see the server picker changes!
I like this new interface. Its a good way to showcase instances and that users can trust they are decently maintained.
@Gargron Is there a chance that you will not be the only one to decide whether or not an instance is listed on joinmastodon ?
@Gargron I think it might be better to have an additional (and maybe by default selected) checkbox saying "curated servers only", and allow other instances to be listed when it's not checked. That way people could still discover all instances that they'd see on the page today.
@Gargron very nice, this provider onboarding is important! One thing I can recommend from our experience with @nextcloud Simple Sign up: only show one provider by default, with e.g. "change provider" below. That happens at https://nextcloud.com/signup/, with the provider being based on which is closest to you.
The original server operated by the Mastodon gGmbH non-profit