not sure I understand your sentence...
didn't see the detail part for the caching so is there any open-source code for such a cache service? and do you think it is possible to make the cache service just a special relay so that we don't need to handle another concept and keep more consistency?
next time people ask me why Nostr, I'll just throw this post at them😼
I build a short-note/long-post mixed one https://flycat-web.vercel.app/ if you are interested
有道理 感觉我可以让flycastle自动保存内容中的图片,这样备份的意义更大了
这个我反而觉得不现实了,wss要搞太麻烦,而且仅仅考虑个人用户他肯定不会有长期可以稳定运行的机器,买专用的也只有geek用户
我自己的体验:不开电脑时,局域网的私人relay一段时间没上线还行,上线时我通常会用飞猫再点一下同步
this is an interesting idea. While adding more stuff on top of nostr, we have to be very careful about how to add it. some of the discussions in the PR are quite enlightening https://github.com/nostr-protocol/nips/pull/344
Do you know what Winny is?
Winny (also known as WinNY) is a Japanese peer-to-peer (P2P) file-sharing program developed by Isamu Kaneko, a research assistant at the University of Tokyo in 2002.
https://en.wikipedia.org/wiki/Winny

interesting, does it make trouble for the creator?
somehow I think this should be the philosophy for nostr protocol
p2p is not a must. we don't need p2p in a lot of cases. but we don't have to go centralization in those cases either.
I agree. the core protocol should decouple from the transport layer. it is good to have a websocket impl at first stage, but it is unnecessary to be limited to it.
happened to me once. get some good rest, and see you back.




