田景

119 posts

田景

田景

@daocao2009

Katılım Mart 2024
50 Takip Edilen2 Takipçiler
田景
田景@daocao2009·
@MaxForAI 都出来了,还用着腾讯这玩意🤣我很好奇你用AI来干嘛
中文
0
0
0
211
Max For AI
Max For AI@MaxForAI·
神了,群友的腾讯电脑管家拦截了Codex,然后Codex自动黑进了腾讯电脑管家的文件,找到了杀毒软件规则绕了过去😺 这就是AGI吧🤯
Max For AI tweet media
中文
170
39
628
100.7K
vogel
vogel@ryanvogel·
gpt 5.6 sol story of the day: i have a macbook connected and powered by a caldigit TS5 it kept reconnecting randomly and it was pissing me off, i told sol to investigate and it found out that it would disconnect when power heavy GPU loads and the caldigit couldn't supply enough power sol created the hypothesis and proved it to me then it told me to plugin the 120W power cable, then it did the reproductions again and they were fixed this would have taken me an entire day
English
10
7
486
165.3K
Joshua Stanton
Joshua Stanton@ShiftingPathway·
@mattshumer_ @gdb Very unfair making such a big deal about something that was completely avoidable and your own fault
English
1
0
11
1.9K
田景
田景@daocao2009·
@MaxForAI 你送人头也没关系,模型是中立的😅
中文
0
0
1
2.5K
Max For AI
Max For AI@MaxForAI·
Claude:还有主动送头的??
Max For AI tweet mediaMax For AI tweet media
中文
123
20
540
229.4K
田景
田景@daocao2009·
@LuminaXspace 希望在7月17出😀从开发者大会5月份等到现在,希望谷歌兑现诺言😎
中文
0
0
0
61
Lumina
Lumina@LuminaXspace·
🚨 New Gemini 3.5 Pro leak just surfaced Google appears to be preparing its next flagship Gemini model: • Internal codename reportedly: Cappuccino • Expected to introduce a new Deep Thinking mode • Rumoured 2M-token context window • Stronger tool use, planning and multi-step execution • Release reportedly targeted for later this month still after delays • Major gains in reasoning, coding and long-horizon agent tasks • Alleged benchmark improvements across web development, SVG generation and complex problem-solving Some leaked builds may already be appearing through LMArena and Google’s Antigravity platform, but the model identity and benchmark claims remain unconfirmed. Are you looking forward to Gemini 3.5 Pro being released?
Lumina tweet media
English
41
69
601
63.3K
田景
田景@daocao2009·
@komal_uk01 强烈建议🤣直接买20X的绝对不后悔,买其他的会后悔
中文
0
0
0
31
komal
komal@komal_uk01·
developers, is it worth purchasing codex pro?
komal tweet media
English
83
3
186
15.8K
田景
田景@daocao2009·
@liferacerza 这是小学生的水平🤣口算一秒都能算出来是3
中文
0
0
0
4
erz🫧
erz🫧@liferacerza·
bunu çözersen IQ seviyen ortalamanın üstündedir. x kaç olabilir ?
erz🫧 tweet media
Türkçe
11.7K
196
6.8K
3M
Rhys
Rhys@RhysSullivan·
i can't believe the ideal form factor for background / proactive agents is codex pets
Rhys tweet media
Rhys@RhysSullivan

alright i'm wanting to try background / proactive agents, looking to learn what peoples setups are like rough things on my mind of random agents i want: - i want an agent that watches a github repo like an sdk and tells me how it changes - i want an agent that whenever i get a slack message it decides whether to page me, start investigating, etc - i want an agent that every 4 hours figures out things i need to reply to / follow up on - i want an agent that watches every github commit for how those changes are doing in production - i want an agent that works as my growth agent running experiments, monitoring posthog, tweaking my landing page marketing copy etc - i want an agent that monitors all my production traffic for any anomalies these don't need to be super aggressive on responding to triggers, some form of cron is fine i've tried codex automations but something didn't really click with their implementation for me also somewhat tried hermes but same thing of just something didn't really click with the implementation eve and flue maybe fit into this category but just seem so high friction to set up for these use cases, my dream UX is just sending a prompt to an agent and getting back a proactive agent setup i do see this being one of the biggest unlocks for making life easier when working with ai but haven't found a setup i like yet

