I couldn't go to any Nostr-related events that were happening, because of various economic and geopolitical reasons, and I couldn't even launch one locally for similar reasons, so the next-best thing that I wanted to do was to see if I could run parallel events of the in-real-life ones but in virtual reality (/ in VRChat), but I haven't got around to doing it, however, I was very happy that I noticed/discovered an individual who made nostr group in VRChat and they discovered me back on nostr, so we connected, and they have organized an (unofficial) event in VRChat to run alongside #nostrasia , where a world was created for it with fun nostr purple ostriches running around as we talked and watched the livestream for the event within the world. It was a great start and I enjoyed myself =3 I don't know if I will, but I'd love to keep an eye on future events and see if they'll also do livestreams so we can do more of these types of events in VR happening in parallel with the in-real-life ones. Eventually / hopefully, we can have our own vr/nostr focused event, perhaps #vrnostr / #nostrvr ( #nostrvrc if specific to one vr game) in the future =3 Aside from that, the friend I made during said event is thinking of doing a very interesting project related to nostr and VRChat, and if they manage to do it, it'll be very exciting/fun =3 View quoted note →

During the #nostrasia event, someone mentioned doing a multisig to verify the authenticity of a secondary nostr key if someone has had their primary nostr key compromised. It was in Japanese, so I might not have gotten the full picture; however, if that's the whole story, there is one issue with it: An attacker can forge a multisig with a different secondary key they control and fake an older data/time than the truthful one. Since nostr doesn't have a timestamp-enforcing mechanism, this method is not necessarily a 100% verifiable solution. However, a solution to it would be to involve Bitcoin in the process, by deriving a Bitcoin address from both the primary and secondary key and conducting the multisig process on that level, which would give it the security/timestamp it needs to properly act as a 100% verifiable backup solution. The only 'con' about this is the cost of money to do so. I'd do that, but I'd also do it differently, the reverse in fact, where the primary key is kept hidden/secure while the secondary key is the one to be used publicly and would be the one being exposed to the risk of being compromised, where if it does happen, then you simply use a different/new secondary key that does another multisig with the primary key, and clients would adapt to this new system where if you follow my primary key, you'd also see posts from my secondary key (with a label 'proxy' so you'd know).

Enjoying Nostrasia digitally in virtual reality x3 (unofficial event, but fun =3) #Nostrasia #Nostrasia2025 #エアのすあじ View quoted note →