google pixel 4xl 开启超级省电 一晚上差不多 5%？

v 站还一堆推荐配置品牌机的，上次我推荐 diy 不要品牌机被批

@yitingbai 自己找很麻烦 有些人根本不想出门比如我，虽然我在一楼

@youngteam99 不管用，不能入库也直接丢

@Jeremial 时长不受限制。「订阅消息」取消了 7 天内推送消息的时间限制，只要用户没有主动拒收消息推送，开发者就可以随时推送服务通知。对于服务周期超过 7 天的小程序而言，这就完美解决了此前的疑虑。

@Jeremial 至少能到达用户啊，安卓是担心到达不了啊

其他的更屎怎么办，就是因为 app 开发安卓的消息到达率问题，我们只能采用小程序开发

可以啊 行动派 但是你可以会有很多阻力 已有的规则不愿意你打破

@westoy 我先问客服发的什么快递，如果是这两家，而且换不了，我就换卖家

买东西的时候让对方不要用圆通和韵达，这两家根本不管你是否愿意发菜鸟和蜂巢

sony 的 kd 系列，自带安卓系统，虽然是国行安卓，但是也能安装 firetv 和奈飞啥的，挺好用，没广告

win10 自带的就行了 越来越强，火绒啥的其实也是一种病毒

别蒙头写，适当说说思路，我来看

@doveyoung
@Tink
我重新生成密钥，公钥丢服务器上了，但是还是无法连接，windows 客户端正常，唯独 mac 不行，-v 的提示好像没有什么有意义的内容，最后一句是 client_loop: send disconnect: Broken pip

命令：ssh root@ip 地址 -p 6800 -v -i .ssh/id_rsa

提示：
OpenSSH_8.1p1, LibreSSL 2.7.3
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 47: Applying options for *
debug1: Connecting to ...
debug1: Connection established.
debug1: identity file .ssh/id_rsa type 0
debug1: identity file .ssh/id_rsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.9p1 Debian-10+deb10u2
debug1: match: OpenSSH_7.9p1 Debian-10+deb10u2 pat OpenSSH* compat 0x04000000
debug1: Authenticating to ... as 'root'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none
debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:eqhZjfKBNpHc23rSU6SXJpmIVxCmcsDPUF8DXhJlgrw
debug1: Host ... is known and matches the ECDSA host key.
debug1: Found key in /Users/hero/.ssh/known_hosts:1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: .ssh/id_rsa RSA SHA256:VNpcJvlrgTcYGbyKY35kp/e/u2/T0XrEiEBA+b0e+WE explicit
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: .ssh/id_rsa RSA SHA256:VNpcJvlrgTcYGbyKY35kp/e/u2/T0XrEiEBA+b0e+WE explicit
debug1: Server accepts key: .ssh/id_rsa RSA SHA256:VNpcJvlrgTcYGbyKY35kp/e/u2/T0XrEiEBA+b0e+WE explicit
debug1: Authentication succeeded (publickey).
Authenticated to ....).
debug1: channel 0: new [client-session]
debug1: Requesting [email protected]
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype [email protected] want_reply 0
debug1: Remote: /root/.ssh/authorized_keys:3: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
debug1: Remote: /root/.ssh/authorized_keys:3: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
debug1: Sending environment.
debug1: Sending env LC_TERMINAL_VERSION = 3.4.7beta2
debug1: Sending env LANG = zh_CN.UTF-8
debug1: Sending env LC_TERMINAL = iTerm2
client_loop: send disconnect: Broken pip

@malagebidi 这概念十年前就在说，一直不温不火

@hyy1995 我在一个城市十多年了也觉得没有朋友