©CC BY-NC-SA 4.0

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

很显然, #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 Short Text Note by Moss
#吐槽

In reply to nevent1q…7y6x
_________________________

读了一下 NIP-96, 是真的复杂(但也真的足够全面)...
> https://nips.nostr.com/96
自托管媒体服务器, 只要域名还在自己手里, 那么文件是否变动其实都很无所谓, 特别是主要的图像和视频. 对个人来说上传, 处理和下载流程都太繁复了, 是比较适合大型的相对集中化提供媒体文件托管服务的服务商的规范.
个人媒体服务器? 就是把图片 "变" 成 URL 的 "魔法" 而已, 过程越简单越好. Blossom 是更适合个人使用的 "魔法".
PS: 大部分媒体服务器都会保存至少两份缩略图, 这对于个人媒体服务器来说, 1+2 占用的资源得不偿失, 尽管最后磁盘空间最多只是 1+1 的结局, 但依旧不值得. 过大的媒体文件应该当作文件分发, 不应该出现在社交媒体的贴文里并自动加载.

via Nostr@cxplay
#吐槽

🤔
quoting nevent1q…32td
The core difference between blossom and NIP-96 is the focus on re-uploading files
If we want censorship resistant media then we need to be able to re-uploaded the files to other servers. similar to now nostr events get spread around the network
NIP-96 could support re-uploading files but it isn't currently part of the nip

There is also the difference that NIP-96 has a "/.well-known/nostr/nip96.json" file and customizable endpoints. In my view this is not a feature and makes it much more difficult to work with servers since clients must first fetch a map of the endpoints before they can talk to the server.

Blossom however requires blobs be served from the root of the domain ( example.com/.ext ) while this isn't very friendly to server admins it makes things very simple and easy to understand.
Also searching for a missing blob is a simple as replacing the domain. something a user could easily do ( and understand ) in the browser address bar

There are more smaller differences but in my view these are the major ones


via Nostr@cxplay
#吐槽

说起来, 同样是 Runner. Blade Runner 被译作「银翼杀手」, 而 Edgerunners 就被译作「边缘行者」.
Edgerunners 按照赛博朋克wiki上的解释, 这个是街头语言(Streetslang), Edge 意味着赛博朋克世界的 "社会边缘" 地带, 也就是灰色地带. Edgerunners 就是在这个灰色地带生活, 通过植入体对抗公司, 从事灰色产业工作的人.
> https://cyberpunk.fandom.com/wiki/Streetslang

而 Blade Runner 这个名字就更加意识流了, 刀锋行者? (刀锋战士 "Blade" 表示很赞) 译为 "银翼杀手" 的动机就更加迷幻了.

> 台版翻译为什么把Blade Runner翻译成《银翼杀手》,一直是个令观众困惑的问题。一个可能是:因为世界上许多地方的警徽图案都是张开双翼的雄鹰,片中那些杀手也是警方雇员,也会随身携带警徽,所以当时的电影译者就顺手把这个标签打上去了,凑成一个听起来很酷的四字头衔。另一个可能是:因为上面提到的那部Blade Runner(A Movie)小说的第一版封面上,有一只长了翅膀的跑鞋,而电影的台版译者正好看到过这个封面画,就不管故事内容有关无关,直接把翅膀借到译名里了。
> —— https://www.zhihu.com/question/67210956/answer/402339321 (《银翼杀手》这个名字是谁翻译的?)

这么一看, "边缘行者" 好像已经算是不错的译名了, 街头语言令人安心.

PS: 仿生体行者! 灰产杀手!
quoting nevent1q…mr2q
刷 federated timeline 看到两个人的名字分别叫「银翼抄手」和「银耳杀手」… :bgm38:


via Nostr@cxplay
CXPLAY World
#吐槽 In reply to nevent1q…4yc4 _________________________ quoting nevent1q…0ylu Today we were made aware of multiple Fediverse blog posts incorrectly attributing “vote Trump” spam on Bluesky to the Mostr.pub Bridge. This spam is NOT coming from Mostr. From…
When Mostr.pub launched, multiple major servers immediately blocked Mostr, including Mastodon.social. The moderators of Mastodon.social claimed that this was because Nostr was unregulated, and suggested to one user that if they want to bridge their account they should host their own bridge.

That is exactly what momostr.pink, the source of this spam, has done.

The obvious response to the censorship of the Mostr Bridge is to build more bridges.

While we have opted for pro-social policies that aim to reduce spam and build better connections between decentralized platforms, other bridges built to get around censorship of the Mostr Bridge may not — as we’re already seeing.

There will inevitably be multiple bridges, and we’re working on creating solutions to the problems that arise from that. In the meantime, if the Fediverse could do itself a favor and chill with the censorship for two seconds, we might not have so many problems.


via Nostr@cxplay
#吐槽

In reply to nevent1q…4yc4
_________________________

quoting nevent1q…0ylu
Today we were made aware of multiple Fediverse blog posts incorrectly attributing “vote Trump” spam on Bluesky to the Mostr.pub Bridge.

This spam is NOT coming from Mostr. From the screenshots used in these blogs, it's clear the spam is coming from an entirely different bridge called momostr.pink. This bridge is not affiliated with Mostr, and is not even a fork of Mostr. We appreciate that the authors of these posts responded quickly to us and have since corrected the blogs.

