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

@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 这概念十年前就在说，一直不温不火

@laincat 烧屏只是想象中的

向上管理？向上听命还差不多

小事情吧 大气点

找在银行工作的朋友立马揪下来了，去年我也遇到了，半年款不下来，找朋友一催立马放下来了，这块上他们没有明确的规定说给谁优先，想给谁优先看心情

比 chrome 先发优势，现在还半死不活 该反省了

@Jooooooooo 有问题，万一用户就不通过首页进入，通过其他地方在跳转浏览呢，这种方法要跟踪所有入口
@lychs1998 应该是第二种（有活用户自动续期功能），第四种要跟踪所有 api，第一种可以通过看客户端网络请求，如果没有轮询就不是
@PeterYang1996 ws 对网络和服务器要求太高，v 站本身在外面，有干扰，用 ws 太为难了
@wellsc 你说的是怎么存储，大家讨论的是怎么判断用户是否在线

以上是我的判断，看站长怎么说吧

没看懂

pixel 4xl 没有这选项 安卓 11 最新

支持，逃离吧，深圳不适合你，找个天好点的地方吧 比如昆明

没用大容量盘，光买 920+吗？硬盘怎么搞？

如果不愿意屈服，那就躺平吧，没有必要去争什么