©CC BY-NC-SA 4.0
🚩加入 Nostr!moe 社区: join.nostr.moe
🚩加入 Nostr!moe 社区: join.nostr.moe
#原神 千织不过数值加强后的原始人罢了! 枫丹出稻妻版本强度的角色, 岩系真孤儿啊.
> 数值爆炸的原始人?千织最精简的硬核攻略及数据解析: https://www.bilibili.com/video/BV1HK421x7eq/��
#吐槽
把快递业稍微整顿了一下, 接下来可能就是直播带货了, 以防有人认为线下实体店都是被电商和快递打趴下的. 需要计算一下房租和人力占实体店运营成本的多少, 而剩下的部分才能继续被电商和快递盘剥.
咋们就是说元宇宙可不可以解决一下这些实体店的房租问题? 或者可以让工人也能 "远程办公"?
把快递业稍微整顿了一下, 接下来可能就是直播带货了, 以防有人认为线下实体店都是被电商和快递打趴下的. 需要计算一下房租和人力占实体店运营成本的多少, 而剩下的部分才能继续被电商和快递盘剥.
咋们就是说元宇宙可不可以解决一下这些实体店的房租问题? 或者可以让工人也能 "远程办公"?
#吐槽
In reply to nevent1q…0dml
_________________________
Web3 差一点就想要选择不向前兼容 Web 1.0 和 Web 2.0, 几乎想要把 OSI 模型上的每一层都推翻重建. 最后自上向下地卡在了基础设施上. 什么时候推翻重建一下 BGP, IP 和 DNS?
In reply to nevent1q…0dml
_________________________
Web3 差一点就想要选择不向前兼容 Web 1.0 和 Web 2.0, 几乎想要把 OSI 模型上的每一层都推翻重建. 最后自上向下地卡在了基础设施上. 什么时候推翻重建一下 BGP, IP 和 DNS?
#吐槽
In reply to nevent1q…r455
_________________________
ahhahaha, QQ.com email addrs, classic. Unless it's really being abused. I'd even go so far as to say the info is fake, and the QQ email is linked to another messenger app that's need fully KYC in China. 💀💀
In reply to nevent1q…r455
_________________________
ahhahaha, QQ.com email addrs, classic. Unless it's really being abused. I'd even go so far as to say the info is fake, and the QQ email is linked to another messenger app that's need fully KYC in China. 💀💀
#吐槽
In reply to nevent1q…pwgw
_________________________
I think the innocent mail system is being abused and CN TLDs in China need to fully KYC. Maybe report it to mail admin or ASN admin or domain admin.💀
In reply to nevent1q…pwgw
_________________________
I think the innocent mail system is being abused and CN TLDs in China need to fully KYC. Maybe report it to mail admin or ASN admin or domain admin.💀
#吐槽
In reply to nevent1q…pu6w
_________________________
So, which TLD and MX records are the spammers using?
In reply to nevent1q…pu6w
_________________________
So, which TLD and MX records are the spammers using?
#吐槽
In reply to nevent1q…txyx
_________________________
确实是有用, 但是目前没有太好的实现, Amethyst 为了向后兼容, 这个 "编辑" 功能实际上就是一个对 kind:1 的评论, 其中多了一个标记内容已编辑的标签, 类型被定义为 kind:1010.
In reply to nevent1q…txyx
_________________________
确实是有用, 但是目前没有太好的实现, Amethyst 为了向后兼容, 这个 "编辑" 功能实际上就是一个对 kind:1 的评论, 其中多了一个标记内容已编辑的标签, 类型被定义为 kind:1010.
#吐槽
最近 Amethyst 引入了一个给 Nostr 笔记再 "编辑" 的功能(就像 Twitter 那样的). 但是社区很多人认为为短文本消息(kind:1)的再编辑是徒增复杂性, 本身 "删除" 功能就是一种 "看起来有用" 的实现, 再编辑只是这种做法的延续.
目前 Nostr 允许内容互相替换的只有 kind:30023 (参数化可替换事件), 如果再引入编辑功能可能会继续影响事件的传递和检索效率(服务端一侧).
最近 Amethyst 引入了一个给 Nostr 笔记再 "编辑" 的功能(就像 Twitter 那样的). 但是社区很多人认为为短文本消息(kind:1)的再编辑是徒增复杂性, 本身 "删除" 功能就是一种 "看起来有用" 的实现, 再编辑只是这种做法的延续.
目前 Nostr 允许内容互相替换的只有 kind:30023 (参数化可替换事件), 如果再引入编辑功能可能会继续影响事件的传递和检索效率(服务端一侧).
quoting nevent1q…asxv
FWIW, I think deletions on Nostr are a "meh" idea and edits are a bad idea. Consider the following:
- It's an additional layer of complexity. Nostr should arguably be simpler and it's already more complex in some ways centralized platforms are not.
- Different relays will disagree on whether to accept the edit or the delete event, so the original note may stay available. It may also become apparently unavailable and then available again in the future. Someone could send the old version to relays you don't use.
- Unlike some specific features like articles, zaps and whatever one can think of, it only makes sense if consistently implemented, but that's something we can only assume to be true of NIP-01.
- It makes retrieving a note less efficient. You now need to wait a response from all relays, just in case one of them has a deletion or a modification the first one to reply doesn't have.
- There is value in having modifications, but there is also value in having platforms that don't allow modifications, IMO, where an ID truly identifies a specific piece of text and nothing else. Now that Twitter allows modifications, Nostr can use the fact that it doesn't to diversify itself so as to convince users to use both (otherwise the network effect plays against Nostr).
On centralized platforms which allow modifications, users sometimes write a post with the plan of modifying it later. On Nostr that would be a bad pattern, however and I think the modification features can lead to bad usage of Nostr and, therefore, a bad user experience.
Ultimately it will prevail if clients and relays implement it and fail otherwise, but I'm not in favor of it.
#吐槽
In reply to nevent1q…00gg
_________________________
I also like this client, it is always faster than other web clients.
In reply to nevent1q…00gg
_________________________
I also like this client, it is always faster than other web clients.