English
14
5
189
31K
骑上我心爱的小摩托
@wangzhian8848 这女的不是你们央视的吗?北京大学光华管理学院MBA学位! 如果不是企业家去读这个MBA,那就是去钓凯子的.
中文
1
0
2
1.1K
王局志安
王局志安@wangzhian8848·
2017年邹市明赢得金腰带后的首场自由卫冕战输给木村翔后,我在他家采访了他。采访中有段插曲,他太太直接冲进来叫停采访,后来我们现场沟通了十几分钟采访才继续。后来我们在播出版中,没有将这个片段剪进节目里。 不知道什么时候邹移民到美国了,其他对他来讲,更适合在中国。在美国他就是路人甲,但在中国至少还是前拳王。 男人可以有钱也可以没钱,生活总有起起落落。但两口子如果不能同甘共苦,早晚是要出事儿的。
王局志安 tweet media王局志安 tweet media王局志安 tweet media王局志安 tweet media
中文
342
45
999
690.9K
Google AI Studio
Google AI Studio@GoogleAIStudio·
What are you vibe coding this weekend?
English
600
51
1.4K
228.3K
田景
田景@daocao2009·
@sama 🤣chat gpt确实可以优秀到让人嫉妒
中文
0
0
0
5
Sam Altman
Sam Altman@sama·
there are a lot of benchmarks that suggest 5.6 sol is the best model in the world right now, but the most reliable way to tell is that elon is obsessed with me again
English
4K
2.9K
62.9K
5.8M
田景
田景@daocao2009·
@doganuraldesign 如果移除chatgpt意味着他们即将收到反垄断调查,奥特曼的chatgpt至少在额度和能力综合上都是第一名无人能及,这是真正的open ai😅
中文
0
0
0
6
田景
田景@daocao2009·
@vamsibatchuk @FlowbyGoogle Flow“发现异常”“把AI数字人认识成名人”的BUG如果解决,谷歌不会损失这么多客户,希望google one团队重视这个问题,这关乎你们的高级订阅用户的去留,如果不行就把FLOW团队换了吧😅我觉得我都比他们强
中文
0
0
0
7
田景
田景@daocao2009·
@MarcosHernanz 你完全可以不用打开,但是宠物的功能也不错,可以监控任务状态
中文
0
0
0
104
Marcos Hernanz
Marcos Hernanz@MarcosHernanz·
OpenAI can you make your models good at frontend and stop this pet bs?
Marcos Hernanz tweet media
English
25
0
114
9.1K
田景
田景@daocao2009·
@st7evechou 你居然能把老豆弄到限额,佩服你的毅力😹
中文
0
0
1
1.2K
田景
田景@daocao2009·
@lucky5458715571 @DH976291 @Alex8282019 你这种人毫无逻辑,就会XXXX本来是XXXX,我给你支个招,先学好基础,再谈科学😹要不表达都不会表达就会骂人,当然这是绝大部分国人的通病,所以好多时候他们觉得被冒犯的原因其实和自己毫无关系,如果有关系就是因为长期浸淫于宏大叙事中无法自拔,只能靠群体续梦,得罪了😅
中文
0
0
0
40
lucky
lucky@lucky5458715571·
@DH976291 @Alex8282019 看给你急的,已经语无伦次了🤣。照你这么说,科学本来就是互相抄袭,再牛逼底层原理是一样,谁都能用。
中文
1
0
20
1.8K
二爷Alex
二爷Alex@Alex8282019·
有没有懂行的同学说说中国为啥采用这种火箭回收方式?相比SpaceX的筷子,优劣如何?
中文
584
13
334
635.3K
田景
田景@daocao2009·
@thsottiaux 原来你们真的是open ai,真的很大方,我都不知道充值多少次了😀实在太棒了
中文
0
0
0
13
Tibo
Tibo@thsottiaux·
Hello beautiful people! We have reset usage limits across Codex and ChatGPT Work. And another one will come later in the day. Rejoice. Now that I have your attention, a quick update on ChatGPT Work, Codex and all the updates we shared yesterday. We’ve spent the last 24 hours reading feedback, looking at usage patterns, and talking with many of you. The short version is that there is a *lot* of excitement for GPT 5.6 Sol, ChatGPT Work on mobile & web, but also that we didn't get everything quite right. - We made it too easy to use the highest-compute settings without making the impact on usage limits sufficiently clear. - We reorganized the desktop app in one bold move, making familiar things like chats and projects harder to find. - Our launch framing was focused on ChatGPT Work and to some of our Codex fans it made it feel like Codex was going away over time. Absolutely not our intention, we love Codex and it is here to stay. - And we introduced regressions for some existing multi-agent workflows, alongside a collection of rough edges in plugins and other parts of the experience. We’re landing a first set of improvements today. We’re resetting usage twice so people can keep experimenting, changing defaults and the model picker so they don’t push people toward unnecessarily expensive settings, fixing several plugin submission issues, improving how we represent Codex in the product, and cleaning up some of the most immediate desktop problems. A larger set of improvements will land next week. We’re bringing chats and projects back into the sidebar in a more familiar and customizable way, making usage and reset timing much more visible, clarifying when to use ChatGPT Work and when to use Codex, and addressing the many other smaller pieces of great feedback we've had. The ambition behind this launch hasn’t changed. We think bringing ChatGPT and Codex together into a workspace where people and agents can collaborate is a very important step forward. But an ambitious direction doesn’t excuse avoidable confusion or regressions in the first version. Please keep the feedback coming. We’re moving quickly, and you should see the experience already get better with a few updates today; and substantially better again next week.
English
2K
831
13.9K
2.2M