> Each user runs a server process, locally or on a remote machine.
Mastodon (and similar services) would benefit greatly from (a) requiring users to own their own instances, via commoditized hosting providers, (b) one-click or few-clicks transition between hosting providers, and (c) enabling serverless-style pricing.
Requiring users to own their own instances safeguards users from admin-shutdown.
Ease of migration safeguards users from poor hosting providers.
Serverless-style pricing (e.g. pay per federated message, not by CPU) reduces the financial barrier to entry for new and lite users who are not yet fully committed users.
Mastodon (and similar services) would benefit greatly from (a) requiring users to own their own instances, via commoditized hosting providers, (b) one-click or few-clicks transition between hosting providers, and (c) enabling serverless-style pricing.
Requiring users to own their own instances safeguards users from admin-shutdown.
Ease of migration safeguards users from poor hosting providers.
Serverless-style pricing (e.g. pay per federated message, not by CPU) reduces the financial barrier to entry for new and lite users who are not yet fully committed users.