Self-hosted Delta Chat?
I've been thinking more about the hurtle of getting friends and family to use federated/self-hosted services. One of the issues to onboarding is people not "getting" the idea of picking an instance. This has led, in part, to "default" instances, like mastadon.social, that grow so large it almost defeates the idea.
I've been thinking that I really wish #DeltaChat had a web client. I have had a MUCH more difficult time getting folks to try that out than even #fediverse SNS. But I was thinking how the heck are you going to pull that off without @delta having to host the overhead for a robust web client and possibly host a gigantic server system that has to grow exponentially to keep everyone's email from all the possible email providers, really defeating the goal of their project.
This morning, I thought of a possible solution to both problems. What if you have a built-in transfer requirement. So you start with a default, say pleb.joinmastodon.org or noob.delta.chat and after a certain time (3 months or something) you have to either transfer to a new instance, including hosting your own client for in browser decryption web access to your encrypted mail chats or your account (in the case of #mastodon) or web client access (in the case of Delta Chat) is shut off.
Do you think this could work?
@delta_chat