# X (Twitter) Comparison

## Summary of advantages of Derupt over X:

* **Monetization** allowing users to directly monetize content without permission.
* Users have more **flexibility** and control over where their data is stored.
* **Transparency** in how the platform operates and how content is handled.
* Better mechanisms for **spam prevention** due to financial barriers for interaction.
* **Greater user control** over content, data, and monetization.
* **High censorship resistance** through immutable, on-chain content.
* **Decentralization** ensures no single entity controls the platform.

<table><thead><tr><th width="221" align="center">ASPECT</th><th width="281" align="center">X (Twitter)</th><th align="center">DERUPT</th></tr></thead><tbody><tr><td align="center">Content Monetization</td><td align="center">Permission Required</td><td align="center">Permission Not Required</td></tr><tr><td align="center">Monetization Method</td><td align="center">Achieved via ad-rev split based on attention</td><td align="center">Achieved via smart contracts, based on consumer sentiment</td></tr><tr><td align="center">Content Discovery </td><td align="center">Centralized opaque algorithm, encouraging favoritism and censorship by omission of presentation. (biased)</td><td align="center">Decentralized transparent chronological algorithm, encouraging equal opportunity of presentation. (unbiased)</td></tr><tr><td align="center">User Control</td><td align="center">Centralized, handled by the platform, very limited.</td><td align="center">Users control attachment storage, including their fallback loadout-URI</td></tr><tr><td align="center">Spam/Bot Prevention</td><td align="center">AI-driven moderation, no financial barriers.</td><td align="center">On-chain fees disincentivize spammers. Economic barrier in place.</td></tr><tr><td align="center">Interface Design</td><td align="center">Interface lock in, developers can not create full clients. eg No alternative interface available.</td><td align="center">Interface agnostic, developers can create full clients. eg Alternative interfaces availability.</td></tr><tr><td align="center">Content Storage</td><td align="center">Centralized storage, no fall back control</td><td align="center">Primary content stored on-chain; attachments in user-controlled Stacks storage, with fallback flexibility. </td></tr><tr><td align="center">Immutability</td><td align="center">Content can be removed or modified by the platform.</td><td align="center">On-chain messages are immutable and URI pointers are permanent. (fallback loadout-uri's ensure resilience in resolution)</td></tr><tr><td align="center">Censorship Resistance</td><td align="center">Subject to platform favoritism  and legal censorship.</td><td align="center">On-chain data cannot be removed. Interfaces may mute, but cannot delete content.</td></tr><tr><td align="center">Proof of Censorship</td><td align="center">No proofs capable, censorship done in secret. No user recourse. </td><td align="center">On-chain attestation proves existence of any muted content. </td></tr></tbody></table>

*


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.derupt.io/legacy/comparison-x.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
