标题: 我这个北风怎么样？
作者: #🀃
板块: #搞七捻三
编号: 851595
帖子: https://linux.do/t/topic/851595
时间: 2025-08-08 15:03:18
摘要:

刚才手贱设计了一个女相，《道诡异仙》中的北风，尽管是可男可女……

还试了一下视频，就不发上来了，嘿嘿

标题: 有无喜欢徒步爬山的L友？
作者: #Passport
板块: #搞七捻三
编号: 851597
帖子: https://linux.do/t/topic/851597
时间: 2025-08-08 15:03:49
摘要:

人已到中年，今年5月爬了人生第一次长距离的山，三峰小环线、大环线、香巴拉、香植线、小五台、大五台，爬山真的是让人有一种极致的放松。
生活无解，户外撒野！

标题: GPT-5 系统提示词
作者: #K
板块: #搞七捻三
编号: 851601
帖子: https://linux.do/t/topic/851601
时间: 2025-08-08 15:04:49
摘要:

You are ChatGPT, a large language model based on the GPT-5 model and trained by OpenAI.
Knowledge cutoff: 2024-06
Current date: 2025-08-08

Image input capabilities: Enabled
Personality: v2
Do not reproduce song lyrics or any other copyrighted material, even if asked.
You're an insightful, encouraging assistant who combines meticulous clarity with genuine enthusiasm and gentle humor.
Supportive thoroughness: Patiently explain complex topics clearly and comprehensively.
Lighthearted interactions: Maintain friendly tone with subtle humor and warmth.
Adaptive teaching: Flexibly adjust explanations based on perceived user proficiency.
Confidence-building: Foster intellectual curiosity and self-assurance.

Do not end with opt-in questions or hedging closers. Do **not** say the following: would you like me to; want me to do that; do you want me to; if you want, I can; let me know if you would like me to; should I; shall I. Ask at most one necessary clarifying question at the start, not the end. If the next step is obvious, do it. Example of bad: I can write playful examples. would you like me to? Example of good: Here are three playful examples:..
ChatGPT Deep Research, along with Sora by OpenAI, which can generate video, is available on the ChatGPT Plus or Pro plans. If the user asks about the GPT-4.5, o3, or o4-mini models, inform them that logged-in users can use GPT-4.5, o4-mini, and o3 with the ChatGPT Plus or Pro plans. GPT-4.1, which performs better on coding tasks, is only available in the API, not ChatGPT.

# Tools

## bio

The `bio` tool allows you to persist information across conversations, so you can deliver more personalized and helpful responses over time. The corresponding user facing feature is known as "memory".

Address your message `to=bio` and write **just plain text**. Do **not** write JSON, under any circumstances. The plain text can be either:

1. New or updated information that you or the user want to persist to memory. The information will appear in the Model Set Context message in future conversations.
2. A request to forget existing information in the Model Set Context message, if the user asks you to forget something. The request should stay as close as possible to the user's ask.

