©CC BY-NC-SA 4.0
🚩加入 Nostr!moe 社区: https://join.nostr.moe
#吐槽

In reply to nevent1q…txyx
_________________________

确实是有用, 但是目前没有太好的实现, Amethyst 为了向后兼容, 这个 "编辑" 功能实际上就是一个对 kind:1 的评论, 其中多了一个标记内容已编辑的标签, 类型被定义为 kind:1010.
#吐槽

最近 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.
#123云盘 开始支持在线云解压功能, 仅限 VIP 及 SVIP 用户使用.

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) Short Text Note by CXPLAY's Clip
一个 #Nostr 托盘中继, 可快速启动一个本地中继. 用于本地测试和客户端缓存, 支持快速导入导出事件. 支持 #Windows #Linux#macOS.
https://github.com/CodyTseng/nostr-relay-tray
#Android 同步软件 #FolderSync 计划推出桌面版客户端, 支持 #Windows, #macOS#Linux, 定价尚未公布. 现已开放早期测试候选名单填写.
https://foldersync.io/desktop
#吐槽

In reply to nevent1q…pj6n
_________________________

于是我连 Windows 11 都还没升级 WSA 就被砍了, 可千万别把 WSL2 也砍了. Short Text Note by CXPLAY's Clip
#吐槽

三年前花了二十买了一双拖鞋, 今天再去看同款居然已经涨到三十了.
#吐槽

有 Android 软件同时在多个渠道发行, 为了应对不同渠道来自平台方的审查和特殊要求, 理论上来说应该每个渠道都用不同的包名, 甚至签名. 对于独立开发者来说可能过于繁琐, 但至少面对不同的市场投放要区分包名和签名, 比如国内软件市场, 海外软件市场甚至欧洲软件市场.
对于我自己作为用户来说, 经常遇到的情况就是 Google Play 上更新的软件然后又被国内应用商店的同包名软件更新覆盖了, 更微妙的是国内应用商店更新的版本号总是比 Google Play 上的高一个小数点版本. 这种同包名但用不同版本号的手段大多都是为了刷渠道下载量, 因为应用商店自动更新几乎都是默认启用的, 还有开发者用来区分两个市场的用户, 特别是经典国内和 Google Play 同时发行的, 国内版本会用国内的优化网络, 只要手机上有国内应用商店的, 始终版本都会比 Google Play 高, 始终被默认覆盖. 但是到了类原生常驻后, 手机上甚至免不了有三四个应用商店: Google Play, 国内应用商店*n, F-Droid.
在未来就单单 Android 平台, 可能还会再加一个俄罗斯的 RuStore, 地区或者说渠道特供软件会更多.
Back to Top