Comment on WHY soj.ooO? by dangun

dangun · 2/16/2025, 6:53:34 PM · permalink

We believe in the goals of all of the above. Federation brings a level of control to the people as does decentralization since the protocol is not centrally controlled and thus, participants get to decide how things work by either running or not running introduced changes. However, this also brings with it, a difficult scenario where disagreements cause splits, forks, and generally reduced progress over time.

That said, centralized services tend to win because of the latter - they progress rapidly (among other things, including easier to use and so forth).

We wanted to bring the goals that decentralization/federation aim to bring while harnessing the benefits of centralization -- and so we decided to build a decentrally-owned, centrally operated platform.

Participants will be able to vote for the representatives/team that will be running the platform -- a truly representative democracy.

We're really excited to have you all on this experiment, which we hope will become a great journey towards the creation of a people-owned, free-speech platform.

Hope this answers your question!

6 bumps

matt · 2/16/2025, 7:02:43 PM · permalink

4 bumps

trajan · 2/16/2025, 10:50:56 PM · permalink

1 bump

trajan · 2/16/2025, 9:16:12 PM · permalink

I appreciate the initiative and thought behind soj.ooo—this platform fills a critical need for free discourse in our algorithmic age. My core arguments for embracing TRAD (Transparent, Repeatable, Augmentable, Decentralized) principles:

Opt-in extensibility would allow users to choose complexity without burdening casual users
    Long-term sustainability outweighs short-term development costs
    Competitive differentiation against platforms like Mastodon/Bluesky
    Mitigating corruption through transparency

On the closed/open dichotomy

While centralized platforms can iterate faster initially (à la Notion), open standards like Obsidian’s Markdown ecosystem show that flexibility breeds longevity. Obsidian thrives because:

Plaintext files allow unlimited plugin interoperability
    Users control their data flow without vendor lock-in
    Community-driven enhancements compound value

An opt-in plugin system for soj.ooo could empower third-party features like:

Structured debate interfaces (Kialo-style branching threads)
    Fediverse/Mastodon bridging
    Community-verified voting systems
    Anti-bot reputation layers

Representation vs Participation

Representative models can work, but history shows they’re vulnerable to state/business capture (e.g., lobbying, regulatory overreach). Decentralized protocols like ActivityPub (used by Mastodon) demonstrate how technical safeguards—not just procedural ones—can enforce platform resilience.

Even partial transparency (e.g., public moderation logs, open API standards) would build trust without sacrificing development velocity.

The path forward isn’t binary. Hybrid models exist:

Code transparency with closed governance (Signal-style)
    Modular federation allowing standalone communities
    Community plugins (opt-in via permissions)

TRAD principles don’t stifle innovation—they future-proof it.

1 bump

Signature