List account posts

Use this recipe when you need social or indexed post lists for an account or feed-like surface.

Nexus is the right starting point for social discovery. Layer 1 remains the source for canonical operation and authority data.

Safety

Safety level: read-only.

This recipe queries Nexus/Bridge data. It does not require a private key and does not broadcast.

Choose the query shape

For new code, prefer option-object Nexus calls when a helper supports them. Option objects make cursors, filters, sort modes and observer behavior explicit.

Conceptually:

const posts = await client.nexus.getAccountPosts({
  account: 'beblurt',
  sort: 'posts',
  limit: 10,
  observer: null
});

For ranked discovery rather than one account's posts:

const posts = await client.nexus.getRankedPosts({
  sort: 'trending',
  limit: 10,
  tag: 'blurt',
  observer: null
});

Why Nexus?

A social UI usually wants already-indexed views such as:

• account post lists;
• ranked feeds;
• community pages;
• discussion trees;
• profile summaries.

Those are application-friendly views. If the next step is security-sensitive, verify the relevant Layer 1 state before signing or broadcasting.

Validated source

Related executable source: examples/node/read-nexus-ranked-posts.cjs.

Run locally from the repository:

node examples/node/read-nexus-ranked-posts.cjs

This example is included in npm run docs:check.

Pagination rule

When a Nexus method exposes cursor parameters, treat the cursor as part of the query state. Keep sort, filters, observer and cursor together so pagination does not accidentally switch views.

Compatibility note

Historical positional Nexus signatures remain supported. New documentation should prefer corrected names and option-object forms when available. The misspelled listPopComunities helper is retained for compatibility but new docs should use listPopCommunities.

Related: Layer 1 and Nexus Layer 2, Use Nexus social data, Deprecations.