还真有不少。。。
你的账号可以先添加几个网址过滤词来过滤一下
另外可以试一下修改详情模式为追踪模式来看帖
迟点他会把名字和回复内容都改为无规律，那该怎么过滤~~~
The challenge of securely logging into a nostr mobile app seems to be stifling innovation/usage for a number of powerful experiences. I've run into this repeatedly over the last couple of days.
Who is actively working on solving this?
I know nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft has nsecbunker and nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy has nsec.app. What else is out there ?
I am also deving a signing app. It support NIP-07 (Just like the app Spring) and NIP-46 (Remote Signing) for Android and IOS. And it also NIP-55 (Android local signing) for Android.
But it is under heavy develop, there are many things need to do.
https://video.nostr.build/6684ef4231be45d2bb09abfc5b15cf92fc600ceb1dfc27964f750c09e4aeea4f.mp4
Many clients support to display it, but you must write markdown by yourself.
Hello, whick client supports using ```nostrconnect://``` url with Nostr Remote Signing (NIP-46) ? I think this method has some problem. The flow must different with using ```bunker://``` url.
https://github.com/nostr-protocol/nips/blob/master/46.md#direct-connection-initiated-by-the-client
#asknostr #devstr #nostr
哈哈, 我已经四百多个了, 全都是 ReplyGuy. 昨前天手动从 nostr.band 检索了关键词后批量加进去三百多个, 然后继续在客户端上屏蔽.
https://media.naeu.net/fa2a1348b475a470d9a3883ba0b424b80266958f96c64943e3308a1983ef8d01.webp
关键词屏蔽不行了？
😅 这么夸张啊
This client is build with flutter and it supports web, pcs and mobiles.
Are there NIPs for *ios signer application* just like *NIP-55: Android Signer Application* .
#asknostr #devstr #nostr
#123云盘 目前的 WebDAV 上传体验非常烂, 特别是多文件. 由于这个 WebDAV 其实是用 OpenAPI 兼容实现的, 所以和一般的 API QPS 限制也是一样严格.
> https://123yunpan.yuque.com/org-wiki-123yunpan-muaork/cr6ced/txgcvbfgh0gtuad5#KWm4Z
文件操作 move 和 delete 居然 QPS 限制为 1, mkdir 和 create 限制为 2. 所以有任何 WebDAV 同步能支持限制 QPS 的吗? 不然只是一串串失败了.
PS: 根据开发群里面的反馈, 要给123单独付费流量包才有可能提高 API 的 QPS.
所有网盘 webdav 接口都比较尴尬吧？我有一些app 用 webdav 当同步接口，经常不好使。webdav 经常限制调用速率
At different place of china, it also has different rule.
Maybe i should change the default nostr.build upload method to nip96?
Yes, this file i had uploaded many times 🤣
Have you change the image service to NIP96? If you select nostr.build upload service, it will try to use the old upload api.
