Cross-Posting Guide

Write once, publish everywhere. DegenFeed’s composer sends your content to every network you select using each protocol’s native API — Nostr events, Farcaster casts, Bluesky records, Mastodon toots, and more — from a single interface.

💡

TipCross-posting is available on the free tier. All signed-in users can publish to every connected protocol at once. No extra fees per post.

How Cross-Posting Works#

When you hit Post in the DegenFeed composer, the platform:

1
Adapts your content
Each protocol receives content in its native format — plain text for Nostr, casts for Farcaster, XRPC records for Bluesky, REST toots for Mastodon.
2
Signs client-side
Your keys never leave the browser. Nostr events are signed with your nsec, Farcaster with your signer, and the rest via OAuth/app tokens you connected.
3
Fan-outs in parallel
Posts are sent to all selected networks simultaneously. Partial failures are retried in the background — you are never left with a half-published thread.
4
Aggregates engagement
Every post gets a canonical DegenFeed ID, so likes, replies, and reposts from all protocols flow back into one unified view.

How to Cross-Post#

Connect accounts

Go to Settings → Connected Accounts and link every protocol identity you want to publish to. Nostr (nsec), Farcaster (signer), Bluesky (app password), Mastodon (OAuth), Threads, and more.

Open the composer

Click the Compose button in the header. Write your text, add media, links, mentions, or hashtags.

Select protocols

Tick the checkboxes for each destination network. DegenFeed shows each protocol’s character limit and will warn you before truncation.

Hit Post

Your content is sent to every selected protocol at once. Engagement flows back into a single canonical post view.

Protocol Limits & Differences#

Protocol	Character Limit	Media	Notes
Nostr	~64 KB (relay dependent)	Images, video links	Some relays cap notes at ~500 chars; signed with nsec client-side.
Farcaster	320 chars	Images, embeds	Posts are called casts; embeds supported via URLs.
Bluesky	300 chars	Images, video	Uses AT Protocol XRPC; app password required.
Mastodon	500 chars (instance dependent)	Images, video	Works with any ActivityPub instance, including social.degenfeed.xyz.
Threads	500 chars	Images, video	Threads API posting requires a linked Instagram account.
Lens	5,000 chars (publication)	Images, video, audio	Publications are signed on Polygon; supported via Lens API.
Threads	500 chars	Images, video	Threads API posting requires a linked Instagram account.
Reddit	40,000 chars (post body)	Images, links	Cross-posting to Reddit requires a Reddit API credential.
RSS / Atom	Source-dependent	Text, media enclosures	Publishing via RSS requires a compatible publishing endpoint.

ℹ

InfoProtocol availability for cross-posting depends on your plan. Free accounts can post to up to 3 protocols; Pro unlocks 10+; Creator+ posts to every supported network. See the Protocol Guide for full details on each network.

Scheduling Cross-Posts#

Creator tier users can schedule posts to publish at a future time. Click the clock icon in the composer, choose your time and timezone, and select target protocols. Scheduled posts appear in Creator Studio where you can edit, reschedule, or cancel them before they go live.

Best Practices#

✓ Keep posts under 300 characters so they fit every protocol (Bluesky is the tightest common denominator).
✓ Use hashtags sparingly — Nostr and Mastodon index them differently than Farcaster.
✓ Attach media that every network supports (JPEG/PNG images, standard MP4/WebM video).
✓ Reply to engagement across protocols from the canonical post view — DegenFeed routes the reply to the correct network.

Cross-Posting via API#

Developers can publish programmatically through the DegenFeed API:

bash

# Publish to Nostr + Farcaster + Bluesky at once
curl -X POST https://degenfeed.xyz/api/publish \
  -H "Authorization: Bearer $DEGENFEED_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Hello from the DegenFeed API 👋",
    "protocols": ["nostr", "farcaster", "bluesky"]
  }'

ℹ

InfoThe publish endpoint returns per-protocol status so you can retry only the networks that failed. See the API Reference for full payload documentation.

Troubleshooting#

Post failed on one protocol?#

Check the per-protocol status in the composer after posting. Common causes: expired OAuth/app password, character limit exceeded, or a relay/instance that rejected the event. Reconnect the account in Settings → Connected Accounts and retry.

Next: read the Video Streaming Guide or the User Guide.