#吐槽
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.
123云盘全新功能【在线云解压】正式上线,面向【VIP及SVIP用户】开放!
在线云解压功能支持云盘中查看或解压压缩包内的文件,无需再将文件下载到本地后再进行解压查看。
VIP用户支持操作5GB以内压缩包,支持 .RAR、.ZIP格式解压。SVIP用户支持操作8GB以内压缩包,支持.RAR、.ZIP、.TAR和.TAR.GZ四种格式解压。
Web端、PC端、Mac端已同步上线,请前往官网下载最新版本体验,云解压使用教程,请扫描下方二维码查看。
#吐槽
In reply to nevent1q…k2s4
_________________________
这个功能仅提供给消费版 OneDrive 的预览版移动客户端用户使用, 卡的真死, 难怪没多少人知道. 2021 年的时候就有人在问了: https://www.reddit.com/r/onedrive/comments/obptjf/how_do_i_upload_by_url/
这种功能能预览测试三年也是没有谁了.
---
不支持使用 URL 将项上传到 OneDrive for Business、SharePoint Online 和 SharePoint Server 2016。
—— 通过 URL 上传 - OneDrive API - OneDrive dev center | Microsoft Learn: https://learn.microsoft.com/zh-cn/onedrive/developer/rest-api/api/driveitem_upload_url
This feature was introduced as an experimental option for users who wanted to save files from the web directly to their OneDrive without downloading them first and was only ever supported for Consumer OneDrive.
—— Important update on OneDrive URL upload feature: https://devblogs.microsoft.com/microsoft365dev/important-update-on-onedrive-url-upload-feature/ (Microsoft 365 Platform - DevBlogs)
In reply to nevent1q…k2s4
_________________________
这个功能仅提供给消费版 OneDrive 的预览版移动客户端用户使用, 卡的真死, 难怪没多少人知道. 2021 年的时候就有人在问了: https://www.reddit.com/r/onedrive/comments/obptjf/how_do_i_upload_by_url/
这种功能能预览测试三年也是没有谁了.
---
不支持使用 URL 将项上传到 OneDrive for Business、SharePoint Online 和 SharePoint Server 2016。
—— 通过 URL 上传 - OneDrive API - OneDrive dev center | Microsoft Learn: https://learn.microsoft.com/zh-cn/onedrive/developer/rest-api/api/driveitem_upload_url
This feature was introduced as an experimental option for users who wanted to save files from the web directly to their OneDrive without downloading them first and was only ever supported for Consumer OneDrive.
—— Important update on OneDrive URL upload feature: https://devblogs.microsoft.com/microsoft365dev/important-update-on-onedrive-url-upload-feature/ (Microsoft 365 Platform - DevBlogs)