Difference between revisions of "Starting new social media platforms"
(18 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
+ | {{Work in progress}} | ||
+ | |||
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: | 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|community]]''' that requires your platform. | # Have a '''[[#Community|community]]''' that requires your platform. | ||
# Have clear '''[[#Reasons|reasons]]''' why existing platforms do not suffice. | # Have clear '''[[#Reasons|reasons]]''' why existing platforms do not suffice. | ||
− | # Have clear '''[[#Requirements|requirements]]'''. | + | # 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(s) 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 == | ||
− | 1) Have a | + | '''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 don't already have a community it will be nearly impossible to just grow one. | ||
Line 22: | Line 25: | ||
== Reasons == | == Reasons == | ||
− | 2) Have clear | + | '''2) Have clear [[reasons]] why existing platforms do not suffice.''' |
Valid example reasons: | Valid example reasons: | ||
− | * to | + | * We need '''[[alternatives]]''' to 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 '''[[security]]''' from censorship and harms |
− | * | + | ** Including defamation, hacks, lies, maliciousness, misinformation, [https://saidit.net/s/Terminology/comments/8f81/sealioning_a_harassment_tactic_under_the_guise_of sealioning], shills, slander, spam, trolls, etc. |
− | ** '''F'''air, '''O'''pen, ''' | + | * We need '''[[FOEPATCHISM]]''' |
− | * | + | ** '''F'''air, '''O'''pen, '''E'''thical, '''P'''eaceful, '''A'''ccountable, '''T'''ransparent, '''C'''onsistent, '''H'''onest, '''I'''nclusive (everyone gets a say in how things are run), '''S'''ocial '''M'''anagement' - for collaborators, communities, families, governments, groups, homes, organizations, social media, societies, teams, workplaces, etc. "Foe" = enemy; "patch" = correction. |
− | ** | + | * We need '''[[technical solutions]]''' and '''[[technology alternatives]]''' |
− | ** | + | ** We need '''[[alternatives]]''' and '''[[solutions]]''' developed and supported |
− | *** | + | ** We need '''[[decentralized alternatives]]''' |
− | ** | + | *** Spread out and distribute away from a single/central point of failure or corruption |
− | ** | + | ** We need '''[[open-source]]''' software (transparent & verifiably safe) |
− | + | ** We need '''[[knowledge]]''' of who '''[[controls]]''' our platforms | |
− | ''' | ||
− | The community must take priority over individuals' egos. | + | '''"We" = community.''' The community must take priority over individuals' egos. |
Questionable example reasons: | Questionable example reasons: | ||
− | * I can be a better leader | + | * "''I can be a better leader.''" |
− | * I know better | + | * "''I know better.''" |
− | * I must censor | + | * "''I must censor 'wrongthink'.''" |
== Requirements == | == Requirements == | ||
− | 3) Have clear | + | '''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 72: | Line 76: | ||
* 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 a | + | '''4) Have clear [[intentions]] outlined in a charter, constitution, founding documents, goals, mission statement, purpose, or whatever term(s) 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 100: | Line 106: | ||
== 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 106: | Line 112: | ||
== 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 112: | Line 118: | ||
== Guidelines == | == Guidelines == | ||
− | 8) | + | '''8) Have a [[longer]] list of grey area [[guidelines]] with as many examples as necessary for clarity.''' |
: ''More soon.'' | : ''More soon.'' | ||
+ | |||
+ | == See also == | ||
+ | |||
+ | * [[Cassandra Team]] | ||
+ | ** [[Projex.Wiki]] | ||
+ | ** [[LeverMind]] | ||
+ | * [[Community organizing concepts]] | ||
+ | * [[Decentralized alternatives]] | ||
+ | * [[FOEPATCHISM]] | ||
+ | * [[Security alternatives]] | ||
+ | * [[Technology alternatives]] | ||
+ | * [[Voluntarism]], volunteering, organizing, and managing volunteers effectively | ||
+ | * [[Voluntaryism]], voluntary interactions without rulers (rather than suffering under and supporting the global mafia corporatocracy with their monopoly on violence, coercion, theft, and mass murder.) | ||
+ | [[Category:Community organizing concepts]] | ||
+ | [[Category:Decentralizing]] | ||
+ | [[Category:Ethical community management]] | ||
+ | [[Category:Ethical social management]] | ||
+ | [[Category:FOTPACHIES community management]] | ||
[[Category:Lists of lists]] | [[Category:Lists of lists]] | ||
+ | [[Category:Prepping]] | ||
+ | [[Category:SaidIt communities]] | ||
+ | [[Category:Social media]] | ||
[[Category:Starting new social media platforms]] | [[Category:Starting new social media platforms]] | ||
− | |||
[[Category:Technology]] | [[Category:Technology]] | ||
+ | [[Category:Technology prepping]] | ||
+ | [[Category:Technology projects]] | ||
[[Category:Websites]] | [[Category:Websites]] |
Latest revision as of 02:01, 19 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(s) 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:
- We need alternatives to 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 security from censorship and harms
- Including defamation, hacks, lies, maliciousness, misinformation, sealioning, shills, slander, spam, trolls, etc.
- We need FOEPATCHISM
- Fair, Open, Ethical, Peaceful, Accountable, Transparent, Consistent, Honest, Inclusive (everyone gets a say in how things are run), Social Management' - for collaborators, communities, families, governments, groups, homes, organizations, social media, societies, teams, workplaces, etc. "Foe" = enemy; "patch" = correction.
- We need technical solutions and technology alternatives
- We need alternatives and solutions developed and supported
- We need decentralized alternatives
- Spread out and distribute away from a single/central point of failure or corruption
- We need open-source software (transparent & verifiably safe)
- We need knowledge of who controls our platforms
"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(s) 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 suffering under and supporting the global mafia corporatocracy with their monopoly on violence, coercion, theft, and mass murder.)