Thread

Replies (2)

You would solve for this differently. I'm not sure if it was discussed in the times before I showed up on nostr, but, kind 1 has always been a bit frustrating. I believe the better implementation would be to tag kind 1 notes with a new identifier. In my mind it would be beneficial to have a type of "broadcast" signifier to determine "this kind 1 event is meant to appear in any global feed" versus.. some other type of kind 1. If the tag were a "gated" post then it would need to include the relay in which it is intended, as to be ignored by clients and not passively republished to every available relay. Spaghetti as fuck. Sounds cool if someone wants to try reworking kind 1. I would wonder what kind of schemas people consider in Nostr forks. Would possibly deprecate some other kinds, or at least affect them. My original solution was to use relays-as-communities if it had to be so- but that doesn't work quite right, either. Headaches and echo chambers doot doot
↩ replying to Tekkadan, ゲロゲロ! 🐸
Tell me more about what you tries to implement and why it failed. I agree if we designed from scratch, your gated tag would work, but that isn't going to happen. So I think other best option is identical kinds designed for gates. Then you have e another kind (6?) For sharing if you want the gated post to be viewable globally. That way existing clients with global views can choose to look at the share and then render the event being shared.