Difference between revisions of "Starting new social media platforms"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
# Have clear '''[[#Reasons|reasons]]''' why existing platforms do not suffice. | # Have clear '''[[#Reasons|reasons]]''' why existing platforms do not suffice. | ||
# Have clear '''[[#Requirements|requirements]]''' for new platforms. | # Have clear '''[[#Requirements|requirements]]''' for new platforms. | ||
| − | # Have | + | # Have clear '''[[#Intentions|intentions]]''' outlined in a charter, constitution, founding documents, goals, mission statement, purpose, or whatever term you wish to call it. |
| − | + | # Have a clear '''[[#Structure|structure]]''' outlining the expectations, behavioral priorities, goals, authority, conflict resolutions, and disciplinary consequences. | |
| − | # | + | # Have a clear '''[[#Roadmap|roadmap]]''' of where things may develop. Include the realistic as well as your ambitious dreams. |
| − | # | + | # Have a '''short''' list of hard '''[[#Rules|rules]]''' that are black and white and crystal clear that '''must''' be followed. |
| − | # | + | # Have a '''longer''' list of grey area '''[[#Guidelines|guidelines]]''' with as many examples as necessary for clarity. |
| − | |||
== Community == | == Community == | ||
| Line 63: | Line 62: | ||
== Requirements == | == Requirements == | ||
| − | 3) Have clear '''requirements''' for new platforms. | + | 3) Have clear '''requirements''' for your new platforms. |
In addition to the [[#Reasons|reasons]] above... | In addition to the [[#Reasons|reasons]] above... | ||
| − | + | === Functional requirements === | |
| + | |||
| + | May include: | ||
* chat (open and/or private) | * chat (open and/or private) | ||
| Line 73: | Line 74: | ||
* groups | * groups | ||
* media | * media | ||
| − | * | + | * organized content (rank, tag, vote) |
* private chats and/or private messages | * private chats and/or private messages | ||
* sharing | * sharing | ||
* wiki | * wiki | ||
| − | + | === Technical requirements === | |
| + | |||
| + | May include: | ||
* backup and/or download | * backup and/or download | ||
| − | * compatible (Windows/Mac/Linux, PC/mobile, etc) | + | * compatible (Windows/Mac/Linux, PC/mobile, etc.) |
| − | * customize (CSS, dark/light, preferences, settings, themes, etc) | + | * customize (CSS, dark/light, preferences, settings, themes, etc.) |
| − | * | + | * expandable (addons, bridging, decentralizations, extensions, modular, etc.) |
| − | * | + | * organized content (categories, classifications, meta-tags, ranks, subjects, topics, votes) |
| − | * support (open-source development community) | + | * tech support (open-source development community) |
| − | == | + | == Intentions == |
| − | 4) Have | + | 4) Have clear '''intentions''' outlined in a charter, constitution, founding documents, goals, mission statement, purpose, or whatever term you wish to call it. |
: ''More soon.'' | : ''More soon.'' | ||
| − | == | + | == Structure == |
| − | 5) | + | 5) Have a clear '''structure''' outlining the expectations, behavioral priorities, goals, authority, conflict resolutions, and disciplinary consequences. |
: ''More soon.'' | : ''More soon.'' | ||
| Line 101: | Line 104: | ||
== Roadmap == | == Roadmap == | ||
| − | 6) | + | 6) Have a clear '''roadmap''' of where things may develop. Include the realistic as well as your ambitious dreams. |
: ''More soon.'' | : ''More soon.'' | ||
| Line 107: | Line 110: | ||
== Rules == | == Rules == | ||
| − | 7) | + | 7) Have a '''short''' list of hard '''rules''' that are black and white and crystal clear that '''must''' be followed. |
: ''More soon.'' | : ''More soon.'' | ||
| Line 113: | Line 116: | ||
== Guidelines == | == Guidelines == | ||
| − | 8) | + | 8) Have a '''longer''' list of grey area '''guidelines''' with as many examples as necessary for clarity. |
: ''More soon.'' | : ''More soon.'' | ||
Revision as of 14:45, 15 July 2024
|
WORK IN PROGRESS! This page is under development. Check back for developments. |
|
| Feel free to join to help edit Projex.Wiki. | ||
It is important to have a clear idea of what you aim to accomplish when starting a new social media platform. This page outlines a rudimentary checklist:
- Have a community that requires your platform.
- Have clear reasons why existing platforms do not suffice.
- Have clear requirements for new platforms.
- Have clear intentions outlined in a charter, constitution, founding documents, goals, mission statement, purpose, or whatever term you wish to call it.
- Have a clear structure outlining the expectations, behavioral priorities, goals, authority, conflict resolutions, and disciplinary consequences.
- Have a clear roadmap of where things may develop. Include the realistic as well as your ambitious dreams.
- Have a short list of hard rules that are black and white and crystal clear that must be followed.
- Have a longer list of grey area guidelines with as many examples as necessary for clarity.
Community
1) Have a community that requires your platform.
If you don't already have a community it will be nearly impossible to just grow one.
If you intend to recruit from existing communities, make sure you're offering superior services, solutions, and reasons to migrate - and consider the community distraction, division, damage, fallout, and unexpected consequences. Is it really worth the risks?
You may have to present the case for migrating. You should be clear and open about the pros and cons.
Reasons
2) Have clear reasons why existing platforms do not suffice.
Valid example reasons:
- to avoid the evil technocracy
- we should not depend on the technocracy
- we should not support the technocracy
- we should not provide our metadata to the technocracy
- we should not be exploited by the technocracy
- we need autonomy
- more control over our own data
- more control over our platform
- more control over our rules/guidelines
- more freedom
- more privacy
- more security
- self-management
- self-regulation
- we need defense from censorship, misinformation, sealioning, shills, spam, trolls, etc.
- we need FOTPACHIES community management
- Fair, Open, Transparent, Peaceful, Accountable, Consistent, Honest, Inclusive (everyone gets a say in how things are run), Ethical, Social management of communities
- we need technical solutions
- we need open-source software (transparent & verifiably safe)
- we need to decentralize
- spread out and distribute away from a single/central point of failure
- we need to develop and support alternatives
- we need to know who controls our platform
"We" = community. The community must take priority over individuals' egos.
Questionable example reasons:
- I can be a better leader
- I know better
- I must censor "wrongthink"
Requirements
3) Have clear requirements for your new platforms.
In addition to the reasons above...
Functional requirements
May include:
- chat (open and/or private)
- forum
- groups
- media
- organized content (rank, tag, vote)
- private chats and/or private messages
- sharing
- wiki
Technical requirements
May include:
- backup and/or download
- compatible (Windows/Mac/Linux, PC/mobile, etc.)
- customize (CSS, dark/light, preferences, settings, themes, etc.)
- expandable (addons, bridging, decentralizations, extensions, modular, etc.)
- organized content (categories, classifications, meta-tags, ranks, subjects, topics, votes)
- tech support (open-source development community)
Intentions
4) Have clear intentions outlined in a charter, constitution, founding documents, goals, mission statement, purpose, or whatever term you wish to call it.
- More soon.
Structure
5) Have a clear structure outlining the expectations, behavioral priorities, goals, authority, conflict resolutions, and disciplinary consequences.
- More soon.
Roadmap
6) Have a clear roadmap of where things may develop. Include the realistic as well as your ambitious dreams.
- More soon.
Rules
7) Have a short list of hard rules that are black and white and crystal clear that must be followed.
- More soon.
Guidelines
8) Have a longer list of grey area guidelines with as many examples as necessary for clarity.
- More soon.
See also
- Cassandra Team
- Community organizing concepts
- Decentralized alternatives
- FOEPATCHISM
- Security alternatives
- Technology alternatives
- Voluntarism, volunteering, organizing, and managing volunteers effectively
- Voluntaryism, voluntary interactions without rulers (rather than supporting and suffering under mafia governments and the corporatocracy with their monopoly on violence)