Why Nostr? What is Njump?
hodlbod /
npub1jlr…ynqn
2024-06-17 21:54:16

hodlbod on Nostr: Vitor Pamplona hzrd149 Stuart Bowman I'm in the process of sprucing up Coracle's nip ...

Vitor Pamplona (nprofile…2dqr) hzrd149 (nprofile…3q3y) Stuart Bowman (nprofile…h25c) I'm in the process of sprucing up Coracle's nip 72 integration, and was wondering how likely it would be for any of you to update your implementations based on the changes outlined here: https://github.com/nostr-protocol/nips/pull/1024

Currently, known issues include:

- Embedded `naddr`s for groups aren't rendered in Amethyst.
- Since Coracle doesn't do post approvals, no moderators are added to the group's definition. Coracle also uses a one-off key to administer the group, so administration can be shared. This makes it impossible to administer groups created in Coracle from other clients.
- Groups created in Coracle don't show up in Satellite.
- Group posts created in Coracle don't show up in Amethyst, and are hidden behind a tab in nostrudel.

I recognize that I'm the one breaking interoperability, but it's my opinion that forcing moderators to post approvals has made adoption of groups fail pretty badly. Making moderation opt-in rather than opt-out would be a big improvement, although I'm open to any opinions on the topic.

I also know that at least Stu has expressed interest in NIP 29 groups, so I don't really expect any changes to satellite. But I do want to make Coracle's groups useful for Nashville, which means interoperability.
Author Public Key
npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn