#吐槽
In reply to nevent1q…csdf
_________________________
这个概念可以解释为什么 #Fediverse 的全球索引无法建立, 而 #Nostr 一开始就有人建立全球索引(Nostr.band). 短期上来说, Nostr.band 的索引完全无利可图, 甚至还会受到两个极端的支持者攻击: 索引不够好用而被攻击为失败产品, 索引太彻底而被攻击为对互联网的监视.
via Nostr@cxplay
In reply to nevent1q…csdf
_________________________
这个概念可以解释为什么 #Fediverse 的全球索引无法建立, 而 #Nostr 一开始就有人建立全球索引(Nostr.band). 短期上来说, Nostr.band 的索引完全无利可图, 甚至还会受到两个极端的支持者攻击: 索引不够好用而被攻击为失败产品, 索引太彻底而被攻击为对互联网的监视.
via Nostr@cxplay
#吐槽
Why are all the NIP-94 implementations server-side only, especially the NIP-96 server, and is it really only the server that can compute the metadata for a file? Why isn't this process done on the client side, and if I insert a random network memes does that mean I'll never be able to add the metadata that makes sense to the client (unless I consider writing event JSON manually)?
As far as I know, all the file metadata for the NIP-35 for Torrent indexing is client-supplied, and users can even fill it in themselves, but somehow it's become a server-only affair with the NIP-96.
#nostr #asknostr
via Nostr@cxplay
Why are all the NIP-94 implementations server-side only, especially the NIP-96 server, and is it really only the server that can compute the metadata for a file? Why isn't this process done on the client side, and if I insert a random network memes does that mean I'll never be able to add the metadata that makes sense to the client (unless I consider writing event JSON manually)?
As far as I know, all the file metadata for the NIP-35 for Torrent indexing is client-supplied, and users can even fill it in themselves, but somehow it's become a server-only affair with the NIP-96.
#nostr #asknostr
via Nostr@cxplay
#吐槽
第一篇写给新手的入门教程, 从密钥对创建到第一条帖子, 包含一些基础的密钥管理和 Nostr 协议常识.
欢迎加入 Nostr, 这是一份快速入门指南. | CXPLAY World
https://blog.cxplay.org/works/nostr-quick-start-guide/
#blog #Nostr
via Nostr@cxplay
第一篇写给新手的入门教程, 从密钥对创建到第一条帖子, 包含一些基础的密钥管理和 Nostr 协议常识.
欢迎加入 Nostr, 这是一份快速入门指南. | CXPLAY World
https://blog.cxplay.org/works/nostr-quick-start-guide/
#blog #Nostr
via Nostr@cxplay
#吐槽
设置 nostr.moe 的一整套, #Nostr 服务端是 0.5c0.5g 的 PaaS 即用即付, 客户端是纯前端的静态托管, 虽然那还在测试阶段, 但目前开销为 0, 不过未来估计也接近于 0. 媒体服务器是最大头, 但并不打算给人选择, nostr.build 已经是最好的了, 如果还要自定义的域名, 那还是请用户自己托管媒体服务器吧, 我自己设置个 OSS 才 5GB 对所有人用来说是太少了, 但如果每个人都自己设置一个, 那就是全都吃饱了.
快让我忘记了上次设置 Mastodon 前查看管理员经验贴后的惊恐, 发现 ActivityPub 就是一个巨型的 PCDN 社交网络, 不仅要存自己的还要存别人的, 还得收发, 数据库带着硬盘和 CPU 没日没夜地满载. 最近听一个朋友说, 单人实例都能快速吃掉了 5GB 的数据库, 最后还是放弃了. 这去中心化的社交何必如此昂贵?
Nostr 的中继确实没有要求互相通讯, 但实际上 strfry 这个最早的的 C++ 中继实现一开始就支持多个中继之间实时同步, 还能仅靠软件本身就组成小型中继集群. 即使如此, 只是用 WebSocket 传 JSON 的协议最终实现设计地再怎么烂也不会消耗掉如此多的资源.
最后还是用的 rnostr, 毕竟有使用经验, 也不需要额外的中继同步功能, 构建一个静态的二进制到处放一行命令就起来了, 导出数据也全是 JSON, 何必如此用 SQL 这种牛刀来杀鸡?
还因为 rnostr 自带全文搜索的 NIP, 虽然索引开销是有点太大了, 但是真方便. 离线了也能往电脑里面的本地中继发, 连上网再 REQ 出来广播出去.
如果真把 Nostr.moe 开放了, 在说明里最好还是多讲点丑话好了, 最终用户离底层协议太近了好像也不是什么好事.
via Nostr@cxplay
设置 nostr.moe 的一整套, #Nostr 服务端是 0.5c0.5g 的 PaaS 即用即付, 客户端是纯前端的静态托管, 虽然那还在测试阶段, 但目前开销为 0, 不过未来估计也接近于 0. 媒体服务器是最大头, 但并不打算给人选择, nostr.build 已经是最好的了, 如果还要自定义的域名, 那还是请用户自己托管媒体服务器吧, 我自己设置个 OSS 才 5GB 对所有人用来说是太少了, 但如果每个人都自己设置一个, 那就是全都吃饱了.
快让我忘记了上次设置 Mastodon 前查看管理员经验贴后的惊恐, 发现 ActivityPub 就是一个巨型的 PCDN 社交网络, 不仅要存自己的还要存别人的, 还得收发, 数据库带着硬盘和 CPU 没日没夜地满载. 最近听一个朋友说, 单人实例都能快速吃掉了 5GB 的数据库, 最后还是放弃了. 这去中心化的社交何必如此昂贵?
Nostr 的中继确实没有要求互相通讯, 但实际上 strfry 这个最早的的 C++ 中继实现一开始就支持多个中继之间实时同步, 还能仅靠软件本身就组成小型中继集群. 即使如此, 只是用 WebSocket 传 JSON 的协议最终实现设计地再怎么烂也不会消耗掉如此多的资源.
最后还是用的 rnostr, 毕竟有使用经验, 也不需要额外的中继同步功能, 构建一个静态的二进制到处放一行命令就起来了, 导出数据也全是 JSON, 何必如此用 SQL 这种牛刀来杀鸡?
还因为 rnostr 自带全文搜索的 NIP, 虽然索引开销是有点太大了, 但是真方便. 离线了也能往电脑里面的本地中继发, 连上网再 REQ 出来广播出去.
如果真把 Nostr.moe 开放了, 在说明里最好还是多讲点丑话好了, 最终用户离底层协议太近了好像也不是什么好事.
via Nostr@cxplay
#吐槽
将 #Nostr 私钥拆分为多片段的集合, 通过 NIP-46 和 NIP-07 完成通讯, 在服务端通过所有个片段的组合完成签名.
暴露在客户端的只有其中一个片段集合, 如果客户端发生泄露, 可以通过轮换集合实现客户端密钥吊销操作.
如果私钥被遗忘, 可以通过多个片段(直到达到设置的阈值)组合完成验证恢复被加密的原始私钥.
igloo 作为 NIP-46 KMS 运行, Frost2x 作为 nos2x 分支的 NIP-07 签名器运行.
via Nostr@cxplay
Invalid media: video
将 #Nostr 私钥拆分为多片段的集合, 通过 NIP-46 和 NIP-07 完成通讯, 在服务端通过所有个片段的组合完成签名.
暴露在客户端的只有其中一个片段集合, 如果客户端发生泄露, 可以通过轮换集合实现客户端密钥吊销操作.
如果私钥被遗忘, 可以通过多个片段(直到达到设置的阈值)组合完成验证恢复被加密的原始私钥.
igloo 作为 NIP-46 KMS 运行, Frost2x 作为 nos2x 分支的 NIP-07 签名器运行.
quoting
nevent1q…gm6z
Apparently video doesn't play on some browsers..
BUMP
nevent1q…jh4a
via Nostr@cxplay
Invalid media: video
#吐槽
In reply to nevent1q…utqt
_________________________
来用 nos.cx.ms, 其实就是我给 nostrudel.ninja 重新中文本地化后的版本.
via Nostr@cxplay
In reply to nevent1q…utqt
_________________________
来用 nos.cx.ms, 其实就是我给 nostrudel.ninja 重新中文本地化后的版本.
via Nostr@cxplay
#吐槽
In reply to nevent1q…73k0
_________________________
三大客户端的功能都已经接近完善了, 底层协议不变动也没什么要变动的, 保持维护就差不多行了, 没有问题为什么要更新呢.
Damus 那边在开发 Android 版本和桌面版本 Notedeck 版本.
via Nostr@cxplay
In reply to nevent1q…73k0
_________________________
三大客户端的功能都已经接近完善了, 底层协议不变动也没什么要变动的, 保持维护就差不多行了, 没有问题为什么要更新呢.
Damus 那边在开发 Android 版本和桌面版本 Notedeck 版本.
via Nostr@cxplay
#吐槽
Immortal 是一个用 Golang 编写的高性能, 可扩展, 可配置的 Nostr 中继实现, 使用 Mongo DB 数据库.
via Nostr@cxplay
Immortal 是一个用 Golang 编写的高性能, 可扩展, 可配置的 Nostr 中继实现, 使用 Mongo DB 数据库.
quoting
nevent1q…wqjx
Announcing Immortal relay version v0.0.8 version! ⚡🪼
Change log 📃:
Supporting shutdown method for manager in gRPC.
Adding pubkey white list black list.
Accepting 1 filter per REQ message. implements: nostr-protocol/nips#1645.
Using mongo db aggregation pipelines to answer to REQ messages.
Fixing possible int overflow, casting int32/64 to uint16 on task scheduler.
Supporting standard NIP-09.
Supporting NIP-62: nostr-protocol/nips#1256.
On Github:
https://github.com/dezh-tech/immortal/releases/tag/v0.0.8
#immortal #dezh #relay #nostr #right_to_vanish
via Nostr@cxplay
#吐槽
Android 开源 #RSS 阅读器 Feeder 已经合并了 #Nostr Feed (NIP-23) 的代码.
https://github.com/spacecowboy/Feeder/commit/7fae5a36af86d24c93663173f10cb3ff57dee1a8
via Nostr@cxplay
Android 开源 #RSS 阅读器 Feeder 已经合并了 #Nostr Feed (NIP-23) 的代码.
https://github.com/spacecowboy/Feeder/commit/7fae5a36af86d24c93663173f10cb3ff57dee1a8
via Nostr@cxplay
#吐槽
刚刚在 #Bluesky 看到有人一口气关注了两万多个人, 叹为观止. 这种超大规模的订阅追随对目前的 #Nostr 来说几乎是不可能的, 因为每多一个追随就要多一个 filter 里面的标签, 刷新一次时间线就要有两万多个标签的 filter 发送到已经连接的中继器里面, 就算客户端做好了分割 filter 的功能, 两万个标签的 filter 请求也是随便就能让客户端和服务端超载的大小, 要么拒绝要么查询失败.
via Nostr@cxplay
刚刚在 #Bluesky 看到有人一口气关注了两万多个人, 叹为观止. 这种超大规模的订阅追随对目前的 #Nostr 来说几乎是不可能的, 因为每多一个追随就要多一个 filter 里面的标签, 刷新一次时间线就要有两万多个标签的 filter 发送到已经连接的中继器里面, 就算客户端做好了分割 filter 的功能, 两万个标签的 filter 请求也是随便就能让客户端和服务端超载的大小, 要么拒绝要么查询失败.
via Nostr@cxplay
#吐槽
In reply to nevent1q…z22s
_________________________
Nice. And maybe you need fix your NIP-05 addr's CORS issue:
https://cors-test.codehappy.dev/?url=https%3A%2F%2Flecturify.net%2F.well-known%2Fnostr.json%3Fname%3Dyonle&method=get
via Nostr@cxplay
In reply to nevent1q…z22s
_________________________
Nice. And maybe you need fix your NIP-05 addr's CORS issue:
https://cors-test.codehappy.dev/?url=https%3A%2F%2Flecturify.net%2F.well-known%2Fnostr.json%3Fname%3Dyonle&method=get
via Nostr@cxplay
#吐槽
Chinese Fediverse instance nya.one claims that their storage provider Wasabi deactivated the account without warning. As a result, 2TB of data is currently inaccessible.
#Nostr #Fediverse #Blossom
via Nostr@cxplay
Chinese Fediverse instance nya.one claims that their storage provider Wasabi deactivated the account without warning. As a result, 2TB of data is currently inaccessible.
#Nostr #Fediverse #Blossom
quoting nevent1q…cekn
我们的 S3 存储服务器商 Wasabi 在没有给出任何信息的情况下停权了我们的存储账号，导致目前喵窝的整套对象存储资料和超过 2TB 累积媒体数据处于不可访问的状态。我们会尽快尝试切换到其他服务商，在此期间媒体文件都会出现无法访问的问题，极端情况下可能会损失建站以来所有的媒体数据。很抱歉给您带来的不便，我们将持续跟进处理这件事。
via Nostr@cxplay
NyaOne Support (npub1hxk…y7zv)
Short Text Note by NyaOne Support
seen on wss://relay.noswhere.com
#吐槽
The Nostr community should also learn from these mature experiences in order to cope with the growing number of users. People's efforts against "censorship" can be an obstacle in the way of "moderation", but that doesn't mean that the anti-censorship vision is wrong, but that we need stronger moderation strategies to deal with anti-censorship abuses. Any product based on Nostr can advertise itself as "anti-censorship" but not as "anti-moderation", starting from the basics of anti-abuse to building community policies.
#Nostr #Ditto
via Nostr@cxplay
The Nostr community should also learn from these mature experiences in order to cope with the growing number of users. People's efforts against "censorship" can be an obstacle in the way of "moderation", but that doesn't mean that the anti-censorship vision is wrong, but that we need stronger moderation strategies to deal with anti-censorship abuses. Any product based on Nostr can advertise itself as "anti-censorship" but not as "anti-moderation", starting from the basics of anti-abuse to building community policies.
#Nostr #Ditto
quoting nevent1q…qzee
Content Moderation: Educational Resources - IFTAS Connect
https://connect.iftas.org/library/moderation-guides/content-moderation-educational-resources/
via Nostr@cxplay
CXPLAY's Clip (npub18dc…sy5z)
Short Text Note by CXPLAY's Clip
seen on wss://relay.damus.io
#吐槽
🦀
via Nostr@cxplay
🦀
quoting nevent1q…ax8y
## rust-nostr v0.32 is out! 🦀
### Versions
Rust & JS: `v0.32.0`
Python, Kotlin & Swift: `v0.32.1`
From this release all packages for all languages will have the same major and minor versions.
### Summary
Added `async`/`future` support to Python, Kotlin and Swift, added automatic authentication to relays (NIP-42, can be deactivated in client options), improvements to relay limits, many bug fixes (relays not auto reconnect, wrong query order for SQLite, tokio panic when using SQLite database in bindings) and more!
Note for kotlin devs: from this release the packages will be published at `org.rust-nostr` instead of `io.github.rust-nostr`.
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to all contributors!
* benthecarman (npub1u8l…turz)
* xy (npub1q0u…9py9)
* RydalWater (npub1zwn…fhrf)
Thanks also to Don't ₿elieve the Hype 🦊 (npub1nxa…a6q8) for helping to discover some nasty bugs!
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr
via Nostr@cxplay
#吐槽
很显然, #Nostr 现在不会有屏蔽(block), 未来也不会有. 静音(Mute)是目前用户侧能在客户端的帮助下能做出的最大的主动信息审查权利. fiatjaf 依旧坚持应该从中继服务端一侧实现过滤.
via Nostr@cxplay
很显然, #Nostr 现在不会有屏蔽(block), 未来也不会有. 静音(Mute)是目前用户侧能在客户端的帮助下能做出的最大的主动信息审查权利. fiatjaf 依旧坚持应该从中继服务端一侧实现过滤.
quoting nevent1q…9c37
To prevent ladies from being harassed, we need to optimize the way to mute accounts. Now the way to mute accounts is that I cannot see the reply posts and all the post information of the person I muted. But he can see all my posts, and can also forward and reply. We should increase some privacy, that is, if I mute the other party's account, the muted account will not be able to see all my dynamic information. In this way, the harassing account cannot continue to harass by replying, forwarding, liking, and zap. #[0]
quoting nevent1q…dvdl
That's not possible.
My proposed solution is for relay-based filtering.
via Nostr@cxplay
Moss (npub129z…y5gm)
Short Text Note by Moss
seen on wss://relay.noswhere.com, wss://nostr.mom
