Offline demo mode is implemented. The live read-only connector is built for private validation and remains disabled until Reddit approval is complete.
One source in validation · More deliberately planned
The source list will grow. The standard should not slip.
ThreadCue is being designed as a broader conversation opportunity platform. Every source will need an approved connection method, narrow permissions, accurate status language, and a workflow that respects the community it connects to.
Current and planned sources
“Planned” is a direction, not a promise of functionality or timing.
Threads
PlannedA future conversation source; no connection is available in the current product.
A future source subject to platform review and approved permission scopes.
X
PlannedA future source; access and product design will follow the platform's current developer terms.
Bluesky
PlannedA future public-conversation source; not implemented in the prototype.
Forums
PlannedFuture support for approved forum and community sources, represented transparently per provider.
Community platforms
PlannedA broader category for professional communities and networks as supported integrations are added.
First integration
Reddit is implemented for private validation, not publicly enabled.
The prototype includes an offline demo and a separate hosted OAuth/Data API gateway. Live access remains disabled until Reddit approves ThreadCue’s exact use case and any required commercial terms are complete.
- identity
- Confirm the connected Reddit username and immutable account identity.
- mysubreddits
- Read communities the connected account follows so the user can choose relevant sources.
- read
- Retrieve matching public posts, comments, and community listings.
Not requested: submit, vote, save, subscribe, messages, history, or moderation scopes.
How a new source earns its place
Future connectors should be represented by the same product and trust contract.
- 01
Approved access
Use the platform’s supported API and authorization path. No scraping or customer-supplied client IDs to bypass review.
- 02
Minimum permissions
Request only what a visible feature needs, and explain each permission in plain language before connection.
- 03
Source-specific retention
Document what is captured, where it is stored, how long it remains, and what derived work survives deletion.
- 04
Human final action
Keep drafting and participation separate. New sources do not imply automatic posting.
Care about a particular source?
Join the waitlist and tell us where thoughtful participation is hardest today.