That’s because all the people excited about it are literally hanging out on Keet and pear apps, lol. I mean if you go to Twitter you won’t find many people excited about Nostr… cuz they’re all on Nostr 😆
I literally know of exactly one person excited by the Pear stack, nostr:npub1h8nk2346qezka5cpm8jjh3yl5j88pf4ly2ptu7s6uu55wcfqy0wq36rpev
Quite interesting to never see anything about it in my nostr feed
Speaking of, is Keet open source yet?
Discussion
Fair 😄, it's interesting nonetheless to see near zero talk about it here. Is nostr brought up in Keet at all? know of anyone interested in building a bridge? I'd love to follow some pubkeys from over there
Also trying to listen to most Pear Report episodes.
Yes actually. Talked to a few people interested in making bridges. Also have talked to some devs myself about building a Nostr client that runs entirely over Pear but we have some other projects to finish first. If we had a separate client that worked really well i imagine bridges would pop up naturally. Of course there’s no reason the functionality for connecting to both relays and directly to peers couldn’t be in the same client.
keet is quite functional enough to carry all its community chat about it and pear on keet
there is a link to the community room on the profile page in keet
today nostr was discussed a lot on keet, supersu the holesail dev is trying out running a nostr relay via holesail
can nostr and pear pubkey formats interoperate somehow?
Not sure. I’ve been looking into finding a path for this with BIP85
i dont remember what the new keet multidevice id system uses but hypercore is using ED25519 https://github.com/holepunchto/hypercore-crypto and https://github.com/sodium-friends/sodium-universal and nostr is using Schnorr signatures standard for the curve secp256k1 which sodium wont do, they are both 64bytes i think