LeanCloud 宣布停止对外提供服务
#PaaS #边缘计算
via @[email protected]
2021 年 4 月 6 日, 心动网络完成对 LeanCloud 收购; 2023 年 12 月 19 日, 联合创始人兼 CEO 离职. LeanCloud 自收购前夕, 其收入主要来源就已经主要为游戏类客户, 其中心动网络就是其最重要的客户, 收购之后 LeanCloud 开始整合进入心动网络旗下的游戏开发服务平台 TapTap Developer Services (TDS) 之中.昨天, 也就是 2026 年 1 月 12 日, LeanCloud 发布公告宣布即日起停止新用户注册并停止新应用注册, 存量客户留有一年迁移时间, 即明年同日平台正式关闭所有对公众服务.
#PaaS #边缘计算
via @[email protected]
#吐槽
In reply to nevent1q…6qzy
_________________________
Use this address to send an email to GitHub customer service for request a 2FA reset. Then, wait one to three months for a reply.
via Nostr@cxplay
In reply to nevent1q…6qzy
_________________________
Use this address to send an email to GitHub customer service for request a 2FA reset. Then, wait one to three months for a reply.
via Nostr@cxplay
#吐槽
In reply to nevent1q…phr4
_________________________
这个问题比起那些还算小, 只是随手炸掉一些企业网络设备, 抱怨的也只有 IT 管理员.
via Nostr@cxplay
In reply to nevent1q…phr4
_________________________
这个问题比起那些还算小, 只是随手炸掉一些企业网络设备, 抱怨的也只有 IT 管理员.
via Nostr@cxplay
#吐槽
读的时候无所谓, 真到要拼写的时候, 大脑总会不自觉宕机, judgement? judgment?
american english - Is the proper spelling “judgment” or “judgement”? - English Language & Usage Stack Exchange
https://english.stackexchange.com/questions/1623/is-the-proper-spelling-judgment-or-judgement
#English
via Nostr@cxplay
读的时候无所谓, 真到要拼写的时候, 大脑总会不自觉宕机, judgement? judgment?
american english - Is the proper spelling “judgment” or “judgement”? - English Language & Usage Stack Exchange
https://english.stackexchange.com/questions/1623/is-the-proper-spelling-judgment-or-judgement
#English
via Nostr@cxplay
#吐槽
In reply to nevent1q…wuqj
_________________________
lol, which 2FA method are you using?
via Nostr@cxplay
In reply to nevent1q…wuqj
_________________________
lol, which 2FA method are you using?
via Nostr@cxplay
#吐槽
Cloudflare 三天前更新, 把自己的公共 DNS 解析器 1.1.1.1 的缓存响应顺序改出了一点问题, CNAME 响应的本来是先响应解析结果 example.com IN CNAME cname.org 然后再跟着 cname.org IN A 1.0.0.1. 更新之后突然之间变成了 example.com 的响应直接先是 cname.org IN A 1.0.0.1, 然后才是 example.com IN CNAME cname.org.
本来 DNS 也没严格规定响应结果的顺序, 只要能解析出 IP 就行. 但是另一边, 某些企业的思科交换机预设了 1.1.1.1 为 DNS, 而交换机系统解析 NTP 服务器和 www.cisco.com 的时候只会按照 DNS 响应结果顺序去找自己要的 IP, 于是第一条本来就是是结果的响应大概是被当成错误处理掉了, 因为响应变成了 canme.org 的 A 记录, 而预期应该是 example.com 的 A 记录. 然后交换机系统来到第二条看到一个 CNAME 记录, 但是继续往下找却没找到这个 CNAME 的 IP, 于是认为是解析失败了.
Cloudflare Status - Global Issues with 1.1.1.1 public resolver
https://www.cloudflarestatus.com/incidents/rk3dgkmy89kc
Cisco switches hit by reboot loops due to DNS client bug
https://www.bleepingcomputer.com/news/security/cisco-switches-hit-by-reboot-loops-due-to-dns-client-bug/?sa=1#cid37986
#Cloudflare #DNS
via Nostr@cxplay
Cloudflare 三天前更新, 把自己的公共 DNS 解析器 1.1.1.1 的缓存响应顺序改出了一点问题, CNAME 响应的本来是先响应解析结果 example.com IN CNAME cname.org 然后再跟着 cname.org IN A 1.0.0.1. 更新之后突然之间变成了 example.com 的响应直接先是 cname.org IN A 1.0.0.1, 然后才是 example.com IN CNAME cname.org.
本来 DNS 也没严格规定响应结果的顺序, 只要能解析出 IP 就行. 但是另一边, 某些企业的思科交换机预设了 1.1.1.1 为 DNS, 而交换机系统解析 NTP 服务器和 www.cisco.com 的时候只会按照 DNS 响应结果顺序去找自己要的 IP, 于是第一条本来就是是结果的响应大概是被当成错误处理掉了, 因为响应变成了 canme.org 的 A 记录, 而预期应该是 example.com 的 A 记录. 然后交换机系统来到第二条看到一个 CNAME 记录, 但是继续往下找却没找到这个 CNAME 的 IP, 于是认为是解析失败了.
Cloudflare Status - Global Issues with 1.1.1.1 public resolver
https://www.cloudflarestatus.com/incidents/rk3dgkmy89kc
Cisco switches hit by reboot loops due to DNS client bug
https://www.bleepingcomputer.com/news/security/cisco-switches-hit-by-reboot-loops-due-to-dns-client-bug/?sa=1#cid37986
#Cloudflare #DNS
via Nostr@cxplay
#吐槽
In reply to nevent1q…hv4z
_________________________
I am always sensitive to any naming or convention that is described as "human-readable" because they virtually imply permanence, despite the fact that I could theoretically modify them. However, doing so would break many references and links that are built upon these readable names. In the fediverse, it even binds user identities to domain names, once key exchange occurs, the domain name effectively becomes an immutable resource.
via Nostr@cxplay
In reply to nevent1q…hv4z
_________________________
I am always sensitive to any naming or convention that is described as "human-readable" because they virtually imply permanence, despite the fact that I could theoretically modify them. However, doing so would break many references and links that are built upon these readable names. In the fediverse, it even binds user identities to domain names, once key exchange occurs, the domain name effectively becomes an immutable resource.
via Nostr@cxplay
#吐槽
每个人都要有自己的「摇篮」系统
“死了么”App登顶中国苹果付费软件榜 | 联合早报
https://www.zaobao.com.sg/realtime/china/story20260111-8082766
via Nostr@cxplay
每个人都要有自己的「摇篮」系统
“死了么”App登顶中国苹果付费软件榜 | 联合早报
https://www.zaobao.com.sg/realtime/china/story20260111-8082766
via Nostr@cxplay
#吐槽
In reply to nevent1q…y95y
_________________________
那当然看不到了, 能直接移动支付为什么还要把卡拿出来刷 POS
via Nostr@cxplay
In reply to nevent1q…y95y
_________________________
那当然看不到了, 能直接移动支付为什么还要把卡拿出来刷 POS
via Nostr@cxplay
#吐槽
In reply to nevent1q…tnk3
_________________________
或者说是如果不指示 Grok 去读, 拿它就会把图片分开单独处理, 最后回复也只有一张图.
不过即使是指示了, Grok 也还没办法把四张切片组合起来当成一张完整的图去对待.
https://xcancel.com/i/status/2010047581368324202
via Nostr@cxplay
In reply to nevent1q…tnk3
_________________________
或者说是如果不指示 Grok 去读, 拿它就会把图片分开单独处理, 最后回复也只有一张图.
不过即使是指示了, Grok 也还没办法把四张切片组合起来当成一张完整的图去对待.
https://xcancel.com/i/status/2010047581368324202
via Nostr@cxplay
#吐槽
In reply to nevent1q…hqey
_________________________
于是很多画师开始故意把一张竖屏的图切成四张来发, 因为 Grok 只会读其中一张图. 全靠客户端将四张图纵向排列之后恢复大部分视觉效果
* https://xcancel.com/i/status/2010036884320202800
* https://xcancel.com/i/status/2010034849625588009
via Nostr@cxplay
In reply to nevent1q…hqey
_________________________
于是很多画师开始故意把一张竖屏的图切成四张来发, 因为 Grok 只会读其中一张图. 全靠客户端将四张图纵向排列之后恢复大部分视觉效果
* https://xcancel.com/i/status/2010036884320202800
* https://xcancel.com/i/status/2010034849625588009
via Nostr@cxplay
#吐槽
In reply to nevent1q…k5d2
_________________________
Yes, It's clear that Android native users are excluded, all thanks to Amber.
via Nostr@cxplay
In reply to nevent1q…k5d2
_________________________
Yes, It's clear that Android native users are excluded, all thanks to Amber.
via Nostr@cxplay
#吐槽
#原神 HoYoLAB 的官方账号「原神官方」自去年 12 月 31 日最后一期放送完钟离的Q版生日贺图[1]之后, 2026 年以来的所有角色生日都没有Q版生日贺图了.
[1]: https://www.hoyolab.com/article/43001634
via Nostr@cxplay
#原神 HoYoLAB 的官方账号「原神官方」自去年 12 月 31 日最后一期放送完钟离的Q版生日贺图[1]之后, 2026 年以来的所有角色生日都没有Q版生日贺图了.
[1]: https://www.hoyolab.com/article/43001634
via Nostr@cxplay