@Vivek So I’ve been thinking about this. To keep things simple, for Satellite, I’m going to go ahead and use kind 4549 as a direct clone of kind 1 as @Vitor Pamplona suggested. So the content string of 4549 will be text just like kind 1. My initial concern was that having a single kind defined as a “community post” would preclude the reuse of other event kinds, which is why I suggested “wrapping” the events. I still intend to use kind 4549 as a wrapper to post non-kind-1 events into communities. When a non-kind-1 event is posted, the 4549 event will include a “k” tag indicating the kind of event that was wrapped. But for 4549 events that do not have a “k” tag (or a “k” tag equal to 1), Satellite will assume that they should be treated like kind 1 and render the content directly. I like this cause it’s just doing the simple “clone kind 1 thing” but adding the “k” tag allows me to do also do the wrapping thing so I can support other event types on Satellite. If other apps only care about kind 1 that’s fine. I’m also implementing this weekend and writing up some documentation. Lmk if you wanna collab 🤙

Awesome :) thanks for the detailed response 🙏 I will try to do the same I will get back to you with questions if I get any during implementation. My weekend schedule is still adhoc and me being in India makes synchronous collab impossible. Will keep a message channel open for async collab, if that's ok with you.

Just pushed this update. Some rough edges here and there but usable now.

Hi @Stuart Bowman is satellite still using 4549 as default kind for community messages? I got a GitHub issue saying NIP doesn't talk about this 4549 kind.

GitHub

New post should be of kind 1 not kind 4549 now · Issue #52 · vivganes/zapddit

Looking over the data zapddit creates I see new un approved post are currently of kind 4549 and the spec says to make it kind 1. Did you do that so...

Not sure how to resolve this. Cc: @Jingles