Once the DNS is in place installing YunoHost is next, which will provide close RFC-compliance for web and email. Again, if you are an expert owner-operator you can use whatever you like, but #
TheRON is going to simplify around YunoHost and whatever is installed by YunoHost.
I have a NextCloud, a Mastodon and this Streams instance, which I nominate to be part of the standard stack. The idea again is to have two different YunoHost stacks for redundant email, and at least two different types of Fediverse nodes. More and different types of nodes like Lemmy or PieFed are recommended to make federation more efficient and more fun.
From here the so-called application stack is going to be used for the purposes and in the context of the owner-operator. My instance of #
TheRON will be focusing on issues in Kane County, Illinois. Two owner-operators still may build in same county, if their purpose and context is different.
Most people will be participants not owner-operators, so when two people build the same purpose and context it's up to the participants to decide which one to support.