For the first step, we practiced many. I am excitied for the second step: human vs AI, that is to make nostr the channel for human talking to the remote AI, eg: you want LLMs work for you while you are in vacation. LLMs reports you the progress via nostr and you repond back and guide them like a real boss.

I think we should make nostr works for human vs human, and then human vs AI, and finally AI vs AI.

yeah, that's the mode: 1. encourage people to save their key and set up contact info if they expect a response 2. ignore if you don't care responds, eg: maybe you offer a alternative contact way in the message.

That's a good idea 🤙. I will talk to keychat about how to do it.

yeah I have such thoughts too. but there isn't a standard way (NIP) to allow relay charges per-message. Another more interesting thoughts to me is that we can have different stamps that is not comming from POW but human-made. So people can buy the stamp from other people.

yes that's part of the plan! Right now you can do something like this in github readme

https://github.com/RetricSu/pingkey

In the future we shall extend that to be a rich embedable component

I have received some letters and collected some pow stamps. thank you!

I made a little project called pingkey https://pingkey.xyz/ it is a messaging app works like traditional mailing. You setup relays as your mailbox, people write letters and post them to you. Each letter must contain a POW which then turn into a unique POW stamp. It is that simple and I imagine it will become a alternative contact card for those people who are old enough that just hate social network and prefer to keep this simple way just like me. Feel free to try it and contact me https://www.pingkey.xyz/p/ce6232feaec4e6d01a4e00daa3648030c42017bdf589e34b53744fc49c5cba8a and give some feed back.

是的，这个其实也是缺少migration的方案，协议没有规定，导致比较混乱。很多relay应该也不接受一下子导入几万个历史event，会被rate limit吧

还有一个想法，也许每个用户都应该只用一个 relay, 挂了就再换一个 relay，同时更新一次 10002 kind 的 event。这样对客户端会比较友好，同时仔细想想，其实好像也不比多用几个 relay 来得差——首先你更明确的知道你的数据在哪个 relay 上，同时 nostr 的应用一般都是 local-first 的，本地也有一个备份。相反，如果用很多 relay，其实反而让客户端和用户都很困惑：我的数据到底存在哪个 relay？于是很多客户端要做很多工作去猜，用户体验也变复杂。

我觉得 nostr 生态缺少 nip65 indexer 的基础设施。需要很多只接受kind 10002 的小 relay, 这些 relay 对带宽和存储的要求都不要，但他们需要彼此能通信同步数据，专注于为应用提供查询 relay list 的功能。

这是一个问题，短时间内创建管理大量 websocket的开销。另外有个问题，要从哪里去找这些用户的 relay list（10002 kind），一些固定的大 relay？

nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl 好奇现在 jumble 有没有采用 nip-65 模式？加载主页的时候，会聚合我关注的人的 relay list 再去找它们抓消息吗？

哈哈不错，比我的英文能力好多了

那可能是梯子的原因。你在家用什么跑的？我有个闲置群晖，倒是想用 docker 跑个长期的

is there any service like NIP-65 indexer in Nostr nowadays? how does it work? simply syncing kind 10002 from all the big relays? #ask #nostr

另外我发现 cody 做的很多东西都很不错，包括 jumble 也是现在非常好的客户端，真高兴 nostr 中文社区有你们还在 build 👍 之前许多人可能都已经不太活跃了

nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl 做的这个 https://github.com/CodyTseng/pigeon 蛮有意思的，我没看代码，目测是直接通过一个有 ip 的公共服务器做代理，让许多分散在本地内网里没有 ip 的 relay 可以对外，内网 relay 和代理 relay 之间就用 client-server 的方式去通信就行了？这个想法我挺喜欢的，简单有效。就是不知道实际运作性能怎么样，我尝试在笔记本上跑了个 relay tray，有时候能连上，有时候不太能，不太确定原因？

I am doing some thing new this past weekend, it is not polished and open-sourced yet, but would like to share it a little bit, it is called PingKey, a kind of replacement for linktree but minimal limited with clean interface.

PingKey works like a contact card, or rather just a way to let other people reach you without requiring email, phone number or any social network accounts.

You can leave a message to PingKey's CEO here https://www.pingkey.xyz/p/87b915fff950d6683f449edb8d283c04ac789c506daf49dbdbd97b344e5db383 to ask question, participate in the early days, make suggestions...

一个类 utxo 结构 + 同样使用 POW 共识的区块链

区块链轻客户端和 nostr 非常契合，因为它们都遵循简单的客户端验证的原则。这就是为什么我觉得用 nostr 来做个区块链轻客户端的钱包会挺有趣的

Blockchain light clients and Nostr are a great fit because they both follow the principle of simple client-side validation. That's why I think it would be interesting to build a blockchain light client wallet using Nostr.