Organizational Principles

Don't Be Evil (for real this time)

This project is to improve the state of our lives and society at large, it should not be possible for people to co-opt it for profit. If a decision can be interpreted as "Evil" don't do it, it is not worth it. The cost structure should support the primary function of the app, and not collect extra if it's not necessary.

Keep it Simple and Explainable

features should be easy to understand, and intuitive. Any algorithms implemented must be clear, not a "black box". Opt for simpler processes when possible, and remove unnecessary features. Do not overload people with information, it should be clear what they need to do to be successful from the beginning.

Let the User Decide

filtering matches should be in the hands of the user, we don't need to automatically arbitrate. If they want to segregate people, let them because that minimizes negative interactions with those marginalized people. However, show them the analytics and let them see the consequences of their actions clearly. Reduce the amount of auto-moderation, and let local communities decide what they want, and what they don't want in their platform. If someone is reported by another user for bad behaviour, take it seriously. If nobody complains, do nothing.

Trust & Privacy

Avoid saving unnecessary data whenever possible. Tell people exactly what data we are saving in clear and plain terms. Any contract that they have to sign should be reasonably digestible in a short period of time. Operate openly as much as possible, and share how algorithms work. Do not take actions that would result in people losing trust in the product or our organization.

Avoid Lock-in where possible

Use modularity is designed when possible and sticks to open-source alternatives when possible. If using closed source products, make sure that data can be exported if necessary. There should be no outside force that can shut down the project if they choose. Use containers whenever possible. The entire tech stack should be portable if necessary. There should be built-in and practiced escape plans.

Build-in Backups

There should always be a business continuity plan. The success of the project should never be dependent on the active contribution of any individual. Anyone should be able to leave the project at any time, and the project should continue functioning. User information and the backend technology should be robust and have backups to prevent downtime and loss. Figure out alternatives to core infrastructural components if they fail or go closed source.

Cover your Ass

Take the required steps to do things by the book, and do it right. Make sure that legal issues are taken care of and that liability is directed to the correct places. Read agreements for the software we adopt to ensure we can comply properly with the contacts we make.

User Equality:

All of the users are equally valuable as people, and should be treated as such.