> For the complete documentation index, see [llms.txt](https://docs.socio.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.socio.family/getting-started/navigating-the-feeds-public-vs.-private.md).

# Navigating the Feeds (Public vs. Private)

Socio runs on a **2 feed system**: a wide-open **Public Feed** and a members-only **Private Feed**. Here's everything you need to know about each.

## The Public Feed

The Public Feed is exactly what it sounds like — content that's visible to **everyone**.

| Feature                     | Public Feed                                              |
| --------------------------- | -------------------------------------------------------- |
| **Who can see it?**         | Everyone, logged in or not                               |
| **Login required to read?** | No                                                       |
| **Who can post?**           | Logged-in users                                          |
| **Typical content**         | Announcements, general takes, teasers, community chatter |

{% hint style="warning" %}
**Guest experience:** If you're browsing without logging in, you can read the public feed freely — but after about **15 seconds**, you'll see a friendly prompt inviting you to log in with X. It's a gentle nudge, not a paywall.
{% endhint %}

##  The Private Feed

The Private Feed is where the real value lives — **exclusive content from a specific creator's group**, only for people who hold that creator's **Creator Shares**.

| Feature                     | Private Feed                                   |
| --------------------------- | ---------------------------------------------- |
| **Who can see it?**         | Only holders of the group's Creator Shares     |
| **Login required to read?** | Yes                                            |
| **Entry requirement**       | Hold ≥ the group's threshold of Creator Shares |
| **Typical content**         | Alpha, early calls, Q\&A, insider discussion   |

## How to unlock a private feed

1. Browse the public feed or the Groups page.
2. Find a creator you like and open their group.
3. **Preview the price** of their Creator Shares.
4. **Buy shares** with ETH — the platform handles the swap automatically.
5. You're in. The private posts unlock instantly.

{% hint style="success" %}
**Already holding shares?** Your access follows your wallet automatically. Simply log in and open the group — you'll see everything you're entitled to.
{% endhint %}

## Quick comparison

|                      | Public Feed     | Private Feed       |
| -------------------- | --------------- | ------------------ |
| Reading access       | Everyone        | Holders only       |
| Login needed to read | No              | Yes                |
| Posting              | Logged-in users | Holders only       |
| Entry cost           | Free            | Buy Creator Shares |

**Next step:** if you're a creator, head to **For Creators (KOLs)** to launch your own group.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.socio.family/getting-started/navigating-the-feeds-public-vs.-private.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.