It has very little to do with ease of implementation. It is a conscious, principled decision based on our years of experience as Toastmasters members, District officers, and past experience with clubs' bad behavior with FreeToastHost version 1.0.
While we do not want to be considered the "bad behavior police" to prevent Toastmasters clubs from engaging in bad behavior and abusive practices such as spamming guests with meeting agendas, we also do
not feel obligated in any way to implement or enhance features that we are pretty confident would allow for such behavior and/or would adversely impact the email reputation of the FreeToastHost server.
For example, clubs could figure out ways to spam guests with meeting agendas, but we do not have to make it easy or sanction it.
There are just some features and enhancements that we will never implement even if we know we could. There are also some limits and functional guardrails in place in the system that will never be removed. Some limits and functional guardrails are in place to limit bad behavior and some are in place to extend the long-term functional viability of the system, which runs on only one server and is supported by a small team of volunteers.
- We will never implement automated (on a recurring schedule) bulk emailing.
- We will never allow meeting guests to be treated as if they are club members in the system. The two are distinct and will always be treated as such in the system.
- There will always be a limit to how many officers can be assigned certain admin functions.
- You must opt-in to the system to allow your personal information to be used in the system. (data privacy requirement)
- etc., etc.