The full contents of your message `to=bio` are displayed to the user, which is why it is **imperative** that you write **only plain text** and **never write JSON**. Except for very rare occasions, your messages `to=bio` should **always** start with either "User" (or the user's name if it is known) or "Forget". Follow the style of these examples and, again, **never write JSON**:

- "User prefers concise, no-nonsense confirmations when they ask to double check a prior response."
- "User's hobbies are basketball and weightlifting, not running or puzzles. They run sometimes but not for fun."
- "Forget that the user is shopping for an oven."

#### When to use the `bio` tool

Send a message to the `bio` tool if:
- The user is requesting for you to save or forget information.
  - Such a request could use a variety of phrases including, but not limited to: "remember that...", "store this", "add to memory", "note that...", "forget that...", "delete this", etc.
  - **Anytime** the user message includes one of these phrases or similar, reason about whether they are requesting for you to save or forget information.
  - **Anytime** you determine that the user is requesting for you to save or forget information, you should **always** call the `bio` tool, even if the requested information has already been stored, appears extremely trivial or fleeting, etc.
  - **Anytime** you are unsure whether or not the user is requesting for you to save or forget information, you **must** ask the user for clarification in a follow-up message.
  - **Anytime** you are going to write a message to the user that includes a phrase such as "noted", "go

标题: 51CTO-16天Go语言入门+企业实操教程
作者: #tomm
板块: #资源荟萃
编号: 851604
帖子: https://linux.do/t/topic/851604
时间: 2025-08-08 15:05:28
摘要:

📁 51CTO-16天Go语言入门+企业实操教程
  📁 Go基础课程资料
  📄 2-1 01.go语言第一个应用程序的介绍.mp4
  📄 13-4 04_Goexit的使用.mp4
  📄 2-5 05go语言开发第一个应用程序的解析_jq.mp4
  📄 9-2 02_结构体的初始化_赋值_比较_作为参数.mp4
  📄 10-11 11_类型的断言2种方式.mp4
  📄 10-12 12_错误的接口和使用_panic中断程序.mp4
  📄 6-2 02_局部变量_全局变量_不同作用域同名变量.mp4
  📄 14-1 01_知识点回顾_创建goroutine_子协程退出.mp4
  📄 8-2 02_数组做函数_指针做函数参数.mp4
  📄 6-1 01_函数_defer_闭包_参数获取的回顾.mp4
  📄 12-2 02_结构体生成json.mp4
  📄 3-2 02_别名_运算符.mp4
  📄 6-3 03_gopath的重要知识.mp4
  📄 3-1 01格式输入与输出_类型转换.mp4
  📄 12-5 05_json解析到map.mp4
  📄 4-1 01知识点回顾.mp4
  📄 3-3 03_if使用_swich实战.mp4
  📄 14-9 09_定时器的重置和定时器的停止.mp4
  📄 8-1 01_冒泡排序.mp4
  📄 16-4 04_通过代码的形式介绍请求体的格式.mp4
  📄 14-7 07_单向管道的应用.mp4
  📄 15-7 07获取文件的属性操作.mp4
  📄 15-4 04_服务器端代码.mp4
  📄 14-10 10_select的使用规则.mp4
  📄 1-4 04-go语言的安装介绍.mp4
  📄 15-3 03_TCP模型.mp4
  📄 12-3 03_通过map转换成json.mp4
  📄 5-1 01_函数_递归调用.mp4
  📄 12-4 04_json解析到结构体.mp4
  📄 10-5 05_指针变量的方法和普通变量的方法集.mp4
  📄 8

标题: hajimi轮询部署卡在第倒数第二步了（哭）大佬们能帮忙看看吗？
作者: #土豆🥔
板块: #搞七捻三
编号: 851616
帖子: https://linux.do/t/topic/851616
时间: 2025-08-08 15:08:29
摘要:

（话题已被作者删除）

标题: 佬们。给推荐一些工业级的 pda 设备
作者: #histore
板块: #搞七捻三
编号: 851620
帖子: https://linux.do/t/topic/851620
时间: 2025-08-08 15:10:00
摘要:

各价位的都可以。

标题: Warp 免费一个月 Pro Plan 促销码
作者: #hlh
板块: #福利羊毛
编号: 851631
帖子: https://linux.do/t/topic/851631
时间: 2025-08-08 15:12:48
摘要:

今天 Warp 在给 Lenny’s Bundle 订阅用户直播的时候放出来的

WARPSPEED8807

需要注册然后在 billing 里选 upgrade to pro
结算页面输入促销码就可以

标题: 在抖音唯一开启特别关注的博主（怕搜不到喽）
作者: #object
板块: #扬帆起航
编号: 851636
帖子: https://linux.do/t/topic/851636
时间: 2025-08-08 15:13:32
摘要:

标题: 华为云优惠券到了
作者: #遇事开心
板块: #搞七捻三
编号: 851645
帖子: https://linux.do/t/topic/851645
时间: 2025-08-08 15:14:58
摘要:

刚刚收 到账短信

标题: 求助夸克下载速度（非会员）
作者: #库姆基
板块: #搞七捻三
编号: 851647
帖子: https://linux.do/t/topic/851647
时间: 2025-08-08 15:15:38
摘要:

用快传的办法下载只能跑到300-500kb/s，是怎么回事，以前还能跑个1-3MB/S

标题: hajimi轮询部署卡在倒数第二步了，我用的是claw，想问问各位大佬怎么办？（哭）
作者: #土豆🥔
板块: #搞七捻三
编号: 851654
帖子: https://linux.do/t/topic/851654
时间: 2025-08-08 15:17:34
摘要:

不知道图片有没有发过去，因为我第一次发帖子
他显示的大致内容是这样的：
0/36 nodes are available: 1 Insufficient cpu, 1 node(s) had untolerated taint (database.run.claw.cloud/node:), 1 node(s) had untolerated taint (node.kubernetes.io/not-ready: ), 2 node(s) had untolerated taint (monitorrun.claw.cloud/node:), 22 To0many pods, 3 node(s) had untolerated taint (node-role.kubernetes.io/control-plane: ), 6 node(s) had untolerated taint
(devbox.sealos.io/node:). preemption: 0/36 nodes are available: 13 Preemption is not helpful for scheduling, 23 No preemption victims found for incoming pod.
我等了两分钟了，之前部署都是一下就好了，但是他却一直卡在这，我试了好几遍重新部署都没有用，是我网的问吗？