Mostr.pub uses stirfry policies for anti-spam filtering. This includes an anti-duplication policy that prevents spam like the recent “vote Trump” posts we’ve seen repeated over and over.

It is important to note WHY there are multiple bridges, though.
#吐槽

In reply to nevent1q…alc5
_________________________

quoting nevent1q…ezwl
Correction: the original version stated that the Mostr.pub bridge was used for a spam wave on Bluesky. This is incorrect, a different bridge between Nostr and the fediverse, momostr.pink, was used. Mostr.pub creator Alex Gleason explains that the Mostr.pub bridge has anti-spam filtering that would have prevented such as spam attack.

https://mastodon.social/@fediversereport/112468656710956489


via Nostr@cxplay
#吐槽

In reply to nevent1q…4ezk
_________________________

- Substack 原文作者错误地把 Mostr.pubMomostr.pink (本次被滥用的中继) 混淆了, Mostr.pub 的开发者在评论区提醒了作者, 现在文章内容已经得到纠正.

- 与 Momostr.pink 中继的管理员取得了联系提醒加强反滥用策略, 但管理员表示所使用的软件 #strfry 并没有直接提供应对的功能和插件, 在之前已经实施了一些简单的策略, 类似的新垃圾内容已经得到了遏制, 但是已经被发送的垃圾内容还没有得到处理.

via Nostr@cxplay
#吐槽

这位朋友最近利用 Nostr 的特点进行了一次模拟攻击, 目的是自动生成密钥对并关注主账号, 达成一百万追随者. 实际上是对公共中继服务器的一次压力测试, 可以看出一些目前 Nostr 网络状态的实际状态.
PS: 这种攻击可能只有实行黑白名单和付费准入的中继才能完全避免. 公共中继除了速率限制基本上没有好的应对措施, 之后要定期清理数据库, 可以一定程度上消除长期影响, 一百万虚假追随者也会随着时间大量消失.
quoting nevent1q…wtyt
Here's how I hit 1 million followers.
https://ron.stoner.com/I_Gained_1_Million_Followers_in_24_Hours/

Key takeaways:

- over half the Nostr listed relays are using some sort of spam mitigation technique(s)
- the attack was still achieveable
- socal media is easily manipulated
- follower counts and engagement are worthless
- content is the real treasure


via Nostr@cxplay Short Text Note by Ron Stoner
#吐槽

#原神 什么? 双子又同框了? 是动画短片? 是飞碟社的饼? 还是DM短片? 等不及了, 快端上来罢!
(十个小时后) 急死我了, 还不发还不发还不发? 吊我胃口是吧. 怎么还不发? 急急急.
https://fxtwitter.com/GenshinImpact/status/1792767528076218658

via Nostr@cxplay
#吐槽

In reply to nevent1q…a5zx
_________________________

是的, 唯一能真正治理滥用的只有中继也就是服务端, 不过目前除了付费墙好像没有什么特别好的办法.

via Nostr@cxplay
#吐槽

Mostr.pubMomostr.pink Bridge 继续被滥用:

Fediverse 和 Bluesky 之间的桥被用来向 Bluesky 发送支持特朗普的垃圾邮件, 这些垃圾邮件来自 Nostr. 垃圾邮件是在 Nostr 上创建的, 而 Nostr 通过 Mostr 桥接器与 fediverse 桥接, 后者又可以与 Bluesky 桥接. 虽然所有网络都有许多方便, 开放注册的地方, 但垃圾邮件往往发生在容易大量注册的地方, 而 Nostr 的协议设计使得创建新账户特别容易.
—— https://fediversereport.com/last-week-in-fediverse-ep-69/ (The Fediverse Report)

支持特朗普的垃圾帖子是如何从 Nostr 转移到 Bluesky 的? 首先, Nostr 内容通过 Mostr Bridge 传播到 Mastodon (基于 ActivityPub 协议). 然后, 使用名为 Bridgy Fed 的工具将内容从 Mastodon 推送到 Bluesky. 这一过程的痕迹出现在 Bluesky 版本的帖子中, 其中的账户柄格式为 npub************.momostr.pink.ap.brid.gy. 其中的第一部分(从 npub 到第一个点)是 Nostr 账户的公钥, 而其余部分(momostr.pink.ap.brid.gy)则包含了用于桥接帖子的工具(Mostr 和 Bridgy Fed)的一些说明.
—— https://conspirator0.substack.com/p/federation-and-political-spam (Conspirador Norteño)

#Nostr #Fediverse #Bluesky

via Nostr@cxplay
#吐槽

In reply to nevent1q…eeu4
_________________________

静态站点生成器主要还得看主题的适配, Hexo 这边也是这样.

via Nostr@cxplay
#吐槽

In reply to nevent1q…89j9
_________________________

梳理一下我的认知时间线, 也补一下这条线程遗漏的:
- 2022 年 08 月 05 日: Pornhub
- 2022 年 11 月 15 日: pixiv, BOOTH, pixivFANBOX
- 2023 年 11 月 08 日: Niconico
- 2024 年 03 月 15 日: Gumroad
- 2024 年 04 月 03 日: DLsite
- 2024 年 05 月 09 日: Niconico
- 2024 年 05 月 21 日: Fantia

via Nostr@cxplay
Back to Top