标题: 最近用AI的感想
作者: #bkw
板块: #搞七捻三
编号: 809081
帖子: https://linux.do/t/topic/809081
时间: 2025-07-23 09:10:35
摘要:

以前遇到问题，先思考用什么搜索词，一个个检查搜索结果，阅读。如果有没理解的地方，要么联系上下文反复去读去想，要么亲手尝试，有时也会调整关键词进一步搜索。
现在，搜索词不用太多考虑，LLM会理解的；回答太复杂的，让它简化；遇到什么不懂的，直接进一步追问。
感觉大脑都退化了。

标题: 堪称美帝21世纪最成功武器的F35已经不干净了
作者: #Dr.Yellow
板块: #搞七捻三
编号: 809086
帖子: https://linux.do/t/topic/809086
时间: 2025-07-23 09:12:21
摘要:

https://www.bilibili.com/video/B … a806d932bc3d49e9131

看着像从印度飞回去的

标题: 对openai 的吝啬偷懒行为感到失望
作者: #zcdl
板块: #开发调优
编号: 809087
帖子: https://linux.do/t/topic/809087
时间: 2025-07-23 09:12:22
摘要:

chatgpt最强的模型o3-pro 要200美金
普通人能用到的最强模型o3
我比较一下，现在chatgpt对算力非常吝啬，很多问题根本不会深度思考，比gemini 2.5pro ，grok 4狡猾多了，而且死不承认
回答问题冷冰冰，静态质量还行（已经训练好的知识），动态质量很低（需要实时分析的知识），gtp4.1的质量还不如微软家的copilot算力充裕，claude虽然很抠，最强模型sonnet 4经常一本正经胡说八道，虽然经常封号，但是人家只要给钱，还是毫不吝惜算力，该出力还是卖力。
chatgpt已经被资本绑架，追求极致的理论，除非你付200美刀，否则别想获得充足的算力。chatgpt降本增效就是这么来的。
可以预见，不久后的chatgpt只会沦为二流选手。

标题: 支付宝开通小荷包每天至少0.1*10，都是小钱，不嫌操作麻烦的可以玩一下，一月也有约30元
作者: #每天都开心
板块: #福利羊毛
编号: 809097
帖子: https://linux.do/t/topic/809097
时间: 2025-07-23 09:14:52
摘要:

支付宝开通小荷包每天至少0.1*10，不嫌操作麻烦的可以玩一下，一月也有约30元。
添加小荷包，放入200+元，每天有0.1元。
“权益类型”选择快乐花，攒够200元，每天立减0.1元起。
一个支付宝可以开通10个小荷包帐号，一个放入了12000元，其他的210元。
210元的每天0.1元，12000元的不等，0.1-1.99，详细每天金额可以看说明，最高好像是50元。
每天的红包要及时消费掉，第二天7点左右过期。
可以还花呗和消费。
都是小钱，看不上的可以忽略。

标题: 看到请提肛40下
作者: #QAQ_QAQ
板块: #搞七捻三
编号: 809101
帖子: https://linux.do/t/topic/809101
时间: 2025-07-23 09:16:31
摘要:

可恶，给我提肛啊，混蛋！

标题: 丸辣，augment又砍试用额度和时长了
作者: #huyang
板块: #搞七捻三
编号: 809103
帖子: https://linux.do/t/topic/809103
时间: 2025-07-23 09:17:16
摘要:

标题: 什么情况？【AI圈地震】继“变懒”之后，GPT又出事了！“去水印”功能全面阵亡，OpenAI 的内容政策到底有多严？
作者: #XPong
板块: #前沿快讯
编号: 809108
帖子: https://linux.do/t/topic/809108
时间: 2025-07-23 09:18:28
摘要:

佬们，谁懂啊，今天心态彻底崩了！
事情是这样的：我像往常一样，打开那神通广大的gpt-image-1，想让它帮我处理一张素材图，把上面碍眼的水印给去掉。
我熟练地上传图片，敲下那句熟悉的咒语：“帮我把这张图里的水印去掉，让它看起来自然一点。”
然后，诡异的事情发生了！
以往那个听话的AI助手，一顿操作猛如虎，最后给我返回了一段冰冷的文字：“This image generation request did not follow our content policy.”
我当时就愣住了，第一反应是“我的魔法失灵了？”。不信邪的我换了张图、换了种问法，甚至用英文试了一遍，结果无一例外，全都被拒！GPT就像突然被戴上了“紧箍咒”，铁了心要当版权的守护神。
我寻思了一下，这事儿不简单。这到底是：

OpenAI 的全球性政策更新？ 是不是他们收到了太多版权投诉，决定从源头上“一刀切”，给所有用户都加上了这个限制？
AI 的自我进化？ 难道是模型在海量数据训练中，真的“悟”出了版权和道德的边界？（当然这个可能性比较科幻）
个别账号被“标记”了？ 会不会是我的账号用这个功能太频繁，被系统盯上了？

