Another project built with Osty (https://osty.dev) has just received the OpenSats Grant! Such an incredible achievementβfeeling grateful! π
nostr:note1zj45eh2nlzkjd42h2jer6pxckafpe6c2gxch8se4warv6m7vt7gqx8vk7x
https://groups.nip29.com πππ₯
congrats good people π
nostr:note1hxnh5gx47a4j8dymjtvumwjwgp4twdjsph5lwcjyln6rz0frs7pq7gwfnk
congrats everyone π
AFAIK getalby supports local passcodes β you may wanna use a passcode to prevent signing on your behalf
make NIP-82 great (merged) again!
Nostr changes lives! π
GM
With top-level groups relays won't need explicit support for NIP-29. Existing relays (nos.lol, frens.nostr1.com) and NIP-29 Groups (0xchat Open Group, habla, Robosats, etc.) can function as communities.
https://video.nostr.build/6541389701cac62b669a106d912c59570927161b680ef860d72daefa66b319b4.mp4
nice fork of Groups! π
MOAR NIPs
nostr:note1r0n6hymy3jnq8rttja6kxsl79qkc3qff6dhuwnqkrc3wv6jaw47qfv909c
why nostr dms not work as smooth as other protocols? is this something to be fixed on relay or client side? i would be happy to have your experience and ideas.
nostr:nprofile1qqspycgrhlwu3he9ddhq407h7duheqxucn4g3a7zlp7agyzzyz6dvhcpz9mhxue69uhkummnw3ezuamfdejj73cxtrz nostr:nprofile1qqs84k6jpsav0jmdeqjn2zxlpnsajaw6f8l0m2d4e9t8gjsyn53s4nspzemhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6qgdwaehxw309aukzcn49ekk2qghwaehxw309aex2mrp0yh8x6tpd4ehgu3wvdhk6pw0r8j nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9uq3xamnwvaz7tmhda6zuat50phjummwv5hsx7c9z9 nostr:nprofile1qqsru22d9lfnnwck54qr4phrvey50h2q33xc0gqxv5j03ftn4efu4rspzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap08rutw0
what problem do you encounter? mine is working good. I'm using different clients day by day and most of them are doing good with DMs. Primal, Coracle, Damus, etc.
how do you think we should send a group link to a friend?
iirc there was a proposal by nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 to add nchat references, they probably can be used to reference groupchats
I think nip29 groups should have standard unique ids just like our pubkeys (nprofile), something like `ngroup` which also includes its relay url.
khathru NIP-29 relays are rejecting events that have a-tags due to a very strict "large tags" policy: https://github.com/fiatjaf/khatru/blob/d4334ac2bb863503cc6348894027461b6d8d4088/README.md?plain=1#L76 one use case I had in mind was to be able to share groups in chats by referencing their metadata event which is replaceable but this prevents me from doing it.
could we relax this nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub18c556t7n8xa3df2q82rwxejfglw5przds7sqvefylzjh8tjne28qld0we7 nostr:npub10td4yrp6cl9kmjp9x5yd7r8pm96a5j07lk5mtj2kw39qf8frpt8qm9x2wl or should I only include text references on the content?
along with the tag limits, I think we need a better approach for addressing NIP29 groups. I don't know maybe something like nostr:ngroup1 π€·ββοΈ
you should try npub.pro by nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy
Opportunity π
nostr:note1gqc5dqgdqepjzc6q9ld0fw8fp3yt3xx0q66gavn632tlljjwqgqscdu6al
