与「ALT！」相关的搜索结果

'商业相关'的： /startup — 把想法变成完整商业计划 /validate — 测试想法的可行性和市场潜力 /monetize — 提供赚钱方案 /offer — 帮你打造难以拒绝的方案 /pricing — 建议合理价格并解释原因 /funnel — 设计从感兴趣到下单的全流程 '高阶用户工具'： /truth — 只说确定的，不瞎猜 /sources — 提供信息源 /assumptions — 列出推理的假设前提 /alt — 给三个方案而不是一个 /steelman — 展示想法最强有力的论证 /x10 — 加强分析深度

【grok画像編集】 タネ画像作りプロンプトの一例です♥ ALTからどうぞ！ 服装や体型などはお好みでいろいろ試してみて下さい。 近々、このタネ画像作りが特に生きてくるプロンプトをリリースします。

'商业相关'的： /startup — 把想法变成完整商业计划 /validate — 测试想法的可行性和市场潜力 /monetize — 提供赚钱方案 /offer — 帮你打造难以拒绝的方案 /pricing — 建议合理价格并解释原因 /funnel — 设计从感兴趣到下单的全流程 '高阶用户工具'： /truth — 只说确定的，不瞎猜 /sources — 提供信息源 /assumptions — 列出推理的假设前提 /alt — 给三个方案而不是一个 /steelman — 展示想法最强有力的论证 /x10 — 加强分析深度

About 4 months ago, I received a ban from SeaOfThieves on an alt account due to my username (RealDrewStevens) with a ban reason of “Rare Staff Impersonation” which I take full accountability for being in the wrong here. At the time I sent in a ticket on my main account asking for clarification on the ban. After a few weeks of contacting support and attempting to reach out to anyone who could assist me, my resolution was the support team telling me there was “no enforcement action against your Xbox Live account.” They also then told me “purchasing a new license for Sea of Thieves through the Microsoft Store / Game Pass subscription / Steam or and linking your Xbox Live account to that new game license should resolve your issue.” Since then, they have gone back on this statement and last night I found out they banned my main account. In a Sea of Thieves Developer Update, @S0nicBob stated “On reflection, we feel we can create a more fair and transparent approach to enforcement, that gives players some breathing room when mistakes are made but most crucially, gives them a chance to be able to learn from those mistakes” in regards to the new points system they were implementing. So what’s the deal with this? Because right now, the actions of the support team directly contradict the public statement that was put out. I did everything "right" here. I opened a ticket instead of going straight to twitter; I kept my patience with the support team; I didn't ban evade until the support team responded and told me to do so. And now, months later, with zero new incidents and zero further communication, my main account, the one the support team confirmed had "no enforcement action" against it, is banned. Where's the "breathing room" in that? Where's the "chance to learn from mistakes" when the current mistake in question was following the support team's own advice? This new policy is just as vague and hard to interpret as the old policy. I have the ticket. I have the exact wording support used. I have a timeline that shows I acted in good faith at every single step (after the original incident of course which I again take full accountability for), only to have the rug pulled out from under me with no explanation, no warning, and no updates to tell me why the goalposts moved. Let me give a couple examples of the inconsistencies here. The gamertag “Official SOT” can receive a 3 point ban (permanent until name change). A tweet can receive a 3 point ban for “Rare Staff Impersonation” (3 days). So then why is my “Rare Staff Impersonation” ban any different? I don’t want special treatment. I want support to actually hold itself to the standards they presented to the entire community. Either Drew’s statement meant something or it didn't and right now, my account says it didn't. @RareLtd @SeaOfThieves @SoT_Support @MicrosoftHelps: I'd appreciate an actual response this time instead of a copy-paste closure. Currently that is all I am able to get out of the lowest level of the support team with no way of escalation. Please allow me my second chance that so many others received in the second chance policy. #SeaOfThieves# #FairAndTransparent#

Grok Build just got major update, giving developers more control over AI tools, better account visibility, built-in diagnostics, stronger session reliability, and lower memory usage for Voice Mode on macOS. Release Notes: v0.2.111 Features: • Users can now disable image generation and video generation tools (and their slash commands) via config.toml or environment variables. • /session-info now displays whether the session uses OAuth or an API key and where to manage the account. • You can now run grok doctor fix commands directly from inside the TUI instead of only from the CLI. Bug Fixes: • !cmd commands now allow up to one hour before timing out. • npm package now installs the native binary under $GROK_HOME/bin (honoring the same override as the Rust CLI). • Startup warnings now point to /doctor for details and fixes. • Dashboard hover and clicks no longer miss the gaps between items in wide mode. • Shift/Alt+Enter now inserts a newline while editing a queued prompt. • Queued prompt edits under combine mode no longer lose changes due to premature hold release. • Forking a session that used compaction no longer causes later rewinds to fail with missing checkpoint errors. • When a permission prompt appears while viewing scrollback, focus now correctly moves to the prompt so you can answer. • Pressing Esc once now cancels the current agent turn (except in fullscreen vim scrollback mode). • Grok now automatically stops a turn that keeps repeating the exact same tool call many times in a row. • Configs using either spelling of the workspace teleport disable flag now load and save correctly. • Background subagent completion messages no longer leak into unrelated sessions when multiple sessions are active. • When the auto-permission classifier times out or fails, Grok now shows a normal permission prompt instead of silently denying. • Managed MCP tools no longer time out prematurely on slow operations like Notion updates. Performance: • Voice dictation on macOS now uses less memory by running capture in a temporary helper process.