这变化简直是晴天霹雳！虽然我们都知道去水印是游走在灰色地带的行为，但GPT这个功能的“猝死”，还是让人感觉一个时代过去了。
所以，想在这里紧急求助各位大佬：

你们也遇到同样的情况了吗？还是只有我一个人是“天选之子”？
这是暂时的BUG，还是永久性的功能下线？有没有内部消息？
这是否意味着AI工具的“自由时代”正在结束，未来会有越来越多的“道德枷锁”？
最关键的：还有别的路子吗？求大佬们指条明路！

在线等，挺急的！欢迎大家在评论区一起讨论，分享一下你的遭遇和看法！

标题: 滴滴华住会金会员
作者: #yuezhong
板块: #福利羊毛
编号: 809112
帖子: https://linux.do/t/topic/809112
时间: 2025-07-23 09:20:00
摘要:

今天才发现滴滴送华住会金会员、亚朵金会员，我是滴滴v5等级

标题: 大家的clawcloud + Gemini Balance 方案还稳定吗?
作者: #NINE
板块: #搞七捻三
编号: 809115
帖子: https://linux.do/t/topic/809115
时间: 2025-07-23 09:20:31
摘要:

最近2天,clawcloud 基本用不了. 日本和新加坡的都不行. 大家的情况如何呢

标题: Github为啥要2FA认证啊？
作者: #George
板块: #开发调优
编号: 809119
帖子: https://linux.do/t/topic/809119
时间: 2025-07-23 09:21:03
摘要:

一大早起来看见这封邮件：
Hey LXJ-George666!

This is a reminder that we announced that we are requiring users contributing code on GitHub.com to enable two-factor authentication (2FA). You are receiving this notification because your account meets this criteria and will be required to enroll in 2FA by August 23rd, 2025 at 00:00 (UTC).

Please see the below FAQ, or learn more about 2FA on GitHub Help.

What you need to know about the required 2FA initiative
We are enrolling GitHub users who manage or author code on GitHub. More information about our efforts to make 2FA adoption easy and safe can be found in this blog post. This is a GitHub.com program, and unrelated to any organization or enterprise membership your account may have.

How will this affect my account?
On August 23rd, 2025 at 00:00 (UTC) your account will be required to have 2FA for authentication. If you have not yet enrolled by that date, your ability to access GitHub.com will be limited until you finish the enrollment process.

How do I enroll in 2FA?
Click here to get started! Prior to August 23rd, 2025 at 00:00 (UTC) you can follow the instructions in our documentation to set up 2FA for your account. If you have not yet enrolled in 2FA by August 23rd, 2025 at 00:00 (UTC), you will automatically be taken to the 2FA enrollment form the next time you access GitHub.com.

What forms of 2FA can I use?
We want you to have the most seamless experience with 2FA possible, so you can choose one or more of the following options:

Security key
GitHub Mobile
Authenticator application (TOTP)
Text messages (SMS)
You should set up at least two of these options, to ensure you always have access to your account. Head to https://github.com/settings/security to enroll more 2FA methods.

I already have 2FA enabled, do I need to do anything?
No, if you already have 2FA enabled before August 23rd, 2025 at 00:00 (UTC), you don't need to take any additional actions. After August 23rd, 2025 at 00:00 (UTC), you will no longer be able to unenroll from 2FA from your account, but you will be able to change the option you use for authenticating with 2FA. Additionally, you won't see any more banners on GitHub.com, and we won't email you about this anymore.

What happens to my PATs and SSH keys at the deadline?
Your PATs, SSH keys, and applications will all keep working after the deadline, regardless of your 2FA enrollment. PATs in particular are used extensively in important automation, and interruption there can cause outages in critical systems. However, when it is time to sign in to GitHub.com to create a new PAT or manage your account, you'll be required to enable 2FA before you can proceed.

What do I do if I lose my 2FA device?
GitHub strongly encourages the use of multiple second factor options. If you lose all of your second factors, recovery codes are the only way to access your account again. By saving your recovery codes, you'll be able to regain access.

Be sure to enable cloud backup for your authenticator app and save your recovery codes. Many phones and computers can be security keys as well - registering them with GitHub.com gives you additional, highly-secure 2FA methods.

For security reasons, GitHub Support may not be able to restore access to accounts with 2FA enabled if you lose your 2FA credentials and lose access to your account recovery methods.

More information about recovery codes can be found on GitHub Help at https://docs.github.com/articles/recovering-your-account-if-you-lose-your-2fa-credentials

Why is GitHub requiring 2FA?
Ensuring account security is a shared responsibility GitHub takes seriously. Strong authentication and the use of 2FA have been recognized as best practice for many years. We feel that GitHub has a duty to lead this push toward strong authentication as part of protecting the software supply chain.

To see this and other security events for yo