Starting new social media platforms

From Projex.Wiki
Revision as of 00:10, 10 April 2023 by Admin (talk | contribs) (Created page with "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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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

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 open about the pros and cons.

Have reasons

Have clear reasons why existing platforms do not suffice.

Valid example reasons:

  • evil corporatocracy/technocracy
    • we should not depend on the corporatocracy/technocracy
    • we should not support the corporatocracy/technocracy
    • we should not provide our metadata to the corporatocracy/technocracy
    • we should not be exploited by the corporatocracy/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 FOTPACHIES management
    • Fair, Open, Transparent, Peaceful, Accountable, Consistent, Honest, Inclusive (everyone gets a say in how things are run), Ethical, Social management
  • 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.

Questionable example reasons:

  • I can be a better leader
  • I know better
  • I must censor "wrongthink"

The community must take priority over egos.

Have technical requirements

Have clear technical requirements.

In addition to the reasons above...

Example interactive functional requirements:

  • chat (open and/or private)
  • forum
  • groups
  • media
  • organize content (rank, tag, vote)
  • private chats and/or private messages
  • sharing
  • wiki

Example technical requirements:

  • backup and/or download
  • compatible (Windows/Mac/Linux, PC/mobile, etc)
  • customize (CSS, dark/light, preferences, settings, themes, etc)
  • expand (addons, bridging, extensions, modular, etc)
  • organize content (categories, classifications, meta-tags, subjects, topics)
  • support (open-source development community)

Have structure

Have a clear structure outlining the goals, authority, what's expected, conflict resolutions, and disciplinary consequences.

More soon.

Draft intentions

Draft a charter, constitution, goals, mission statement, or purpose (or whatever you want to call it) to be clear about your intentions.

More soon.

Draft roadmap

Draft a rough roadmap of where things can develop. Include the realistic as well as your ambitious dreams.

More soon.

Draft rules

Draft a short list of black and white hard rules that must be followed.

More soon.

Draft guidelines

Draft a longer list of grey area guidelines with many examples.

More soon.