Repository navigation
这个重置,是需要订阅X的API吗 #69
Replies: 4 comments
|
If you mean AIHOT's Codex reset monitor, you do not need an X/Twitter API subscription. It reads X through SocialData, so you need a I checked the current scheduler and provider code and ran this small guard check: Set |
|
感谢您的回复, 指的是 AIHOT 的*Codex 重置监控器*, *SocialData 是怎么申请的 * SOCIALDATA_API_KEY是一个付费
API;价格是多少钱呢
Chi-Wei Lee ***@***.***> 于2026年10月2日周五 11:57写道:
… If you mean AIHOT's *Codex reset monitor*, you do not need an X/Twitter
API subscription. It reads X through *SocialData*, so you need a
SOCIALDATA_API_KEY from that separate service. SocialData is a paid API.
The monitor cannot collect new reset posts without that key.
I checked the current scheduler and provider code and ran this small guard
check:
SOCIALDATA_API_KEY=<unset>: monitor scheduled=false
SOCIALDATA_API_KEY=example-key: monitor scheduled=true
provider requires SOCIALDATA_API_KEY: yes
Set SOCIALDATA_API_KEY in your deployment's .env and restart the worker.
The repository's monitor documentation
<https://github.com/KKKKhazix/AIHOT/blob/main/docs/leaderboard.md#codex-%E9%87%8D%E7%BD%AE%E7%9B%91%E6%8E%A7codex-reset>
says that, without it, the page shows no reset records. If you do not want
to use SocialData, turn off codexResetMonitor in industry/features.ts;
that also removes the monitor routes and scheduled collection.
—
Reply to this email directly, view it on GitHub
<#69?email_source=notifications&email_token=B2PPZ4XHR2AET33KI5HX66L5R4RTFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGA4DSNJVUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18708955>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B2PPZ4R4VX5QKUZNAVWO75L5R4RTFAVCNFSNUABJKJSXA33TNF2G64TZHMYTGOJTHE3DKOBSHE5UI2LTMN2XG43JN5XDWMJQHEZTENRYGSQXMAQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/B2PPZ4WNNBVAPET4DXRDXMD5R4RTFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGA4DSNJVUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/B2PPZ4XEM4YIVO7EHMU2SA35R4RTFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGA4DSNJVUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
补充一下:4.0.0 起 Codex 重置监控已经移出开源框架,只留在 AIHOT 线上(见部署文档的“升级到公开接口 4.0.0”)。现在的开源版没有这个功能;X 账号信源仍然需要 SocialData 的 key。 |
|
好的 明白了 谢谢
Khazix ***@***.***> 于 2026年10月4日周日 15:43写道:
… 补充一下:4.0.0 起 Codex 重置监控已经移出开源框架,只留在 AIHOT 线上(见部署文档的“升级到公开接口
4.0.0”)。现在的开源版没有这个功能;X 账号信源仍然需要 SocialData 的 key。
—
Reply to this email directly, view it on GitHub
<#69?email_source=notifications&email_token=B2PPZ4THW54266SIZILTA535SH5S5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGQYDONBUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18740744>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B2PPZ4TCKPVOSU6XK2TLNRT5SH5S5AVCNFSNUABJKJSXA33TNF2G64TZHMYTGOJTHE3DKOBSHE5UI2LTMN2XG43JN5XDWMJQHEZTENRYGSQXMAQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/B2PPZ4UAXRJDWLN4YXLHGCD5SH5S5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGQYDONBUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/B2PPZ4XSJLDA735O7JNQACL5SH5S5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGQYDONBUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
If you mean AIHOT's Codex reset monitor, you do not need an X/Twitter API subscription. It reads X through SocialData, so you need a
SOCIALDATA_API_KEYfrom that separate service. SocialData is a paid API. The monitor cannot collect new reset posts without that key.I checked the current scheduler and provider code and ran this small guard check:
Set
SOCIALDATA_API_KEYin your deployment's.envand restart the worker. The repository's monitor documentation says that, without it, the page shows no reset records. If you do not want to use Soci…