©CC BY-NC-SA 4.0

频道: cx.ms/channel
笔记: cx.ms/memo
博客: cx.ms/blog
剪贴: cx.ms/clip
社交: cx.ms/sns
#吐槽

In reply to nevent1q…fzmx
_________________________

6PB 的长期会员已经发售了... 价格 CN¥4999.
带有独立的服务条款《长期VIP会员服务使用规范》, 也就是 "我已知晓:为充分保护第三方权益,长期VIP会员禁止存储监控影像及直播录屏等文件".

一、文件内容限制规则
1. 禁止存储以下内容:
实时通信类:视频通话、语音通话、会议录像、直播流以及其他本平台禁止的文件内容;
安防监控类:监控影像、门禁录音以及其他本平台禁止的文件内容;
长视频分段:长视频切割文件、直播回放切片以及其他本平台禁止的文件内容;
其他违反相关法律、法规、规范性文件规定以及本平台使用协议、服务条款或相关政策的内容。
2. 本平台有权根据市场情况、法律法规、监管规则、行业政策及用户反馈等因素进行内容限制规则的调整、取消、增加及变更,届时会提前在本平台内公示。
—— http://archive.today/2025.05.14-183504/https://statics.123957.com/static/app_pro/permanentVip.html

这条款有够霸道的. 倒是从原来口中的仅限影音的存储调整成了不限文件格式的存储.

#123云盘

via Nostr@cxplay
#吐槽

In reply to nevent1q…8m95
_________________________

已读回执是社交里面的两难选择. 应该把电子邮件当作普通的纸质邮件的通讯形式来使用, 如果要追求回执就不应该用邮件, 对面要求用电子邮件就说明对面也不希望给你回执, 任何时候都不会主动给回执.

via Nostr@cxplay
#吐槽

我开始怀疑哔哩哔哩是怎么盈利的了

via Nostr@cxplay
#吐槽

今天为了分析 Nostr 的异常客户端让 AI 写了一个简单的 WebSocket tarpit 服务器, 然后最后发现是自己人, 人都麻了, 这就是不好好沟通的下场.
而这个 tarpit 到底应该怎么翻译呢, 焦油坑? 沥青坑?
好是好玩, 但还是要占用连接数和自己的硬件资源, 观察完还是用 WAF 屏蔽掉算了.

via Nostr@cxplay
#吐槽

「韦伯-费希纳定理 ... 人的感觉是和实际的物理量的对数成正比 ...
按照这个规律, 假设你活到八十岁, 那你生命的中点当然是四十岁.
但假设你四岁开始有记忆, 在你的对数感觉里, 生命的中点其实是十八岁.」

「本福特定律 ... 这些符合本福特定律的数据有一个共同的特点: 大小跨越好几个数量级, 但 log 一下就比较均匀 ... 接近对数均匀分布. 在数学上 ... 对数均匀分布的数据集就是会符合本福特定律, 在自然过程中随机演变而来的数据很多都 ... 会不由自主地具有对数尺度均匀的特征, 所以符合本福特定律.」

【毕导】这个定律,预言了你的人生进度条_哔哩哔哩_bilibili
https://www.bilibili.com/video/av114478410699738

via Nostr@cxplay
#吐槽

Dear Nostr client developers, relay automation software developers, protocol extension software developers, please add proper User-Agent headers to your HTTP clients and WebSocket clients, and if necessary declare the client's characteristics and IP range in both directions.

Last night, I blocked some massive resource abusers for my community relay. They all had one thing in common: without a User-Agent, I had no way of knowing who was behind the IP. I recommend that all client developers include the full and correct User-Agent header for both HTTP clients and WebSocket clients, especially for unsolicited messages, and preferably with contact information. I realize that this header can be easily tampered with, but as long as the administrator of a particular dedicated facility declares the IP range and User-Agent characteristics of their client in both directions, this is still valid, as is the case with Googlebot crawlers.

Since I had no way of knowing who was who, I made the mistake of blocking the bot used by Mostr.pub to check the validity of NIP-05 identity in user profiles for a few days, which led to a few minor problems. It was only after a targeted check of the server logs that I realized it was hiding in a visitor with the User-Agent "Deno". cc: Alex Gleason (npub1q3s…d26p)

via Nostr@cxplay
 
 
Back to Top