Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
СпутникиРНSpaceXРоскосмосNASA
What’s your App ID?
32973549
What endpoint are you using?
GET /2/users/:id/mentions, GET /2/users/me, GET /2/users/:id/tweets, and POST /2/tweets using reply.in_reply_to_tweet_id.
What API version are you on?
X API v2 with OAuth 2.0 user context.
Are you using a library or SDK? Which one?
No X SDK. A TypeScript service makes direct HTTPS requests to X API v2.
What is the issue?
This is not a bug report. I manage @MarlowStudent and am requesting prior written and explicit approval for its limited AI-powered automated reply workflow, or written confirmation that this mention-triggered design does not require separate approval.
What it does
@MarlowStudent is clearly labelled as automated. It considers an AI-generated, context-specific reply only when another user directly mentions @MarlowStudent or replies to one of its posts in a way that invites an answer.
How the software enforces the boundary
Automated replies are solicited only: timeline-observed and keyword/search-discovered posts cannot become replies or quotes.
At most one automated reply is permitted for each inbound post, and it is sent in-reply-to that source post.
Every public action, including a conversational reply, is separated by at least 12 minutes.
Reply volume is capped at 14 in a rolling day during the opening period and 8 afterward; these are ceilings, not targets.
A clear “stop”, “unsubscribe”, or equivalent opt-out is stored durably and blocks generation. The opt-out is checked again immediately before sending.
The reply path uses only the official X API. It sends no automated DMs and performs no unsolicited mentions.
An operator kill switch immediately blocks reads, generation, and dispatch.
Separate original posts or permitted engagement actions never expand who is eligible to receive an automated reply.
The X worker remains disabled while I seek this policy confirmation.
Please confirm whether this use case is approved, whether no additional written approval is required for this constrained design, and whether any further conditions apply.
Steps to reproduce the issue
N/A — policy approval request.
What is the error message?
N/A.
When did it start?
The implementation is complete but remains disabled pending policy confirmation.
What have you tried to troubleshoot?
I reviewed the current X Automation Rules, Developer Guidelines, and recent forum answers concerning mention-triggered AI reply bots.
1 post - 1 participant
Read full topic
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Do human-reviewed AI reply suggestions need additional approval? | 0 | 9.98 | 27-08-2026 |
| 2 | Approval route requested: owner-reviewed AI-assisted X reply preparation | 0 | 10.42 | 27-08-2026 |
| 3 | API authorization issue OAuth2 | 0 | 8.78 | 28-08-2026 |
| 4 | Credits added to wrong developer account — which app/account should I use? | 0 | 6.39 | 27-08-2026 |
| 5 | X APIを利用した有料LINE・Discord案件検索通知サービスの利用可否について | 0 | 16.06 | 28-08-2026 |
| 6 | Developer Policy clarification for public-Post research | 0 | 6.14 | 27-08-2026 |
| 7 | OAuth 2.0 regression / authorization rejects numeric-only state values | 0 | 9.79 | 27-08-2026 |
| 8 | Account automation not working anymore | 0 | 7.98 | 27-08-2026 |
| 9 | Problems between X and Grok Bot | 0 | 6.62 | 28-08-2026 |
| 10 | X Can't post link | 0 | 9.12 | 30-08-2026 |